Skip to content

Band Atlas (Hyper Nexus)

by 365724-ctrl · remote · no sign-in to list tools · v1.2.0 · published by GitHub user 365724-ctrl

Which cellular IoT modules work on which networks: 465 networks, 172 countries, device verdicts

Changes · 4

7 tools: 4 change things and 3 only read.

Scanned Oct 21, 2026

No check matched anything in the tool definitions. No finding is not a safety guarantee. How the checks work.

claude mcp add --transport http band-atlas https://www.aiotrf.com/mcp

Tools

Open a tool for its reasons and full description. Descriptions are the publisher's own words, shown as they are.

7 tools

Changes things 4Claude Code: ask
  • check_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 rul…No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    Paste 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.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • check_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.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    Verdict (good, limited or no) for a known module or device on every network of a country, with the LTE and NR bands it lacks. Use list_coverage for device ids, or check_bands for a device that is not listed.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • iot_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%)…No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    The 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. Only confirmed data counts; "not listed" is never taken as "not available", so thinly documented countries may be under-scored.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • project_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…No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    One 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).

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
Only reads 3Claude Code: allow
  • find_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.No findings

    Why it is in this group

    • The name "find_devices" says "find": a word for reading.
    Description, as the server wrote it
    Rank 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. Useful to pick the fewest SKUs for a multi-country deployment.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • get_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, Re…No findings

    Why it is in this group

    • The name "get_country_networks" says "get": a word for reading.
    Description, as the server wrote it
    Mobile 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.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • list_coverageList every country (ISO code, name, number of networks) and every module or device (id, name, kind) Band Atlas covers.No findings

    Why it is in this group

    • The name "list_coverage" says "list": a word for reading.
    Description, as the server wrote it
    List every country (ISO code, name, number of networks) and every module or device (id, name, kind) Band Atlas covers. Call this first if you are unsure of a country code or a device id.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Install

Pinned to version 1.2.0. Values in angle brackets are yours to fill in.

claude mcp add --transport http band-atlas https://www.aiotrf.com/mcp

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__band-atlas__list_coverage",
      "mcp__band-atlas__get_country_networks",
      "mcp__band-atlas__find_devices"
    ],
    "ask": [
      "mcp__band-atlas__check_device",
      "mcp__band-atlas__check_bands",
      "mcp__band-atlas__project_report",
      "mcp__band-atlas__iot_readiness"
    ],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. It assumes the server is installed as band-atlas. Review it before you use it.