# Exoplanet Archive (npm · @pipeworx/mcp-exoplanet-archive)

NASA Exoplanet Archive MCP.

- Trust score: 81/100 (high trust)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- remote · `gateway.pipeworx.io`: 77/100, [markdown](https://verifymcp.io/servers/pipeworx-io-exoplanet-archive/exoplanet-archive-mcp.md), [page](https://verifymcp.io/servers/pipeworx-io-exoplanet-archive/exoplanet-archive-mcp)
- npm · `@pipeworx/mcp-exoplanet-archive`: 81/100 (this document), [markdown](https://verifymcp.io/servers/pipeworx-io-exoplanet-archive/pipeworx-mcp-exoplanet-archive.md), [page](https://verifymcp.io/servers/pipeworx-io-exoplanet-archive/pipeworx-mcp-exoplanet-archive)

## Channel facts

- Registry: `npm`
- Package: `@pipeworx/mcp-exoplanet-archive`
- Version: `0.2.1`
- Transport: `stdio`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-05.

- **Supply Chain Security**: 100/100
  - No malware found by supply-chain analysis.
  - No known CVEs affecting this package version or its production dependencies.
  - No install/post-install scripts declared.
  - No production dependencies, so there is no dependency health to assess.
- **Provenance & Transparency**: 97/100
  - Source repository is publicly reachable at the declared URL.
  - Cryptographically verified build provenance (signed, bound to pipeworx-io/mcp-exoplanet-archive).
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 3 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 67/100
  - AI-judged instruction clarity (good).
  - Tool/resource definitions use about 638 tokens (~106/item across 6 items; 6 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 23/100
  - Stability observed for 7 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 82/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 45% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 6 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 7 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### 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.

### Claude

```bash
claude mcp add pipeworx-io-exoplanet-archive -- npx -y @pipeworx/mcp-exoplanet-archive
```

### Cursor

```json
{
  "mcpServers": {
    "pipeworx-io-exoplanet-archive": {
      "command": "npx",
      "args": [
        "-y",
        "@pipeworx/mcp-exoplanet-archive"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "pipeworx-io-exoplanet-archive": {
      "command": "npx",
      "args": [
        "-y",
        "@pipeworx/mcp-exoplanet-archive"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add pipeworx-io-exoplanet-archive -- npx -y @pipeworx/mcp-exoplanet-archive
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "pipeworx-io-exoplanet-archive": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "@pipeworx/mcp-exoplanet-archive"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add pipeworx-io-exoplanet-archive --command npx --arg -y --arg @pipeworx/mcp-exoplanet-archive
```

### Hermes

```yaml
mcp_servers:
  pipeworx-io-exoplanet-archive:
    command: "npx"
    args: ["-y", "@pipeworx/mcp-exoplanet-archive"]
```

### Netclaw

```json
{
  "McpServers": {
    "pipeworx-io-exoplanet-archive": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "@pipeworx/mcp-exoplanet-archive"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add pipeworx-io-exoplanet-archive -t stdio -c npx -a -y @pipeworx/mcp-exoplanet-archive
```

### Other

```json
{
  "mcpServers": {
    "pipeworx-io-exoplanet-archive": {
      "command": "npx",
      "args": [
        "-y",
        "@pipeworx/mcp-exoplanet-archive"
      ]
    }
  }
}
```

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-05 (score 81, 0)

- [functional regression] Security disclosure: unverified → fail

### 2026-11-04 (score 81, +1)

- [functional regression] Security disclosure: fail → unverified

### 2026-11-02 (score 80, +1)

- [functional regression] Security disclosure: unverified → fail

### 2026-11-01 (score 79, +1)

- [security regression] 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.
- [functional regression] Tool coverage: 100 → unverified
- [functional regression] Capabilities: pass → unverified
- [functional regression] Security disclosure: fail → unverified
- [functional improvement] Stability: unverified → 0.10
- [functional] First check of Schema quality: unverified
- [functional] Package version: 0.2.0 → 0.2.1

### 2026-10-30 (score 78, 0)

- [functional regression] Security disclosure: unverified → fail

### 2026-10-29 (score 78)

First indexed and scored.

## MCP tools (6)

### `tap` (~145 tokens)

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.

Input parameters:

- `format` (string): json (default) | csv | votable
- `query` (string, required): e.g. "SELECT TOP 5 pl_name, sy_dist FROM ps"

### `planets` (~127 tokens)

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.

Input parameters:

- `limit` (number): 1-10000 (default 25).
- `query` (string): Optional WHERE clause (without "WHERE").

### `composite` (~89 tokens)

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.

Input parameters:

- `limit` (number)
- `query` (string)

### `confirmed_planet_count` (~122 tokens)

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.

Input parameters:

- `query` (string): Optional WHERE clause on pscomppars (without "WHERE"), e.g. "disc_year = 2023".

### `kepler_candidates` (~60 tokens)

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.

Input parameters:

- `limit` (number)
- `query` (string)

### `microlensing` (~37 tokens)

Microlensing event table -- detection events, not a planet count.

Input parameters:

- `limit` (number)
- `query` (string)

## Diagnostics

Captured diagnostic sections: Provenance, Dependencies. The full working is on the page: https://verifymcp.io/servers/pipeworx-io-exoplanet-archive/pipeworx-mcp-exoplanet-archive#diagnostics

## Score history

- 2026-11-05: 81
- 2026-11-04: 81
- 2026-11-03: 80
- 2026-11-02: 80
- 2026-11-01: 79
- 2026-10-31: 78
- 2026-10-30: 78
- 2026-10-29: 78

## Common questions

### 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.

## Links

- npm package: https://www.npmjs.com/package/@pipeworx/mcp-exoplanet-archive
- Socket report: https://socket.dev/npm/package/@pipeworx/mcp-exoplanet-archive
- Repository: https://github.com/pipeworx-io/mcp-exoplanet-archive
- Website: https://pipeworx.io/packs/exoplanet-archive
- Changelog RSS feed: https://verifymcp.io/servers/pipeworx-io-exoplanet-archive/pipeworx-mcp-exoplanet-archive.xml
- Changelog JSON feed: https://verifymcp.io/servers/pipeworx-io-exoplanet-archive/pipeworx-mcp-exoplanet-archive/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/pipeworx-io-exoplanet-archive/pipeworx-mcp-exoplanet-archive.json
- HTML version of this page: https://verifymcp.io/servers/pipeworx-io-exoplanet-archive/pipeworx-mcp-exoplanet-archive