Band Atlas (Hyper Nexus)

Measured conclusion: Alive, not deep-tested. L2 outcome: not_attempted.

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

Add to your agent

Copy this into your MCP client config:

{
  "mcpServers": {
    "Band Atlas (Hyper Nexus)": {
      "url": "https://www.aiotrf.com/mcp",
      "transport": "streamable-http"
    }
  }
}

Measured tools (7)

• list_coverage read-only

  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.

  Hints: read-only yes · destructive no · idempotent yes · open-world no

• get_country_networks read-only

  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.

  Parameters:

  • country (required) — string — ISO 3166-1 alpha-2 code (us, de, br) or an English or Chinese country name

  Hints: read-only yes · destructive no · idempotent yes · open-world no

• check_device read-only

  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.

  Parameters:

  • device (required) — string — Device id or name, for example mf833v, ec25-e, Quectel EG25-G, Teltonika TRB140
  • country (required) — string — ISO code or country name

  Hints: read-only yes · destructive no · idempotent yes · open-world no

• check_bands read-only

  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.

  Parameters:

  • lte_bands (required) — string — LTE bands, for example "B1 B3 B5 B7 B8 B20 B28" or "1,3,20"
  • countries (required) — array — ISO codes or country names; at most 10
  • nr_bands — string — Optional 5G NR bands, for example "n1 n28 n78"

  Hints: read-only yes · destructive no · idempotent yes · open-world no

• find_devices read-only

  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.

  Parameters:

  • countries (required) — array — ISO codes or country names; at most 20

  Hints: read-only yes · destructive no · idempotent yes · open-world no

• project_report read-only

  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).

  Parameters:

  • device (required) — string — Device id or name, for example mf833v, EG25-G, Quectel BG77
  • countries (required) — array — ISO codes or country names (English or Chinese), up to 30

  Hints: read-only yes · destructive no · idempotent yes · open-world no

• iot_readiness read-only

  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.

  Parameters:

  • countries — array — ISO codes or country names; at most 20; leave out for the top 20

  Hints: read-only yes · destructive no · idempotent yes · open-world no

Publisher website Repository

Measured by MCPYP probing. Untested fields are omitted, never estimated. Listing is always free; MCPYP never proxies calls or stores user tokens.