# Meteors (npm · @pipeworx/mcp-meteors)

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

- Trust score: 84/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-meteors/meteors-mcp.md), [page](https://verifymcp.io/servers/pipeworx-io-meteors/meteors-mcp)
- npm · `@pipeworx/mcp-meteors`: 84/100 (this document), [markdown](https://verifymcp.io/servers/pipeworx-io-meteors/pipeworx-mcp-meteors.md), [page](https://verifymcp.io/servers/pipeworx-io-meteors/pipeworx-mcp-meteors)

## Channel facts

- Registry: `npm`
- Package: `@pipeworx/mcp-meteors`
- 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-meteors).
  - 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**: 75/100
  - AI-judged instruction clarity (good).
  - Tool/resource definitions use about 302 tokens (~100/item across 3 items; 3 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**: 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 3 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 4 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 Meteors MCP server?

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

### Cursor

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

### VS Code

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

### Codex

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

### opencode

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

### OpenClaw

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

### Hermes

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

### Netclaw

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

### Vellum

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

### Other

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

## 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 84, 0)

- [functional regression] Security disclosure: unverified → fail

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

- [security improvement] Malware scan: unverified → pass

### 2026-11-03 (score 68, −13)

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

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

- [functional regression] Security disclosure: fail → unverified

### 2026-10-31 (score 81, 0)

- [functional regression] Security disclosure: unverified → fail

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

First indexed and scored.

## MCP tools (3)

### `get_fireballs` (~61 tokens)

Track recent meteor impacts and atmospheric explosions detected by US government sensors. Returns impact energy, radiated energy, velocity, altitude, and geographic location.

Input parameters:

- `limit` (number): Maximum number of fireball events to return (default 10, max 100).

### `get_close_approaches` (~70 tokens)

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.

Input parameters:

- `limit` (number): Maximum number of close approach records to return (default 10, max 50).

### `get_neo_feed` (~118 tokens)

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.

Input parameters:

- `end_date` (string, required): End date in YYYY-MM-DD format. Maximum 7-day range from start_date (e.g. "2025-01-07").
- `start_date` (string, required): Start date in YYYY-MM-DD format (e.g. "2025-01-01").

## Diagnostics

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

## Score history

- 2026-11-05: 84
- 2026-11-04: 84
- 2026-11-03: 68
- 2026-11-02: 81
- 2026-11-01: 81
- 2026-10-31: 81
- 2026-10-30: 81
- 2026-10-29: 81

## Common questions

### What is the Meteors MCP server?

Meteors is an MCP server listed in the public MCP registry as io.github.pipeworx-io/meteors. Meteors MCP, NASA fireball, near-Earth asteroid, and close approach data. This page covers its npm package (@pipeworx/mcp-meteors).

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

Meteors scores 84 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 Meteors MCP server expose?

Meteors exposes 3 tools: get_fireballs, get_close_approaches, get_neo_feed. Their descriptions and schemas cost roughly 249 tokens of context every time the server is loaded.

### Is the Meteors MCP server still maintained?

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

Meteors 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 Meteors MCP server?

VerifyMCP ran 16 checks on Meteors, 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-meteors
- Socket report: https://socket.dev/npm/package/@pipeworx/mcp-meteors
- Repository: https://github.com/pipeworx-io/mcp-meteors
- Website: https://pipeworx.io/packs/meteors
- Changelog RSS feed: https://verifymcp.io/servers/pipeworx-io-meteors/pipeworx-mcp-meteors.xml
- Changelog JSON feed: https://verifymcp.io/servers/pipeworx-io-meteors/pipeworx-mcp-meteors/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/pipeworx-io-meteors/pipeworx-mcp-meteors.json
- HTML version of this page: https://verifymcp.io/servers/pipeworx-io-meteors/pipeworx-mcp-meteors