# io.github.qso-graph/meteor-mcp (pypi · meteor-mcp)

Meteor scatter planning between two stations: showers, radiant geometry, live counts

- Trust score: 79/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-10-16

## Components

- pypi · `meteor-mcp`: 79/100 (this document), [markdown](https://verifymcp.io/servers/qso-graph-meteor-mcp/meteor-mcp.md), [page](https://verifymcp.io/servers/qso-graph-meteor-mcp/meteor-mcp)

## Channel facts

- Registry: `pypi`
- Package: `meteor-mcp`
- Version: `0.1.0`
- 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-10-16.

- **Supply Chain Security**: 100/100
  - No malware found by supply-chain analysis.
  - No known CVEs affecting this package version or its production dependencies.
  - Runs hatchling.build at install time, a recognised build step with no custom scripting around it.
  - 1 of 16 dependencies flagged as unhealthy.
- **Provenance & Transparency**: 97/100
  - Source repository is publicly reachable at the declared URL.
  - Cryptographically verified build provenance (signed, bound to qso-graph/meteor-mcp).
  - Clear OSI-approved license (GPL-3.0-or-later).
  - Actively maintained (last published 4 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 66/100
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 1070 tokens (~152/item across 7 items; 7 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 0/100
  - Stability not yet verified: not enough scan history yet (needs a 30-day window).
- **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.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 7 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 8 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a current MCP spec version (2026-07-28).

**Unverified: 1 category.** A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.

## Install

### How do I install the io.github.qso-graph/meteor-mcp server?

io.github.qso-graph/meteor-mcp runs locally as a PyPI package, launched with uvx meteor-mcp. 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 qso-graph-meteor-mcp -- uvx meteor-mcp
```

### Cursor

```json
{
  "mcpServers": {
    "qso-graph-meteor-mcp": {
      "command": "uvx",
      "args": [
        "meteor-mcp"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "qso-graph-meteor-mcp": {
      "command": "uvx",
      "args": [
        "meteor-mcp"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add qso-graph-meteor-mcp -- uvx meteor-mcp
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "qso-graph-meteor-mcp": {
      "type": "local",
      "command": [
        "uvx",
        "meteor-mcp"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add qso-graph-meteor-mcp --command uvx --arg meteor-mcp
```

### Hermes

```yaml
mcp_servers:
  qso-graph-meteor-mcp:
    command: "uvx"
    args: ["meteor-mcp"]
```

### Netclaw

```json
{
  "McpServers": {
    "qso-graph-meteor-mcp": {
      "Transport": "stdio",
      "Command": "uvx",
      "Arguments": [
        "meteor-mcp"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add qso-graph-meteor-mcp -t stdio -c uvx -a meteor-mcp
```

### Other

```json
{
  "mcpServers": {
    "qso-graph-meteor-mcp": {
      "command": "uvx",
      "args": [
        "meteor-mcp"
      ]
    }
  }
}
```

## 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-10-16 (score 79, +15)

- [security improvement] Malware scan: unverified → pass

### 2026-10-14 (score 64, +30)

- [security improvement] Injection markers: unverified → pass
- [security] First check of Judged manipulation: pass
- [security] Stability: Stability not yet verified: not enough scan history yet (needs a 30-day window).
- [functional improvement] Tool coverage: unverified → 100
- [functional improvement] MCP protocol: unverified → pass
- [functional] First check of Schema quality: fail
- [functional] First check of Destructive annotations: pass
- [functional] First check of Schema quality: fail
- [functional] First check of Schema quality: good
- [functional] First check of Tool coverage: 100
- [functional] First check of Tool coverage: 100

### 2026-10-13 (score 34, −15)

- [security regression] Malware scan: pass → unverified

### 2026-10-12 (score 49)

First indexed and scored.

## MCP tools (7)

### `meteor_window` (~474 tokens)

Meteor Window

When two stations can work each other by meteor scatter, and why.

Give both grid squares. The answer covers the path itself (is it even a
meteor-scatter distance), which shower is in play, and then hour by hour
whether the geometry can reflect — reported as no / marginal / good / best
with the reason that decided it.

Three things decide it, and radiant elevation is only one: the path length,
the radiant's elevation **at the path midpoint** (where the reflection
happens, not at either station), and the angle between the radiant and the
path. That last one is the one usually left out and the one that makes a
reflection geometrically possible at all — a trail reflects only where it
is tangent to the ellipsoid with both stations at its foci, so a radiant
broadside to the path works and one up- or down-path does not, at the very
same elevation.

Your own end can be left out when the host supplies it from the operator's
station profile — ADIF's `MY_GRIDSQUARE`, or `MY_LAT` and `MY_LON` when the
exact position is known. Those fields describe the **transmitting station**,
not where the operator is sitting, which is what makes a remote operation
come out right: the reflection geometry depends on where the antenna is.

Input parameters:

- `hours`: How far ahead to look. Default 12, at most 14 days.
- `my_grid`: Your locator. Omitted, it must come from your station profile.
- `my_lat`: Your latitude, if known exactly — preferred over a grid square, which is a rectangle this would otherwise have to take the centre of.
- `my_lon`: Your longitude.
- `shower`: Shower code, IAU number or name. Omitted, the one nearest its published peak is used and named in the answer.
- `step_minutes`: Sampling interval. Default 30.
- `their_grid`: The other station's Maidenhead locator, e.g. "EM12".
- `their_lat`: The other station's latitude, if known exactly.
- `their_lon`: The other station's longitude.
- `when`: UTC start, ISO 8601. Omitted, now.

### `meteor_showers` (~105 tokens)

Meteor Showers

Which showers are near their peak, closest first.

The IAU MDC publishes each maximum as a solar longitude rather than a date,
because solar longitude names the same point in the stream every year while
a date drifts. The longitude is converted here to the date it falls on in
the year asked about.

Input parameters:

- `limit`: How many to return. Default 12.
- `when`: UTC instant to rank around, ISO 8601. Omitted, now.

### `meteor_shower_info` (~105 tokens)

Meteor Shower Info

Every published solution for one shower, unaveraged.

The MDC carries several solutions per shower, each from a different study,
with slightly different radiants and speeds. All of them are returned. None
is blended, because the average of two published radiants is a third that
nobody published and no paper stands behind.

Input parameters:

- `shower` (string, required): Code, IAU number or name — "PER", "7", "Perseids", "perseid".

### `meteor_activity` (~103 tokens)

Meteor Activity

How many meteors the Global Meteor Network has actually confirmed today.

A count of observed trajectories broken down by shower — not a flux
density, which is a different quantity GMN computes separately. The file is
written during the day, so an early read covers a partial day; the
generation time is in the answer.

This reads the network. Attribution is a condition of GMN's CC BY 4.0
licence and is carried in the result.

### `meteor_fireballs` (~71 tokens)

Meteor Fireballs

Recent fireballs recorded by NASA CNEOS.

Bolides bright enough to be detected from orbit — the "did anyone else see
that" events, not a meteor rate. Reads the network.

Input parameters:

- `limit`: How many of the most recent to return. Default 10, at most 100.

### `meteor_source_info` (~80 tokens)

Meteor Source Info

Where every number in this server comes from, and how to cite it.

The shower list is the IAU Meteor Data Center's, carried in the package
with its checksum so the exact edition served is identifiable. The live
sources are named with their licences. Nothing here is this project's own
measurement, and the citations are the owners' own.

### `get_version_info` (~23 tokens)

Get Version Info

This server's version and the edition of the shower list it carries.

## Diagnostics

Captured diagnostic sections: Provenance, Install scripts, Dependencies. The full working is on the page: https://verifymcp.io/servers/qso-graph-meteor-mcp/meteor-mcp#diagnostics

## Score history

- 2026-10-16: 79
- 2026-10-15: 64
- 2026-10-14: 64
- 2026-10-13: 34
- 2026-10-12: 49

## Common questions

### What is the io.github.qso-graph/meteor-mcp server?

io.github.qso-graph/meteor-mcp is listed in the public MCP registry as io.github.qso-graph/meteor-mcp. Meteor scatter planning between two stations: showers, radiant geometry, live counts. This page covers its PyPI package (meteor-mcp).

### Is the io.github.qso-graph/meteor-mcp server safe to use?

io.github.qso-graph/meteor-mcp scores 79 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 16 October 2026. 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 io.github.qso-graph/meteor-mcp server expose?

io.github.qso-graph/meteor-mcp exposes 7 tools: meteor_window, meteor_showers, meteor_shower_info, meteor_activity, meteor_fireballs, and 2 more. Their descriptions and schemas cost roughly 961 tokens of context every time the server is loaded.

### Is the io.github.qso-graph/meteor-mcp server still maintained?

io.github.qso-graph/meteor-mcp is still listed as active in the MCP registry. We last reached this channel on 16 October 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 io.github.qso-graph/meteor-mcp server under?

io.github.qso-graph/meteor-mcp declares the GPL-3.0-or-later licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.

## Links

- PyPI project: https://pypi.org/project/meteor-mcp/
- Socket report: https://socket.dev/pypi/package/meteor-mcp
- Repository: https://github.com/qso-graph/meteor-mcp
- Changelog RSS feed: https://verifymcp.io/servers/qso-graph-meteor-mcp/meteor-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/qso-graph-meteor-mcp/meteor-mcp.json
- HTML version of this page: https://verifymcp.io/servers/qso-graph-meteor-mcp/meteor-mcp