io.github.qso-graph/omiss-mcp
PYPI · OMISS-MCP
OMISS MCP server. Net schedule, nets on the air, members, check-in history, awards.
Available components
Last scanned (21 hours ago)
Scores higher than 92% of PyPI servers
Category Communication
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 Security99
- 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
- 2 of 19 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/omiss-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 Usability78
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 1301 tokens (~92/item across 14 items; 14 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management57
- Stability observed for 17 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
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 14 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 15 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
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.
- 15 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 50 to 53. That category is still filling its 30-day observation window: 15 days of observed history at the previous scan, 16 at this one. The score rises as the window fills, whether or not the server changes.
- 14 Oct 26 +54
- Injection markers: unverified → pass ▲ security
- Malware scan: unverified → pass ▲ security
- Tool coverage: unverified → 100 ▲ functional
- Stability: unverified → 0.50 ▲ functional
- MCP protocol: unverified → pass ▲ functional
- Package version: 0.1.5 → 0.1.10 functional
- 12 Oct 26 −33
- Tool safety: pass → unverified ▼ security
- Stability: Stability not yet verified: we do not have a sandbox capture of the MCP schema this version of the package serves yet. security
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- First check of Schema quality: unverified functional
- Package version: 0.1.5 → 0.1.10 functional
- 29 Sept 26 67
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/omiss-mcp@0.1.10
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/omiss-mcp |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/qso-graph/omiss-mcp/.github/workflows/publish.yml@refs/heads/main |
| Rekor log index | 3197604833 |
| Predicate type | PyPI publish attestation https://docs.pypi.org/attestations/publish/v1 |
| Subject digest | sha256:1c8b0889a356382e496a7339466433966b235efb7493fe9a833e832fa50623af |
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 19 packages
| Packages resolved | 19 |
|---|---|
| Stale | 2 |
| 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 ~35
Get omiss-mcp's version, the omiss.net layout it reads, and the version of the records it returns.
Input schema present but exposes no named parameters.
Structured output declared, but exposes no named fields.
No examples provided.
omiss_award_recipients Omiss Award Recipients ~92
List who holds an OMISS award, newest certificates first, or check one member.
| Name | Type | Req | Description |
|---|---|---|---|
| award_id | string | yes | The award's ID, from omiss_awards (e.g. ALPHABETSOUP). |
| callsign | – | – | Only this station's certificates. |
| limit | – | – | At most this many (default 100). |
| om_number | – | – | Only this member's certificates. |
Structured output declared, but exposes no named fields.
No examples provided.
omiss_award_rules Omiss Award Rules ~62
Get an OMISS award's rules, or (no award_id) every award's name, ID and summary.
| Name | Type | Req | Description |
|---|---|---|---|
| award_id | – | – | The award's ID, from omiss_awards or this tool (e.g. ALPHABETSOUP). |
Structured output declared, but exposes no named fields.
No examples provided.
omiss_awards Omiss Awards ~30
List the OMISS awards that have recipients, with the award IDs the other award tools take.
Input schema present but exposes no named parameters.
Structured output declared, but exposes no named fields.
No examples provided.
omiss_checkin_history Omiss Checkin History ~179
List past OMISS nets, newest first: all of them, or only those a member checked in to, on a band, on a date, or run by a net control. omiss.net shows the latest 100 matches.
| Name | Type | Req | Description |
|---|---|---|---|
| band | – | – | Only nets on this band: 10m, 12m, 15m, 17m, 20m, 40m, 80m or 160m. |
| callsign | – | – | Only nets this station checked in to (e.g. KI7MT). |
| date | – | – | Only nets on this date: YYYY, YYYY-MM or YYYY-MM-DD (UTC). |
| net_control | – | – | Only nets this station ran as net control. |
| om_number | – | – | Only nets this OMISS member checked in to (e.g. 7212). |
Structured output declared, but exposes no named fields.
No examples provided.
omiss_eligibility Omiss Eligibility ~124
For stations on a net: is each an OMISS member, and which award categories does it count for? From omiss.net's own rosters. Use it with a net's check-ins (netlogger-mcp's netlogger_checkins for a live net, or omiss_net_checkins for a past one) to see who you still need. Only the callsigns asked about are answered.
| Name | Type | Req | Description |
|---|---|---|---|
| callsigns | array | yes | Up to 200 callsigns (e.g. ["KI7MT", "W4DWS"]). |
Structured output declared, but exposes no named fields.
No examples provided.
omiss_member_lookup Omiss Member Lookup ~64
Look up one OMISS member by callsign or by OM number (give one).
| Name | Type | Req | Description |
|---|---|---|---|
| callsign | – | – | The member's callsign (e.g. KI7MT). |
| om_number | – | – | The member's OMISS number (e.g. 7212). |
Structured output declared, but exposes no named fields.
No examples provided.
omiss_net_checkins Omiss Net Checkins ~58
Get one past OMISS net: its net control, relays, frequency, net control's notes, and the check-in list.
| Name | Type | Req | Description |
|---|---|---|---|
| net_id | integer | yes | The net's ID, from omiss_checkin_history. |
Structured output declared, but exposes no named fields.
No examples provided.
omiss_net_schedule Omiss Net Schedule ~158
Get the OMISS net schedule: every net's band, UTC time, frequency and window, days, holiday time and band coordinator, and the next time it runs; the schedule's footnotes (holidays, winter schedule); and the federal holiday dates the holiday schedule follows. Days and times are UTC, so an evening net in the Americas falls on the previous local day; use next_utc and as_of_utc to work out "today" in the user's time zone. next_utc is the listed start: nets often open early for check-ins, and a net on the air now shows next_utc as its next run, so ask omiss_nets_on_air whether one is open.
Input schema present but exposes no named parameters.
Structured output declared, but exposes no named fields.
No examples provided.
omiss_net_statistics Omiss Net Statistics ~90
Get OMISS net statistics for the last 52 weeks: nets per band, the last net on each band, and the leaderboards (most check-ins, most nets as net control).
| Name | Type | Req | Description |
|---|---|---|---|
| state | – | – | Also give this state's last check-in on each band (2 letters, e.g. ID). |
| top | – | – | How many leaderboard entries (default 10, at most 50). |
Structured output declared, but exposes no named fields.
No examples provided.
omiss_nets_on_air Omiss Nets On Air ~90
List OMISS nets on the air now, from NetLogger, each matched to OMISS's own net schedule. A net on NetLogger is an OMISS net when it matches a scheduled one (its frequency is in that net's window, on a day it runs, near its start time) or its name says OMISS. Each says which scheduled net it is.
Input schema present but exposes no named parameters.
Structured output declared, but exposes no named fields.
No examples provided.
omiss_officers Omiss Officers ~35
List OMISS's officers, directors, band coordinators, committees, appointees, past presidents and other VIPs.
Input schema present but exposes no named parameters.
Structured output declared, but exposes no named fields.
No examples provided.
omiss_set_callsign Omiss Set Callsign ~87
Save the user's amateur radio callsign, for omiss_nets_on_air. Needed once. NetLogger is told which station is asking. The callsign is shared with netlogger-mcp, if it's installed. Ask the user for their own callsign; don't guess it.
| Name | Type | Req | Description |
|---|---|---|---|
| callsign | string | yes | The user's callsign (e.g. KI7MT). |
Structured output declared, but exposes no named fields.
No examples provided.
omiss_statehood_schedule Omiss Statehood Schedule ~37
Get the 40m Statehood schedule: each 40m net date and its free-call states, and the next one.
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/omiss-mcp server?
io.github.qso-graph/omiss-mcp runs locally as a PyPI package, launched with uvx omiss-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 · omiss-mcp
claude mcp add qso-graph-omiss-mcp -- uvx omiss-mcp
What is the io.github.qso-graph/omiss-mcp server?
io.github.qso-graph/omiss-mcp is listed in the public MCP registry as io.github.qso-graph/omiss-mcp. OMISS MCP server. Net schedule, nets on the air, members, check-in history, awards. This page covers its PyPI package (omiss-mcp).
Is the io.github.qso-graph/omiss-mcp server safe to use?
io.github.qso-graph/omiss-mcp scores 89 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/omiss-mcp server expose?
io.github.qso-graph/omiss-mcp exposes 14 tools: get_version_info, omiss_net_schedule, omiss_nets_on_air, omiss_set_callsign, omiss_member_lookup, and 9 more. Their descriptions and schemas cost roughly 1,141 tokens of context every time the server is loaded.
Is the io.github.qso-graph/omiss-mcp server still maintained?
io.github.qso-graph/omiss-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/omiss-mcp server under?
io.github.qso-graph/omiss-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.