Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

io.github.qso-graph/iota-mcp

PYPI · IOTA-MCP

Islands on the Air MCP server. Group lookup, island search, DXCC mapping, nearby groups.

Available components

+11 this week 92 Trust /100

Last scanned (19 hours ago)

Scores higher than 95% of PyPI servers

Category Maps and Location

Trust breakdown (7 categories)

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/iota-mcp). View diagnostics → Pass
  • Clear OSI-approved license (GPL-3.0-or-later).Pass
  • Actively maintained (last published 6 days ago).Pass
  • Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability80
  • AI-judged instruction clarity (excellent).Pass
  • Tool/resource definitions use about 549 tokens (~78/item across 7 items; 7 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management70
  • Stability observed for 21 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 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
Changelog

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.

  • 4 Nov 26 +1
    • Package version: 0.2.0 → 0.4.1 functional
  • 3 Nov 26 −5
    • Stability: pass → 0.67 functional
  • 31 Oct 26 +15
    • Malware scan: unverified → pass ▲ security
  • 29 Oct 26 0
    • Package version: 0.4.0 → 0.4.1 functional
  • 27 Oct 26 0
    • Package version: 0.3.0 → 0.4.0 functional
  • 26 Oct 26 0
    • Package version: 0.2.0 → 0.3.0 functional
    • Package version: 0.2.0 → 0.2.3 functional
    • Package version: 0.2.0 → 0.2.2 functional
    • Package version: 0.2.0 → 0.2.1 functional
  • 17 Oct 26 +1
    • Stability: 0.97 → pass security
  • 15 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.

Diagnostics

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 4 Nov 2026 · Analysed pypi/iota-mcp@0.4.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/iota-mcp
Certificate issuer https://token.actions.githubusercontent.com
Certificate SAN https://github.com/qso-graph/iota-mcp/.github/workflows/publish.yml@refs/heads/main
Rekor log index 3559969477
Predicate type PyPI publish attestation https://docs.pypi.org/attestations/publish/v1
Subject digest sha256:ee09be098500cdbb6c3104af06568aaed4a50f33c97a4b9e5fa45fd4aa9153cd

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 →

MCP tools · 7 exposed · ~503 tokens

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 →

Tool Tokens
get_version_info ~78

Get iota-mcp service version and upstream programme data version. Returns the running PyPI version of iota-mcp and the IOTA programme data revision in use. Use this to confirm fleet alignment across MCP deployments — agents can compare service_version and spec_version across servers to detect drift without going outside the MCP protocol.

Input schema present but exposes no named parameters.

Structured output declared, but exposes no named fields.

No examples provided.

iota_dxcc ~93

Bidirectional DXCC-to-IOTA mapping. Provide either dxcc_num to find all IOTA groups for a DXCC entity, or refno to find which DXCC entities an IOTA group belongs to.

NameTypeReqDescription
dxcc_num––DXCC entity number (e.g., 291 for USA, 223 for England).
refno––IOTA reference number (e.g., EU-005).

Structured output declared, but exposes no named fields.

No examples provided.

iota_islands ~56

List all islands and subgroups in an IOTA group. Returns the full hierarchy: subgroups containing individual islands.

NameTypeReqDescription
refnostringyesIOTA reference number (e.g., NA-005, EU-005).

Structured output declared, but exposes no named fields.

No examples provided.

iota_lookup ~69

Look up an IOTA group by reference number. Returns group details including name, DXCC entity, bounding box, center coordinates, credit percentage, and island count.

NameTypeReqDescription
refnostringyesIOTA reference number (e.g., NA-005, EU-005, AF-001).

Structured output declared, but exposes no named fields.

No examples provided.

iota_nearby ~96

Find IOTA groups nearest to a location. Computes great-circle distance from the given coordinates to the center of each IOTA group's bounding box.

NameTypeReqDescription
latitudenumberyesLatitude in decimal degrees (e.g., 43.6 for Boise).
limit––Maximum results to return (default 20).
longitudenumberyesLongitude in decimal degrees (e.g., -116.2 for Boise).

Structured output declared, but exposes no named fields.

No examples provided.

iota_search ~73

Search IOTA groups and islands by name. Searches both group names and individual island names. Results are deduplicated by IOTA reference number.

NameTypeReqDescription
limit––Maximum results to return (default 25).
querystringyesSearch text (e.g., Hawaii, Shetland, Comoro).

Structured output declared, but exposes no named fields.

No examples provided.

iota_stats ~38

Get IOTA programme summary statistics. Returns total groups and islands, breakdown by continent, DXCC entity count, and most/least credited groups.

Input schema present but exposes no named parameters.

Structured output declared, but exposes no named fields.

No examples provided.

Install

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

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

# add to Claude Code
claude mcp add qso-graph-iota-mcp -- uvx iota-mcp
Common questions

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

io.github.qso-graph/iota-mcp is listed in the public MCP registry as io.github.qso-graph/iota-mcp. Islands on the Air MCP server. Group lookup, island search, DXCC mapping, nearby groups. This page covers its PyPI package (iota-mcp).

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

io.github.qso-graph/iota-mcp scores 92 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 4 November 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/iota-mcp server expose?

io.github.qso-graph/iota-mcp exposes 7 tools: get_version_info, iota_lookup, iota_search, iota_islands, iota_dxcc, and 2 more. Their descriptions and schemas cost roughly 503 tokens of context every time the server is loaded.

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

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

io.github.qso-graph/iota-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.