Log inSubmit server
Jpl Ssd logo

Jpl Ssd

Queries NASA/JPL small-body, close-approach, impact-risk, and fireball data through MCP.

InstallRepositoryWebsite
Full README Compare alternatives Embed widget Claim this listing

Install Jpl Ssd

Pick your client, then add it in one click or paste the config.

STDIONode.js
~/Library/Application Support/Claude/claude_desktop_config.json
claude_desktop_config.json
{
  "mcpServers": {
    "jpl-ssd": {
      "command": "npx",
      "args": [
        "-y",
        "@pipeworx/mcp-jpl-ssd"
      ]
    }
  }
}

Settings → Developer → Edit Config, merge this into mcpServers, then fully quit and reopen Claude Desktop.

We couldn’t confirm it starts correctly

The install command started, but didn't respond the way we expected when we tried to talk to it.

npx -y @pipeworx/mcp-jpl-ssd

initialize succeeded but no response to tools/list.

This is an experimental automated check and can have false negatives — missing environment variables, a slow cold install, etc. It doesn’t necessarily mean something’s wrong. Last checked Today.

Overview

Jpl Ssd MCP server connects AI agents to NASA/JPL Solar System Dynamics and CNEOS data. It provides tools for asteroid and comet parameters, near-Earth close approaches, Sentry impact risk, and recent atmospheric fireballs. The tools are keyless and can run through the Pipeworx gateway or as a local stdio package. Reach for it when an agent needs structured solar-system and planetary-defense data.

Use cases

  • Look up asteroid or comet orbital parameters
  • Find near-Earth approaches within a date range
  • Check Sentry impact risk for an asteroid
  • Review recent atmospheric fireball observations

Key features

  • NASA/JPL small-body lookups
  • CNEOS close-approach data
  • Sentry impact-risk reports
  • Recent fireball observations
  • Keyless access
  • Local stdio and gateway modes

Tools4

What Jpl Ssd lets your agent do. Expand a tool for its parameters.

Self-reported~228 tokens of context

Security & health

What it can reach and how reliably it runs — from our own checks, not the maintainer’s claims.

ActiveLast checked 3d ago

Recent health check succeeded.

6/6 checks healthy over the last 35d

Supply-chain signal

No high-severity advisories surfaced by our automated scan.

Critical 0High 0Medium 0Low 0

Scanned 15d ago via OSV.dev · @pipeworx/mcp-jpl-ssd (npm)

Adoption & maintenance

Factual signals from GitHub, npm, and our automated checks — not a rating.

npm downloads444Package downloads in the last 30 days.
Last commit27d agoMost recent push to the default branch.
Install checkInconclusiveStarted but did not complete the MCP handshake in our test.
Tools exposed4Callable tools this server registers over MCP.
Directory activity1 viewsConfig copies, upvotes, and views on AllMCPs.

How Jpl Ssd works

What Jpl Ssd does

Jpl Ssd MCP server exposes NASA and JPL datasets for small bodies and near-Earth objects through the Model Context Protocol. Its four pack-specific tools cover object properties, Earth close approaches, asteroid impact risk, and recently detected fireballs. No API key is required for these tools.

The server is suited to agents that need factual astronomy or planetary-defense data rather than general-purpose space calculations. Results include structured measurements such as orbital elements, miss distance, velocity, object size indicators, impact probabilities, and event energy.

How it works

The service can be reached through a scoped Pipeworx gateway endpoint at https://gateway.pipeworx.io/jpl-ssd/mcp, or through the full gateway at https://gateway.pipeworx.io/mcp. The scoped endpoint lists this pack's tools directly, but it also exposes shared Pipeworx meta-tools. Those tools can route questions to other catalog sources through ask_pipeworx.

A local installation is also available as an MCP process communicating over standard input and output. The local process exposes only the Jpl Ssd tools and does not include the gateway's shared meta-tools or cross-catalog routing. The same capabilities can also be called over HTTP through the gateway's /v1/tools/{tool} endpoints.

Setup and configuration

For an MCP client that supports remote endpoints, add the scoped URL as an MCP server. The README gives configuration examples for Claude Desktop, Cursor, and Windsurf. A full-gateway configuration is an alternative when an agent should access every Pipeworx source directly.

For local stdio use, run the package with npx -y @pipeworx/mcp-jpl-ssd and configure the client with the npx command and package argument. This mode does not require a Pipeworx account or a gateway round trip. The gateway also allows initial calls without an account.

No environment variables or API credentials are documented as required.

Tools and capabilities

  • get_small_body accepts an asteroid or comet name or designation. It returns orbital and physical information, including eccentricity, semi-major axis, MOID, diameter, albedo, and NEO or PHA flags.
  • close_approaches searches near-Earth approaches within a date range. Results include Earth miss distance in AU, relative velocity in km/s, and absolute magnitude as a size proxy.
  • impact_risk uses NASA/JPL CNEOS Sentry data. With a designation, it returns an object's cumulative impact probability, Palermo and Torino scale values, diameter, and impact window. Without one, it can list tracked objects above an impact-probability threshold.
  • recent_fireballs returns recent atmospheric fireball or bolide observations from U.S. Government sensors, including date, location, altitude, velocity, and radiated and total impact energy in kilotons of TNT.

Limitations and notes

The gateway and local modes expose different tool scopes. A gateway connection adds shared Pipeworx tools, while the standalone process is limited to this pack. The exact gateway tool list can change; its initialize response is authoritative for the active connection. Data comes from the referenced NASA/JPL services, so results reflect those sources and their available records.

Read the full README View source on GitHub

Reviews

No reviews yet — be the first to share how it worked for you.

Frequently Asked Questions about Jpl Ssd

Jpl Ssd is an MCP server that connects AI agents to NASA/JPL Solar System Dynamics and CNEOS data. Its main tools look up asteroid and comet properties, list near-Earth close approaches, report Sentry impact risk, and retrieve recent fireball observations. The tools require no API keys.

Install it locally by configuring your MCP client to run `npx -y @pipeworx/mcp-jpl-ssd`. This uses the standalone stdio package, requires no Pipeworx account, and exposes only the pack's four tools.

Yes, Jpl Ssd works with Cursor through the remote MCP endpoint. Add `https://gateway.pipeworx.io/jpl-ssd/mcp` to Cursor's MCP configuration, or use the local `npx` stdio configuration.

Call the gateway's tool endpoint with a JSON POST request, such as `/v1/tools/get_small_body` with `{"name":"Ceres"}`. The gateway also provides GET requests for inspecting a tool.

No, the four Jpl Ssd tools are keyless.

Related MCP servers

All in Aerospace & Astrodynamics All alternatives
Add a badge to your READMEShow it’s listed — live SVG, Markdown or HTML.

AllMCPs Directory Badge

Full Badge Customizer

Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.

Badge Style:
Live Dynamic SVG PreviewJpl Ssd AllMCPs Directory Badge
Markdown (GitHub README)
[![AllMCPs](https://allmcps.com/api/badge/jpl-ssd?style=directory)](https://allmcps.com/mcp/jpl-ssd)
HTML Embed
<a href="https://allmcps.com/mcp/jpl-ssd"><img src="https://allmcps.com/api/badge/jpl-ssd?style=directory" alt="Jpl Ssd on AllMCPs" /></a>