AstroMCP
Related Servers
Alternatives to AstroMCP
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityAmaintenanceConnects AI assistants to Vetstar, MAST, SIMBAD, VizieR, Gaia DR3, ExoFOP-TESS, the NASA Exoplanet Archive, NASA ADS, Crossref/DataCite, the UAT, and Zenodo so users can vet TESS candidates, fit ephemerides, check contamination and novelty, build RNAAS manuscripts, verify references, and prepare Zenodo submission bundles. It prepares analyses and files only, leaving uploads, submissions, and publishing to the user.1MIT
- AlicenseAqualityCmaintenanceAccurate astronomical catalog data and observing session planner for LLM assistants. Stops hallucinated magnitudes, coordinates, and visibility.326 npm3MIT
- FlicenseNot gradedqualityDmaintenanceEnables natural language queries of astronomical data across multiple archives (Gaia, 2MASS, image holdings) via the Trillian platform, allowing users to search catalogs and find images by sky coordinates.-
- AlicenseNot gradedqualityBmaintenanceEnables AI agents to query NASA/JPL data on asteroids and comets, including small-body orbits and physical parameters, near-Earth close approaches, Sentry impact-risk assessments, and recent atmospheric fireballs. All four tools are keyless and work over a hosted gateway endpoint or a local stdio server.14 npmMIT
- 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-
- AlicenseBqualityDmaintenanceMCP 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.238 npm2BSD 3-Clause
TDQS
Scored across 14 tools
Most tools have distinct resource-and-action purposes: TNS name lookup vs. cone search, ZTF light curve vs. nearby objects, Rubin object vs. recent objects. The main ambiguity is that whats_here aggregates SIMBAD, VSX, Gaia, TESS, ZTF, and asteroid lookups while individual catalog tools also exist, so an agent must decide between broad and targeted queries. Descriptions largely resolve this, but the overlap keeps it from a 5.
Names are readable and often grouped by resource prefix (tns_object, ztf_lightcurve, rubin_recent), but conventions are mixed: bare catalog names like simbad, vsx, and gaia, verb-style observe_tonight, and noun/qualifier forms like tess_known and asteroids_at. There is no single predictable action pattern throughout.
Fourteen tools is well within the ideal range and each maps to a meaningful astronomy follow-up capability. The set covers several catalogs, planning, cutouts, and transient brokers without obvious redundancy at the count level.
The surface covers a broad range of object lookup, crossmatching, transient discovery, and observing-planning needs across TESS, SIMBAD, VSX, Gaia, TNS, ZTF, and Rubin. Minor gaps remain, such as a general name-to-coordinate resolver or NED/MPC catalog access, but core workflows are supported.