Skip to main content
Glama
iota-mcp

iota-mcp

by qso-graph

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault

No arguments

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{
  "listChanged": true
}
logging
{}
prompts
{
  "listChanged": true
}
resources
{
  "subscribe": false,
  "listChanged": true
}

Tools

Functions exposed to the LLM to take actions

NameDescription
get_version_infoA

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.

iota_lookupA

Look up an IOTA group by reference number.

Returns group details including name, DXCC entity, bounding box, center coordinates, credit percentage, and island count.

iota_searchA

Search IOTA groups and islands by name.

Searches both group names and individual island names. Results are deduplicated by IOTA reference number.

iota_islandsA

List all islands and subgroups in an IOTA group.

Returns the full hierarchy: subgroups containing individual islands.

iota_dxccA

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.

iota_statsA

Get IOTA programme summary statistics.

Returns total groups and islands, breakdown by continent, DXCC entity count, and most/least credited groups.

iota_nearbyA

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.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

A3.9/5.0

Scored across 7 tools

Disambiguation5/5

Each tool has a clearly distinct purpose: version metadata, reference lookup, name search, island hierarchy, statistics, DXCC mapping, and proximity search. The only plausible overlap is lookup versus search, but they are separated by reference number versus name, and the descriptions make the boundary clear.

Naming Consistency4/5

Six tools share a predictable iota_ prefix and are readable together, though the pattern is noun-oriented rather than a strict verb_noun convention. get_version_info is a minor deviation as a meta tool with a different prefix, but it is clear and not confusing.

Tool Count5/5

Seven tools is well scoped for a read-only IOTA reference server. Each tool covers a meaningful operation, and there are no redundant or filler endpoints.

Completeness4/5

The surface covers lookup by reference, search by name, island hierarchy, DXCC mapping, proximity search, statistics, and version metadata. Minor gaps such as listing or filtering all groups without a name query are workable through existing search and mapping tools.

Maintenance

ActivityActive
ResponsivenessLimited data