Exoplanet Archive
NPM · @PIPEWORX/MCP-EXOPLANET-ARCHIVE · 2 COMPONENTS
NASA Exoplanet Archive MCP.
Available components
Last scanned (14 hours ago)
Scores higher than 69% 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-exoplanet-archive). 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 Usability67
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 638 tokens (~106/item across 6 items; 6 tools + 0 resources), lean.Pass
- 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 Coverage82
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 45% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 6 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 7 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.
- 5 Nov 26 0
- Security disclosure: unverified → fail ▼ functional
- 4 Nov 26 +1
- Security disclosure: fail → unverified ▼ functional
- 2 Nov 26 +1
- Security disclosure: unverified → fail ▼ functional
- 1 Nov 26 +1
- Tool safety: pass → unverified ▼ security
- Stability: Stability not yet verified: we do not have a sandbox capture of the MCP schema this version of the package serves yet. security
- Tool coverage: 100 → unverified ▼ functional
- Capabilities: pass → unverified ▼ functional
- Security disclosure: fail → unverified ▼ functional
- Stability: unverified → 0.10 ▲ functional
- First check of Schema quality: unverified functional
- Package version: 0.2.0 → 0.2.1 functional
- 30 Oct 26 0
- Security disclosure: unverified → fail ▼ functional
- 29 Oct 26 78
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-exoplanet-archive@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-exoplanet-archive |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/pipeworx-io/mcp-exoplanet-archive/.github/workflows/publish.yml@refs/heads/main |
| Rekor log index | 3635933984 |
| Predicate type | SLSA build provenance https://slsa.dev/provenance/v1 |
| Subject digest | sha512:4a0e88ef88b4c4f584b51ca23389474180fe1a54b18249c5880c7eb34d571256b9aa6e16f05b3fd37d7edac476877ebfac67b138f67df111c48762ebe |
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 →
composite ~89
Composite planet parameter table `pscomppars` -- one row per confirmed planet. Use this (or `confirmed_planet_count`) for "how many confirmed exoplanets" questions and for any per-planet listing; do not use `ps`/`tap` for those, since `ps` has several rows per planet.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | number | – | – |
| query | string | – | – |
No output schema declared.
No examples provided.
confirmed_planet_count ~122
Count of confirmed exoplanets -- from the composite parameter table `pscomppars` (one row per planet), not the per-solution `ps` table. Use this for "how many confirmed exoplanets" questions. Optional filter narrows the count, e.g. "disc_year = 2023" for planets discovered that year. Returns the unit and the date of the live query.
| Name | Type | Req | Description |
|---|---|---|---|
| query | string | – | Optional WHERE clause on pscomppars (without "WHERE"), e.g. "disc_year = 2023". |
No output schema declared.
No examples provided.
kepler_candidates ~60
Kepler Object of Interest (KOI) candidate table -- unconfirmed candidates, not confirmed planets. Do not use this table's row count to answer a confirmed-planet-count question.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | number | – | – |
| query | string | – | – |
No output schema declared.
No examples provided.
microlensing ~37
Microlensing event table -- detection events, not a planet count.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | number | – | – |
| query | string | – | – |
No output schema declared.
No examples provided.
planets ~127
Per-solution search against the `ps` (Planetary Systems) table -- one row per published parameter SOLUTION, with several solutions per confirmed planet. Good for comparing how a planet's measured parameters changed across papers; NOT a planet count or a clean per-planet list (its row count is parameter solutions, not planets). For planet counts or one-row-per-planet listings use `composite` or `confirmed_planet_count` instead.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | number | – | 1-10000 (default 25). |
| query | string | – | Optional WHERE clause (without "WHERE"). |
No output schema declared.
No examples provided.
tap ~145
ADQL TAP query. For "how many confirmed exoplanets" or any per-planet count, query `pscomppars` (one row per confirmed planet) or COUNT(DISTINCT pl_name) -- never a bare COUNT(*) FROM ps, which counts published parameter SOLUTIONS (several per planet, currently ~40k rows for ~6.5k planets) and silently over-counts by 6x. Prefer the dedicated confirmed_planet_count tool for planet-count questions.
| Name | Type | Req | Description |
|---|---|---|---|
| format | string | – | json (default) | csv | votable |
| query | string | yes | e.g. "SELECT TOP 5 pl_name, sy_dist FROM ps" |
No output schema declared.
No examples provided.
How do I install the Exoplanet Archive MCP server?
Exoplanet Archive runs locally as an npm package, launched with npx -y @pipeworx/mcp-exoplanet-archive. 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-exoplanet-archive
claude mcp add pipeworx-io-exoplanet-archive -- npx -y @pipeworx/mcp-exoplanet-archive
What is the Exoplanet Archive MCP server?
Exoplanet Archive is an MCP server listed in the public MCP registry as io.github.pipeworx-io/exoplanet-archive. NASA Exoplanet Archive MCP. This page covers its npm package (@pipeworx/mcp-exoplanet-archive).
Is the Exoplanet Archive MCP server safe to use?
Exoplanet Archive scores 81 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 Exoplanet Archive MCP server expose?
Exoplanet Archive exposes 6 tools: tap, planets, composite, confirmed_planet_count, kepler_candidates, microlensing. Their descriptions and schemas cost roughly 580 tokens of context every time the server is loaded.
Is the Exoplanet Archive MCP server still maintained?
Exoplanet Archive 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 Exoplanet Archive MCP server under?
Exoplanet Archive 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 Exoplanet Archive MCP server?
VerifyMCP ran 16 checks on Exoplanet Archive, 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.