ENDPOINT 1
https://www.aiotrf.com/mcp
MCP server metadata
- Name
- band-atlas
- Version
- 1.2.0
Band Atlas answers whether cellular IoT modules and devices work on the mobile networks of 172 countries, network by network. Use check_device for a listed device, check_bands for any band list, get_country_networks for a country, find_devices to pick devices for several countries. Verdicts: good, limited (works with gaps, often a missing coverage band under 1 GHz), no. Data is CC BY 4.0; credit "Hyper Nexus · Band Atlas" and link https://www.aiotrf.com/en/ai/band-atlas/.
Known tools 7
list_coverageList every country (ISO code, name, number of networks) and every module or device (id, name, kind) Band Atlas covers.
Inferred read-onlyget_country_networksMobile networks of one country: their 4G/LTE and 5G/NR bands (each marked cross-checked by two independent sources or single-source), core bands, and the state of 2G, 3G, 5G SA, RedCap, LTE-M and NB-IoT, with switch-off dates.
Inferred read-onlycheck_deviceVerdict (good, limited or no) for a known module or device on every network of a country, with the LTE and NR bands it lacks.
Inferred read-onlycheck_bandsPaste the LTE (and optionally 5G NR) bands of any cellular module or device and get a verdict on every network of one or more countries, with the bands it lacks, using the same rules as Band Atlas: bands cross-checked by two sources are scored, coverage bands under 1 GHz weigh double, good needs at least 60 percent and a coverage band.
Inferred read-onlyfind_devicesRank the modules and devices in Band Atlas by how many networks of the given countries rate them good, and say which device works well on every network of each country.
Inferred read-onlyproject_reportOne report for a device across several target countries: where it works as is, where it needs attention (with the indoor-coverage risk when a network's own coverage band is missing) and where it does not work, plus a link to the full report on the website (PDF, share link, ask an engineer to confirm).
Inferred read-onlyiot_readinessThe Band Atlas IoT connectivity readiness index (beta, 0-100) for the given countries, or the top 20 when none are given: coverage (share of networks with a sub-1 GHz 4G band, 30%), LTE-M and NB-IoT confirmed on at least one network (30%), 5G and RedCap (20%), device fit (20%), with rank and data confidence.
Inferred read-onlyCONNECT WITH APPROVAL
Client installation
Review this server and its permissions before adding it. Secret placeholders must be set locally.
Codex
~/.codex/config.toml
[mcp_servers.band-atlas]
url = "https://www.aiotrf.com/mcp"
enabled = true
Claude Code
.mcp.json
{
"mcpServers": {
"band-atlas": {
"type": "http",
"url": "https://www.aiotrf.com/mcp"
}
}
}
Claude Desktop
Settings → Connectors → Add custom connector
Name: band-atlas
Remote MCP URL: https://www.aiotrf.com/mcp
Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.
Cursor
.cursor/mcp.json
{
"mcpServers": {
"band-atlas": {
"url": "https://www.aiotrf.com/mcp"
}
}
}
Visual Studio Code
.vscode/mcp.json
Add to Visual Studio Code{
"servers": {
"band-atlas": {
"type": "http",
"url": "https://www.aiotrf.com/mcp"
}
}
}
Generic MCP
Client-specific MCP configuration
{
"name": "band-atlas",
"transport": "streamable-http",
"url": "https://www.aiotrf.com/mcp"
}
MCP Inspector
Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.
TRUST AND VERIFICATION EVIDENCE
Loading Trust v2 evidence…
Checking the associated registrable domain. The BuiltWith key remains server-side.
Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.