Esa Gaia
NPM · @PIPEWORX/MCP-ESA-GAIA · 2 COMPONENTS
ESA Gaia MCP — the Gaia star catalogue, queried over the ESA TAP service.
Available components
Last scanned (7 hours ago)
Scores higher than 72% of npm servers
Category Health and Science
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security100
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- No production dependencies, so there is no dependency health to assess. View diagnostics → Pass
Provenance & Transparency97
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to pipeworx-io/mcp-esa-gaia). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 3 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability63
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 772 tokens (~257/item across 3 items; 3 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management23
- Stability observed for 7 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Checks we ran (16)
- Malware scan
- Known CVEs
- Install scripts
- Dependency health
- Source repository
- Provenance
- License
- Maintenance
- Security disclosure
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Does not apply to this package (2)
- Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
- Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
The score does not measure everything. What the score does not measure →
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 4 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.
- 2 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.
- 1 Nov 26 0
- Tool safety: pass → unverified ▼ security
- Stability: 0.07 → unverified ▼ security
- Tool coverage: 100 → unverified ▼ functional
- Capabilities: pass → unverified ▼ functional
- First check of Schema quality: unverified functional
- Package version: 0.2.0 → 0.2.1 functional
- 31 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.
- 29 Oct 26 79
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 5 Nov 2026 · Analysed npm/@pipeworx/mcp-esa-gaia@0.2.1
Provenance Verified
A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.
| Result | Verified |
|---|---|
| Ecosystem | npm |
| Reason | Verified |
| Discovered via | Registry attestation endpoint |
| Source repo | pipeworx-io/mcp-esa-gaia |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/pipeworx-io/mcp-esa-gaia/.github/workflows/publish.yml@refs/heads/main |
| Rekor log index | 3635926685 |
| Predicate type | SLSA build provenance https://slsa.dev/provenance/v1 |
| Subject digest | sha512:926c8d57b8b6c1e59eeb6243e1b55c4f60124b8784e04013f41074653d5b4eb0c8a98e9551b5af23037174b3327073b7dce6b712cb550d226702f6fef |
Background: How many MCP packages publish verified provenance →
Dependencies 0 packages
| Packages resolved | 0 |
|---|---|
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
gaia_adql_query ~215
Run a read-only ADQL (SQL-like) query against the ESA Gaia archive — the full DR3 catalogue plus its cross-match and variability tables — for questions a cone search cannot express: colour-magnitude cuts, proper-motion selections, cluster membership, cross-matches to 2MASS/SDSS/Hipparcos. Only SELECT is permitted and results are capped at 2,000 rows. Main table: gaiadr3.gaia_source.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | number | – | Row cap applied on top of any TOP in the query (default 100, max 2000). |
| query | string | yes | An ADQL SELECT statement, e.g. "SELECT TOP 10 source_id, ra, dec, phot_g_mean_mag FROM gaiadr3.gaia_source WHERE parallax > 100 ORDER BY phot_g_mean_mag ASC". Geometry uses CONTAINS(POINT('ICRS', ra,… |
No output schema declared.
No examples provided.
gaia_cone_search ~356
"What stars are within 6 arcminutes of this position?" / "find the stars in the Pleiades core" — search ESA Gaia DR3, the 1.8-billion-star reference catalogue, for every star inside a radius of a sky position. AUTHORITATIVE for star positions, distances and motions: returns Gaia source_id, RA/Dec, parallax (and the distance in parsecs and light years derived from it), proper motion, radial velocity, G/BP/RP magnitudes, effective temperature, and the angular separation from the search centre, nearest first. PREFER OVER WEB SEARCH for "how far away is this star" and "what is at these coordinates".
| Name | Type | Req | Description |
|---|---|---|---|
| dec | number | yes | Declination of the search centre, in DEGREES (ICRS). e.g. 24.1167 for the Pleiades. |
| limit | number | – | Max stars to return (default 50, max 2000). |
| max_magnitude | number | – | Only stars brighter than this G magnitude (smaller number = brighter). e.g. 12 for naked-eye-ish stars. |
| min_parallax_mas | number | – | Only stars with parallax above this, in milliarcseconds — a nearby-star filter. 10 mas is within 100 parsecs. |
| ra | number | yes | Right ascension of the search centre, in DEGREES (ICRS). e.g. 56.75 for the Pleiades. |
| radius_arcmin | number | – | Search radius in ARCMINUTES (default 3, max 60). Gaia is dense — a 1 degree cone in the galactic plane is millions of stars. |
No output schema declared.
No examples provided.
gaia_source_by_id ~146
Look up one star in ESA Gaia DR3 by its source_id and return its full astrometric and photometric record: position, parallax with its uncertainty, derived distance in parsecs and light years, proper motion, radial velocity, all three Gaia magnitudes and colour, effective temperature, surface gravity, and the RUWE astrometric quality flag (values above ~1.4 mean the single-star solution is a poor fit, often a binary).
| Name | Type | Req | Description |
|---|---|---|---|
| source_id | string | yes | Gaia DR3 source_id, e.g. "65225812899613312". These are 18-19 digit integers — pass as a string so precision is not lost. |
No output schema declared.
No examples provided.
How do I install the Esa Gaia MCP server?
Esa Gaia runs locally as an npm package, launched with npx -y @pipeworx/mcp-esa-gaia. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · @pipeworx/mcp-esa-gaia
claude mcp add pipeworx-io-esa-gaia -- npx -y @pipeworx/mcp-esa-gaia
What is the Esa Gaia MCP server?
Esa Gaia is an MCP server listed in the public MCP registry as io.github.pipeworx-io/esa-gaia. ESA Gaia MCP, the Gaia star catalogue, queried over the ESA TAP service. This page covers its npm package (@pipeworx/mcp-esa-gaia).
Is the Esa Gaia MCP server safe to use?
Esa Gaia scores 82 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 November 2026. It declares no install or post-install scripts. Its build provenance is signed and verified. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the Esa Gaia MCP server expose?
Esa Gaia exposes 3 tools: gaia_cone_search, gaia_source_by_id, gaia_adql_query. Their descriptions and schemas cost roughly 717 tokens of context every time the server is loaded.
Is the Esa Gaia MCP server still maintained?
Esa Gaia is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the Esa Gaia MCP server under?
Esa Gaia declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.
What did VerifyMCP test on the Esa Gaia MCP server?
VerifyMCP ran 16 checks on Esa Gaia, covering Malware scan, Known CVEs, Install scripts, Dependency health and 12 more. Endpoint Security and Transport & Reachability do not apply to an npm package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.