io.github.qso-graph/meteor-mcp
PYPI · METEOR-MCP
Meteor scatter planning between two stations: showers, radiant geometry, live counts
Available components
Last scanned (20 hours ago)
Scores higher than 80% of PyPI servers
Category Health and Science
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. How we score → Why this is hard to score →
Supply Chain Security100
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- Runs hatchling.build at install time, a recognised build step with no custom scripting around it. View diagnostics → Pass
- 1 of 16 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency97
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to qso-graph/meteor-mcp). View diagnostics → Pass
- Clear OSI-approved license (GPL-3.0-or-later).Pass
- Actively maintained (last published 4 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability66
- AI-judged instruction clarity (good).Pass
- 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. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 7 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 8 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
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.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 16 Oct 26 +15
- Malware scan: unverified → pass ▲ security
- 14 Oct 26 +30
- 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). security
- Tool coverage: unverified → 100 ▲ functional
- 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 functional
- 13 Oct 26 −15
- Malware scan: pass → unverified ▼ security
- 12 Oct 26 49
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 16 Oct 2026 · Analysed pypi/meteor-mcp@0.1.0
Provenance Verified
A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.
| Result | Verified |
|---|---|
| Ecosystem | pypi |
| Reason | Verified |
| Discovered via | Registry attestation endpoint |
| Source repo | qso-graph/meteor-mcp |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/qso-graph/meteor-mcp/.github/workflows/publish.yml@refs/heads/main |
| Rekor log index | 3215940413 |
| Predicate type | PyPI publish attestation https://docs.pypi.org/attestations/publish/v1 |
| Subject digest | sha256:73b2c03030a5eab50577766a5a67282c8d6d2474f339974883905f0447aaf82d |
Background: How many MCP packages publish verified provenance →
Install scripts 1 script
| Hook | Tier | Command |
|---|---|---|
| build_backend | allowlisted | hatchling.build |
Background: Why install scripts are a supply-chain risk →
Dependencies 16 packages
| Packages resolved | 16 |
|---|---|
| Stale | 1 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
get_version_info Get Version Info ~23
This server's version and the edition of the shower list it carries.
Input schema present but exposes no named parameters.
Structured output declared, but exposes no named fields.
No examples provided.
meteor_activity Meteor Activity ~103
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.
Input schema present but exposes no named parameters.
Structured output declared, but exposes no named fields.
No examples provided.
meteor_fireballs Meteor Fireballs ~71
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.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | – | – | How many of the most recent to return. Default 10, at most 100. |
Structured output declared, but exposes no named fields.
No examples provided.
meteor_shower_info Meteor Shower Info ~105
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.
| Name | Type | Req | Description |
|---|---|---|---|
| shower | string | yes | Code, IAU number or name — "PER", "7", "Perseids", "perseid". |
Structured output declared, but exposes no named fields.
No examples provided.
meteor_showers Meteor Showers ~105
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.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | – | – | How many to return. Default 12. |
| when | – | – | UTC instant to rank around, ISO 8601. Omitted, now. |
Structured output declared, but exposes no named fields.
No examples provided.
meteor_source_info Meteor Source Info ~80
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.
Input schema present but exposes no named parameters.
Structured output declared, but exposes no named fields.
No examples provided.
meteor_window Meteor Window ~474
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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. |
Structured output declared, but exposes no named fields.
No examples provided.
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.
pypi · meteor-mcp
claude mcp add qso-graph-meteor-mcp -- uvx meteor-mcp
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.