# Nasa (npm · @pipeworx/mcp-nasa)

NASA MCP — wraps NASA Open APIs (api.nasa.gov)

- Trust score: 77/100 (medium)
- Change this week: −2
- 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-nasa/nasa-mcp.md), [page](https://verifymcp.io/servers/pipeworx-io-nasa/nasa-mcp)
- npm · `@pipeworx/mcp-nasa`: 77/100 (this document), [markdown](https://verifymcp.io/servers/pipeworx-io-nasa/pipeworx-mcp-nasa.md), [page](https://verifymcp.io/servers/pipeworx-io-nasa/pipeworx-mcp-nasa)

## Channel facts

- Registry: `npm`
- Package: `@pipeworx/mcp-nasa`
- 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**: 71/100
  - Repository presence not verified: we could not reach the forge to check. This is a gap on our side, not a finding about the repository.
  - Cryptographically verified build provenance (signed, bound to pipeworx-io/mcp-nasa).
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 2 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 64/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 1990 tokens (~221/item across 9 items; 9 tools + 0 resources), over budget; trim descriptions and params.
  - 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**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% 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 9 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 10 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 Nasa MCP server?

Nasa runs locally as an npm package, launched with npx -y @pipeworx/mcp-nasa. 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-nasa -- npx -y @pipeworx/mcp-nasa
```

### Cursor

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

### VS Code

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

### Codex

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

### opencode

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

### OpenClaw

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

### Hermes

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

### Netclaw

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

### Vellum

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

### Other

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

## 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 77, −5)

- [security regression] Provenance: pass → unverified

### 2026-11-04 (score 82, +16)

- [security improvement] Malware scan: unverified → pass

### 2026-11-03 (score 66, −15)

- [security regression] Malware scan: pass → unverified
- [functional] Package version: 0.2.0 → 0.2.1

### 2026-11-02 (score 81, +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.

### 2026-10-31 (score 80, +1)

- [functional regression] Security disclosure: unverified → fail

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

First indexed and scored.

## MCP tools (9)

### `get_apod` (~113 tokens)

Get the NASA Astronomy Picture of the Day with explanation. Optionally specify a date. Example: get_apod({ date: "2024-01-15", _apiKey: "DEMO_KEY" })

Input parameters:

- `_apiKey` (string): NASA API key (optional, defaults to DEMO_KEY — get a free key at api.nasa.gov)
- `date` (string): Date in YYYY-MM-DD format (optional, defaults to today). Range: 1995-06-16 to today.

### `get_asteroids` (~132 tokens)

Get near-Earth asteroids approaching within a date range (max 7 days). Returns size, velocity, and miss distance. Example: get_asteroids({ start_date: "2024-01-01", end_date: "2024-01-07", _apiKey: "DEMO_KEY" })

Input parameters:

- `_apiKey` (string): NASA API key (optional, defaults to DEMO_KEY)
- `end_date` (string, required): End date in YYYY-MM-DD format (max 7 days after start)
- `start_date` (string, required): Start date in YYYY-MM-DD format

### `get_mars_photos` (~336 tokens)

"Show me photos from the Mars rover" / "Perseverance images from sol 1000" / "latest pictures from Mars" — raw images from NASA's Perseverance rover (Mars 2020), straight off the mars.nasa.gov feed. Filter by Martian sol and by camera. Returns image URLs at four resolutions, the sol, the UTC and Mars-local capture times, and the camera instrument. Keyless. Covers Perseverance only — Curiosity, Opportunity and Spirit have no live public image feed. Example: get_mars_photos({ sol: 1000, camera: "NAVCAM_LEFT" })

Input parameters:

- `camera` (string): Camera instrument, exact: "NAVCAM_LEFT", "NAVCAM_RIGHT", "FRONT_HAZCAM_LEFT_A", "FRONT_HAZCAM_RIGHT_A", "REAR_HAZCAM_LEFT", "REAR_HAZCAM_RIGHT", "MCZ_LEFT"/"MCZ_RIGHT" (Mastcam-Z), "SHERLOC_WATSON",…
- `limit` (number): Max images to return (default 20, max 100).
- `sol` (number): Martian sol (mission day) to retrieve images from, e.g. 1000. Perseverance landed on sol 0 (2021-02-18) and is past sol 1900. Omit for the most recent images.

### `search_nasa_images` (~148 tokens)

Search the NASA Image and Video Library for images/videos of any subject — planets, missions, astronauts, launches, galaxies, etc. PREFER for "NASA photos of Jupiter", "images of the Apollo 11 mission", "pictures of a nebula". Returns title, description, date, NASA ID, media type, and a thumbnail URL. Keyless.

Input parameters:

- `limit` (number): Max results to return (default 10, max 50).
- `media_type` (string): Optional filter: "image", "video", or "audio".
- `query` (string, required): Search terms, e.g. "jupiter", "apollo 11", "crab nebula".

### `get_solar_flares` (~143 tokens)

Get recent solar flare events from NASA DONKI space-weather data. Returns each flare's class (e.g. C4.0, M1.8, X1.2), begin/peak/end times, source region, and active region number. Use for "recent solar flares", "is there solar activity / a solar storm", space-weather questions.

Input parameters:

- `_apiKey` (string): NASA API key (optional, defaults to DEMO_KEY)
- `end_date` (string): End date YYYY-MM-DD (optional; default today).
- `start_date` (string): Start date YYYY-MM-DD (optional; default ~30 days ago).

### `donki_cme` (~282 tokens)

"Was there a coronal mass ejection this week?" / "is a CME heading for Earth?" — coronal mass ejections catalogued by NASA DONKI, the space-weather event database run by NASA's Community Coordinated Modeling Center. AUTHORITATIVE for CME occurrence and geometry: returns each eruption's start time, the instruments that saw it, the analysts' note describing the source region, and for analysed events the modelled speed in km/s, the direction (latitude/longitude on the solar disk), half-angle width and whether the analysis is the most accurate available. A CME is the thing that causes an aurora or a satellite drag event two or three days later, so speed plus direction is what says whether it will reach Earth.

Input parameters:

- `_apiKey` (string): NASA API key (optional, defaults to DEMO_KEY)
- `end_date` (string): End date YYYY-MM-DD (optional; defaults to today).
- `limit` (number): Max events to return (default 50, max 200).
- `min_speed_km_s` (number): Only return CMEs whose best analysis measured at least this speed in km/s. ~500 is fast, ~1000+ is a major event.
- `start_date` (string): Start date YYYY-MM-DD (optional; DONKI defaults to ~30 days ago).

### `donki_geomagnetic_storms` (~266 tokens)

"Was there a geomagnetic storm?" / "will there be an aurora tonight?" / "how strong was the Kp index?" — geomagnetic storm events from NASA DONKI, each with the full series of observed Kp index readings and their timestamps. AUTHORITATIVE for whether Earth's magnetic field was actually disturbed, as opposed to whether a flare happened: Kp 5 is a minor storm, Kp 7 puts aurora over the northern US and northern Europe, Kp 8-9 is severe. Also returns the CMEs and shocks DONKI linked to each storm, so you can trace a storm back to the eruption that caused it.

Input parameters:

- `_apiKey` (string): NASA API key (optional, defaults to DEMO_KEY)
- `end_date` (string): End date YYYY-MM-DD (optional; defaults to today).
- `limit` (number): Max storms to return (default 50, max 200).
- `min_kp` (number): Only return storms whose peak observed Kp reached at least this value (5 = minor storm, 7 = strong, 9 = extreme).
- `start_date` (string): Start date YYYY-MM-DD (optional; DONKI defaults to ~30 days ago).

### `donki_solar_energetic_particles` (~200 tokens)

Solar energetic particle (SEP) events from NASA DONKI — bursts of high-energy protons arriving at Earth after a flare or CME. These are the events behind radiation warnings for polar airline routes, astronaut EVA holds and satellite single-event upsets. Returns the event time, the detecting instruments and energy channels (e.g. "GOES-P: SEISS >10 MeV"), and the flare or CME DONKI linked as the source.

Input parameters:

- `_apiKey` (string): NASA API key (optional, defaults to DEMO_KEY)
- `end_date` (string): End date YYYY-MM-DD (optional; defaults to today).
- `limit` (number): Max events to return (default 50, max 200).
- `start_date` (string): Start date YYYY-MM-DD (optional; DONKI defaults to ~30 days ago). SEP events are rare — a year-wide window is often the right query.

### `donki_notifications` (~319 tokens)

"What is the current space weather forecast?" — the alerts, watches, warnings and weekly summary reports NASA DONKI issues to spacecraft operators. This is the narrative layer over the event catalogues: a human forecaster's text saying what happened, what is expected and what the impact is. Filter by message type (alert, watch, warning, summary) or by event class (CME, flare, geomagnetic storm, SEP, radiation belt enhancement).

Input parameters:

- `_apiKey` (string): NASA API key (optional, defaults to DEMO_KEY)
- `end_date` (string): End date YYYY-MM-DD (optional; defaults to today).
- `include_body` (boolean): Include the full message text (default true). Set false for a compact index — these bodies are long.
- `limit` (number): Max messages to return (default 20, max 100).
- `message_type` (string): Filter the returned rows by the DONKI messageType field: "Alert", "Watch", "Warning" or "Report". Applied after fetching.
- `start_date` (string): Start date YYYY-MM-DD (optional; DONKI defaults to ~30 days ago).
- `type` (string): Message class: "all" (default), "FLR" (flare), "SEP", "CME", "IPS" (interplanetary shock), "MPC" (magnetopause crossing), "GST" (geomagnetic storm), "RBE" (radiation belt enhancement), "report" (week…

## Diagnostics

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

## Score history

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

## Common questions

### What is the Nasa MCP server?

Nasa is an MCP server listed in the public MCP registry as io.github.pipeworx-io/nasa. NASA MCP, wraps NASA Open APIs (api.nasa.gov). This page covers its npm package (@pipeworx/mcp-nasa).

### Is the Nasa MCP server safe to use?

Nasa scores 77 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 Nasa MCP server expose?

Nasa exposes 9 tools: get_apod, get_asteroids, get_mars_photos, search_nasa_images, get_solar_flares, and 4 more. Their descriptions and schemas cost roughly 1,939 tokens of context every time the server is loaded.

### Is the Nasa MCP server still maintained?

Nasa 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 Nasa MCP server under?

Nasa declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.

## Links

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