Band Atlas (Hyper Nexus) MCP server

• check_bandsFree

  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.

• check_deviceFree

  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.

• find_devicesFree

  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.

• get_country_networksFree

  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.

• iot_readinessFree

  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.

• list_coverageFree

  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.

• project_reportFree

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

• –Code scanremote-only server, no package to scann/a
• Live reliabilityremote reachable in 2048ms17/20
• Tool poisoning7 tool descriptions checked15/15
• Auth qualityopen endpoint, read-only tools10/15
• Maintenancelast push 1 days ago15/15
• Maintainer identityregistry namespace matches repository owner6/10

Safety score

84/100

higher than 68% of 48,255 servers

Tools

7

the typical server has 7

Tools that change things

0%

typical: 0%. Fewer write tools means less an agent can break

Uptime

100%

of our recent checks; the typical remote server answers 100%

Response time

1,392 ms

faster than 6% of 30,031 servers

Band Atlas (Hyper Nexus): common questions

Is Band Atlas (Hyper Nexus) MCP server safe?

Mostly: it is graded B (84/100). Read the Band Atlas (Hyper Nexus) safety report

How do I install Band Atlas (Hyper Nexus)?

It runs remotely at www.aiotrf.com. Add it to Claude Code, Cursor, VS Code or Claude Desktop with the snippets above, or call it through the mcp.market gateway without installing anything.

Does Band Atlas (Hyper Nexus) need an API key?

Not as far as the registry entry and our scan can tell: no credentials are declared or required.

Is Band Atlas (Hyper Nexus) maintained?

The last commit was 9 days ago (2026-10-26). The latest release is v1.2.0.

Is Band Atlas (Hyper Nexus) up?

100% of our last 28 checks got an answer. We check remote servers about four times a day.

What can I use instead of Band Atlas (Hyper Nexus)?

Servers from other publishers that do the same job: UniFi Network MCP server.

How does Band Atlas (Hyper Nexus) compare with other MCP servers?

safety score 84/100 (higher than 68% of 48,255 servers); tools 7 (the typical server has 7); tools that change things 0% (typical: 0%. Fewer write tools means less an agent can break). Full comparison.