io.github.qso-graph/eme-mcp
PYPI · EME-MCP
EME prediction for amateur radio: moon windows, path loss and degradation, computed locally
Available components
Last scanned (4 hours ago)
Scores higher than 82% of PyPI servers
Category Maps and Location
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 15 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/eme-mcp). View diagnostics → Pass
- Clear OSI-approved license (GPL-3.0-or-later).Pass
- Actively maintained (last published 5 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability71
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 480 tokens (~96/item across 5 items; 5 tools + 0 resources), lean.Pass
- 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 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 6 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.
- 13 Oct 26 +46
- Injection markers: unverified → pass ▲ security
- Malware scan: 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: pass functional
- First check of Schema quality: good functional
- First check of Tool coverage: 100 functional
- First check of Tool coverage: 100 functional
- 12 Oct 26 34
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 17 Oct 2026 · Analysed pypi/eme-mcp@0.1.1
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/eme-mcp |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/qso-graph/eme-mcp/.github/workflows/publish.yml@refs/heads/main |
| Rekor log index | 3212995120 |
| Predicate type | PyPI publish attestation https://docs.pypi.org/attestations/publish/v1 |
| Subject digest | sha256:576b0689be4538daf1bbe90a8237520d1e5edf2b88d62edefed734bd380ffc61 |
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 15 packages
| Packages resolved | 15 |
|---|---|
| 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 →
eme_calendar Eme Calendar ~39
The least degraded days ahead — when the moon is nearest.
| Name | Type | Req | Description |
|---|---|---|---|
| days | – | – | How far ahead to look. Default 30, at most 365. |
Structured output declared, but exposes no named fields.
No examples provided.
eme_degradation Eme Degradation ~59
How much worse than the best case the moon is, now or at a given time.
| Name | Type | Req | Description |
|---|---|---|---|
| locator | – | – | Your grid square, for a topocentric range. Optional. |
| when | – | – | UTC time (ISO 8601). Default now. |
Structured output declared, but exposes no named fields.
No examples provided.
eme_moon_window Eme Moon Window ~138
Where the moon is from a grid square, and when both ends of a schedule can see it.
| Name | Type | Req | Description |
|---|---|---|---|
| hours | – | – | How far ahead to look. Default 24, at most 336 (14 days). |
| locator | string | yes | Maidenhead locator, e.g. DN13 or DN13la. |
| other_locator | – | – | A second station's locator. Given one, the answer also carries the mutual window — the rows where the moon is above the horizon at both ends, which is the only time a contact is possible. |
| step_minutes | – | – | Sampling interval. Default 30, at least 1. |
Structured output declared, but exposes no named fields.
No examples provided.
eme_path_loss Eme Path Loss ~133
What the path to the moon and back costs, now or at a given time.
| Name | Type | Req | Description |
|---|---|---|---|
| band | – | – | 2m, 70cm or 23cm. Ignored if frequency_mhz is given. |
| frequency_mhz | – | – | An exact frequency, for a band this does not name. |
| locator | – | – | Your grid square. Given one, the range is topocentric — from where you are, not from the Earth's centre, which differs by up to about 1.7% as the moon rises and sets. |
| when | – | – | UTC time (ISO 8601). Default now. |
Structured output declared, but exposes no named fields.
No examples provided.
get_version_info Get Version Info ~25
Get eme-mcp's version and the ephemeris series it computes from.
Input schema present but exposes no named parameters.
Structured output declared, but exposes no named fields.
No examples provided.
How do I install the io.github.qso-graph/eme-mcp server?
io.github.qso-graph/eme-mcp runs locally as a PyPI package, launched with uvx eme-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 · eme-mcp
claude mcp add qso-graph-eme-mcp -- uvx eme-mcp
What is the io.github.qso-graph/eme-mcp server?
io.github.qso-graph/eme-mcp is listed in the public MCP registry as io.github.qso-graph/eme-mcp. EME prediction for amateur radio: moon windows, path loss and degradation, computed locally. This page covers its PyPI package (eme-mcp).
Is the io.github.qso-graph/eme-mcp server safe to use?
io.github.qso-graph/eme-mcp scores 80 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 17 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/eme-mcp server expose?
io.github.qso-graph/eme-mcp exposes 5 tools: get_version_info, eme_moon_window, eme_path_loss, eme_degradation, eme_calendar. Their descriptions and schemas cost roughly 394 tokens of context every time the server is loaded.
Is the io.github.qso-graph/eme-mcp server still maintained?
io.github.qso-graph/eme-mcp is still listed as active in the MCP registry. We last reached this channel on 17 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/eme-mcp server under?
io.github.qso-graph/eme-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.