Meteors logo

Meteors

Meteors provides MCP tools for NASA fireballs, near-Earth objects, and close asteroid approaches.

Install Meteors

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": {
    "meteors": {
      "command": "npx",
      "args": [
        "-y",
        "@pipeworx/mcp-meteors"
      ]
    }
  }
}

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

Automated check passed— started and listed 3 tools correctly (5d ago).

Overview

Meteors MCP server exposes NASA fireball, near-Earth asteroid, and close-approach data through three MCP tools. It can run through the Pipeworx gateway over streamable HTTP or locally as a stdio package with npx. Use it to inspect recent atmospheric events, identify close asteroid passes, or query near-Earth objects across a date range. The gateway also provides shared Pipeworx tools, while the local package exposes only the Meteors tools.

Use cases

  • Track recent meteor impacts and atmospheric explosions
  • Find asteroids approaching Earth within 0.05 AU
  • Query near-Earth objects across a date range
  • Summarize asteroid size, velocity, distance, and hazard fields

Key features

  • Recent fireball and atmospheric explosion data
  • Near-Earth asteroid close-approach searches
  • Date-range NEO feeds
  • Velocity, energy, altitude, and location fields
  • Hosted gateway and local stdio modes
  • Optional Pipeworx catalog routing

Tools3

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

Verified live~299 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 1d ago

Recent health check succeeded.

7/7 checks healthy over the last 39d

What it can do

From the 3 tools this server returned when we ran it.

Read-only tools · 3
Network at startup3 connections
Files written at startupNone
Install scriptsNone
npm provenanceSigned build
Package age184 days
Maintainers1

Observed 2026-10-17 in an isolated sandbox. A description of reach, not a security audit.

Supply-chain signal

No high-severity advisories surfaced by our automated scan.

Critical 0High 0Medium 0Low 0

Scanned 13d ago via OSV.dev · @pipeworx/mcp-meteors (npm)

Adoption & maintenance

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

npm downloads459Package downloads in the last 30 days.
Last commit26d agoMost recent push to the default branch.
Availability100%Our rolling endpoint + install checks that succeeded.
Install checkPassedOur sandbox started it and listed its tools.
Tools exposed3Callable tools this server registers over MCP.
Directory activity2 viewsConfig copies, upvotes, and views on AllMCPs.

How Meteors works

What Meteors MCP server does

The Meteors MCP server gives AI agents structured access to three types of space-object data: recent fireballs and atmospheric explosions, near-Earth asteroid close approaches, and near-Earth objects observed during a specified date range. The returned fields support basic event review and risk-oriented filtering, including energy, speed, altitude, location, miss distance, diameter, size, and hazard status where available.

Its data scope is aimed at questions such as which meteor events were recently detected, which asteroids will pass within a selected threshold, and which near-Earth objects are recorded between two dates. The listing identifies the fireball observations as detections from US government sensors and describes the asteroid information as NASA data.

Tools and capabilities

The Meteors MCP server exposes these tools:

  • get_fireballs retrieves recent meteor impacts and atmospheric explosions. Results include impact energy, radiated energy, velocity, altitude, and geographic location.
  • get_close_approaches finds near-Earth asteroids making approaches within 0.05 AU. Results can include the object name, approach date, miss distance, velocity, and diameter.
  • get_neo_feed returns near-Earth objects passing Earth during a supplied date range, such as 2024-01-01 through 2024-12-31. Results include asteroid names, sizes, velocities, miss distances, and hazard status.

These tools are suitable for agent workflows that need to compare objects, summarize observations, or answer date- and distance-based questions. They do not imply prediction beyond the fields returned by the underlying data.

How it works

The hosted endpoint is https://gateway.pipeworx.io/meteors/mcp. An MCP client connects to that URL and discovers the available tools. A scoped gateway connection lists the three Meteors tools plus shared Pipeworx meta-tools, including routing and discovery functions. The exact tool scope is reported by the connection's initialize response and may be treated as authoritative for that session.

The same gateway also has a full endpoint at https://gateway.pipeworx.io/mcp. The hosted Meteors endpoint and the full endpoint reach the same gateway and data sources; the difference is which pack tools are listed directly. The gateway's ask_pipeworx function can route a natural-language request to tools across the catalog from either endpoint.

Meteors MCP server tools can also be called without an MCP client through the gateway's HTTP tool interface. For example, POST https://gateway.pipeworx.io/v1/tools/get_fireballs accepts JSON input.

Setup and configuration

For a hosted connection, add the gateway URL to an MCP client's server configuration:

config.json
{
  "mcpServers": {
    "meteors": {
      "url": "https://gateway.pipeworx.io/meteors/mcp"
    }
  }
}

The README names Claude Desktop, Cursor, and Windsurf as compatible client examples. It states that initial gateway calls do not require an account.

For local use, run the package as a stdio server with npx:

config.json
{
  "mcpServers": {
    "meteors": {
      "command": "npx",
      "args": ["-y", "@pipeworx/mcp-meteors"]
    }
  }
}

Running npx -y @pipeworx/mcp-meteors directly starts the process for a basic launch check. The local process communicates over stdin and stdout and exposes only the three pack tools, without gateway meta-tools or ask_pipeworx routing.

Limitations and notes

The gateway and local modes differ in their discovered tool sets. Gateway connections add shared Pipeworx schemas, which can increase context usage; the local package avoids those additional tools but does not provide cross-catalog routing. The documentation does not specify authentication settings, custom environment variables, rate limits, or data refresh intervals.

The close-approach query is explicitly limited to objects within 0.05 AU, while the NEO feed requires a date range. Consumers should handle the returned measurements as source data rather than treating the tool as an independent hazard assessment system.

The Meteors MCP server is released under the MIT license.

Reviews

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

Frequently Asked Questions about Meteors

Meteors is an MCP server that connects AI agents to NASA fireball, near-Earth asteroid, and close-approach data. Its main tools are get_fireballs for atmospheric events, get_close_approaches for objects within 0.05 AU, and get_neo_feed for near-Earth objects during a chosen date range.

Install it locally by configuring an MCP client to run npx with @pipeworx/mcp-meteors. The package communicates over stdin and stdout and does not require a Pipeworx gateway account.

Connect an MCP client to https://gateway.pipeworx.io/meteors/mcp. The README gives Claude Desktop, Cursor, and Windsurf as examples, and the hosted gateway can be added with a URL-based server configuration.

Yes, Meteors works locally without a gateway account through its npx stdio package. The local mode exposes the three Meteors tools only, while the hosted gateway also adds shared Pipeworx meta-tools.

Call get_close_approaches to find objects passing within 0.05 AU, or call get_neo_feed with a start and end date to retrieve near-Earth objects during that period. Results can include distance, velocity, size or diameter, and hazard status.

Related MCP servers

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 PreviewMeteors AllMCPs Directory Badge
Markdown (GitHub README)
[![AllMCPs](https://allmcps.com/api/badge/meteors?style=directory)](https://allmcps.com/mcp/meteors)
HTML Embed
<a href="https://allmcps.com/mcp/meteors"><img src="https://allmcps.com/api/badge/meteors?style=directory" alt="Meteors on AllMCPs" /></a>