Starfetch
OfficialRelated Servers
Alternatives to Starfetch
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityDmaintenanceMCP server that provides tools to query 17+ astronomical databases (e.g., SIMBAD, VizieR, Gaia) via HTTP/TAP APIs, enabling AI applications to access astronomical data through natural language.132BSD 3-Clause
- FlicenseNot gradedqualityDmaintenanceProvides unified natural language access to 40+ astronomical databases and surveys including DESI, SIMBAD, SDSS, and Gaia, enabling researchers to search, retrieve, and analyze astronomical data without learning complex APIs.6-
- AlicenseNot gradedqualityCmaintenanceEnables querying the SIMBAD astronomical database for object resolution, script execution, ADQL TAP queries, and cone searches using natural language.14MIT
- AlicenseNot gradedqualityAmaintenanceAn MCP server exposing IVOA-compliant astronomical archives (NOIRLab Astro Data Lab, NRAO/ALMA, CADC, ESO, Gaia, …) to LLM clients.2MIT
- AlicenseNot gradedqualityCmaintenanceEnables querying NASA Exoplanet Archive data using ADQL TAP, planet search, composite parameters, Kepler candidates, and microlensing events.19MIT
- AlicenseNot gradedqualityAmaintenanceEnables AI agents to safely explore and query databases across SQLite, PostgreSQL, MySQL, and MSSQL, with schema introspection, natural language queries, and data profiling.MIT
TDQS
Scored across 12 tools
Each tool targets a distinct TAP workflow step—service discovery, metadata inspection, synchronous query, or async job lifecycle—and the descriptions clearly separate near-neighbors like availability vs capabilities and query vs submit_job. No two tools appear interchangeable.
All tools share a consistent starfetch_ prefix and snake_case style, but the suffix pattern is mixed: list_presets and submit_job use verb-noun order, registry_search and job_wait/fetch/delete use noun-verb order, and availability/capabilities/tables/columns are bare nouns. The grouping is readable, but verb placement is not uniform.
Twelve tools is well-scoped for a TAP client; each tool covers a necessary step from service discovery and metadata inspection through synchronous queries and async job cleanup. There is no obvious redundancy.
The tool set covers the main TAP workflow comprehensively: discovery, capabilities, tables, columns, synchronous queries, and async job lifecycle. Minor gaps such as missing explicit job abort/cancel or job listing exist, but agents can work around them using wait and delete.