Meteors

Meteors MCP — NASA fireball, near-Earth asteroid, and close approach data

Open source Repository Open in the app JSON README (API)

About

Meteors MCP — NASA fireball, near-Earth asteroid, and close approach data

Details

Kind: MCP servers
Topic: No topic detected
Publisher: pipeworx-io
Origin: official
Category: ferramentas
Transport: http
Version: 0.1.0
Last push: 2026-08-26T17:22:17Z
Repository state: ativo
Language: TypeScript
License: MIT
Added: 2026-08-29 04:01:08
Updated: 2026-08-29 04:01:08
Origin id: io.github.pipeworx-io/meteors

README

# mcp-meteors

Meteors MCP — NASA fireball, near-Earth asteroid, and close approach data

Part of [Pipeworx](https://pipeworx.io) — an MCP gateway connecting AI agents to 1476+ live data sources.

## Tools

| Tool | Description |
|------|-------------|
| `get_fireballs` | Track recent meteor impacts and atmospheric explosions detected by US government sensors. Returns impact energy, radiated energy, velocity, altitude, and geographic location. |
| `get_close_approaches` | Find near-Earth asteroids making close approaches within 0.05 AU. Returns object name, approach date, miss distance, velocity, and diameter to identify potentially hazardous objects. |
| `get_neo_feed` | Get near-Earth objects passing Earth during a date range (e.g., "2024-01-01" to "2024-12-31"). Returns asteroid names, sizes, velocities, miss distances, and hazard status. |

## Quick Start

Add to your MCP client (Claude Desktop, Cursor, Windsurf, etc.):

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

### What this endpoint actually serves

`tools/list` at `https://gateway.pipeworx.io/meteors/mcp` returns the tools in the table
above **plus the shared Pipeworx meta-tools** — `ask_pipeworx`,
`discover_tools`, `search_within`, `remember`/`recall` and the rest of the
gateway-wide set. So the tool count you see is larger than this table: a
single-pack endpoint currently lists roughly 30 shared tools alongside the
pack's own. The connection's `initialize` response states its exact scope, and
is the authoritative answer for a given day.

This is deliberate, not multiplexing by accident. The meta-tools are what let a
scoped connection answer a question this pack does not cover — via
`ask_pipeworx`, which routes across the whole catalog — without you adding a
second MCP server. There is currently no way to mount a pack endpoint without
them; if the extra schemas cost you more context than the routing is worth,
connect to the full gateway once rather than to several pack endpoints.

Or connect to the full Pipeworx gateway to get every pack's tools listed
directly, instead of just this one's:

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

Both URLs reach the same gateway and the same 1476+ data sources. The
only difference is which pack's tools are listed **directly**; `ask_pipeworx`
reaches all of them from either one.

## Using with ask_pipeworx

Instead of calling tools directly, you can ask questions in plain English —
this works on the pack endpoint above as well as on the full gateway:

```
ask_pipeworx({ question: "your question about Meteors data" })
```

The gateway picks the right tool and fills the arguments automatically.

## More

- [Docs and guides](https://pipeworx.io/docs)
- [pipeworx.io](https://pipeworx.io)

## License

MIT