Comprehensive Model Context Protocol server for managing Home Assistant through AI assistants.
Nothing to run from here
Band Atlas (Hyper Nexus) is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
96/100
tool-list score
7
tools declared
remote
at its publisher
—
calls last 7d
What it does
Which cellular IoT modules work on which networks: 465 networks, 172 countries, device verdicts
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http band-atlas-hyper-nexus-mcp https://www.aiotrf.com/mcp
# 2 — ask your agent for something these tools do
# list_coverage, get_country_networks, check_device and 4 more
Band Atlas (Hyper Nexus) costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Publishernot claimed
3CAll 1 server
365724-ctrl1 server
1 category
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Installation
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. Nothing here runs on your machine and nothing runs on ours: this server answers at its publisher’s own address, and what you install is the connection straight to it.
Claude Codedeclared by this listing
This is a public server: it answers at its publisher’s own address and this marketplace is not in the path. Claude Code registers it in one command; --scope user makes it available in every project. The transport below is http, as the publisher's own manifest declares it.
claude mcp add --scope user --transport http band-atlas-hyper-nexus-mcp https://www.aiotrf.com/mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
Free on mcprush, and it answers at its publisher’s own address: this marketplace is not in the path, so there is no key of ours to hold and no card to add.
What it writes
One config entry pointing straight at the publisher’s own address — this marketplace is not in the path, and nothing from this listing executes on your machine.
What you approve
7 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
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.
No parameter schema on file.
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| country | string | yes | ISO 3166-1 alpha-2 code (us, de, br) or an English or Chinese country name |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| device | string | yes | Device id or name, for example mf833v, ec25-e, Quectel EG25-G, Teltonika TRB140 |
| country | string | yes | ISO code or country name |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| lte_bands | string | yes | LTE bands, for example "B1 B3 B5 B7 B8 B20 B28" or "1,3,20" |
| nr_bands | string | no | Optional 5G NR bands, for example "n1 n28 n78" |
| countries | array | yes | ISO codes or country names; at most 10 |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| countries | array | yes | ISO codes or country names; at most 20 |
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).
| Parameter | Type | Required | Notes |
|---|---|---|---|
| device | string | yes | Device id or name, for example mf833v, EG25-G, Quectel BG77 |
| countries | array | yes | ISO codes or country names (English or Chinese), up to 30 |
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 docu
| Parameter | Type | Required | Notes |
|---|---|---|---|
| countries | array | no | ISO codes or country names; at most 20; leave out for the top 20 |
Free
$0 forever
- Every tool — any call limit is its publisher’s, not ours
- No card, and mcprush charges nothing for it
- Runs at its publisher’s own address — this marketplace is not in the path
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install Band Atlas (Hyper Nexus) or to call it, at any volume.
Call allowance · this installenforced at the gateway
Monthly allowance, in calls
—
—
Alert at 80% · then the tool returns a normal MCP error
Used this month: —
ATool-list grade · score 96 / 100
Release 1.2.0 · scanned 21 Oct 2026
Graded from the tools this server lists, not from its source code.
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
Threat score100
Client score96
Findings0 threat · 0 capability
Capabilityminimal
Coveragemanifest
Verificationnot in this report
Surface digestab20fb981567a444e7b54d9c895193cde66aeda9573c560105e35fb49383dccf
Score vectorthreat 100 → client 96
| Term | Level | What it prices | Points |
|---|---|---|---|
| capability-exposure | minimal | capability blast radius (minimal) — client exposure if the model is manipulated | −0 |
| coverage-honesty | manifest | inspection depth (manifest) — how much of the target the scan could see | −4 |
score = clamp(round(threatScore − E_cap − E_ver − E_cov), 0, 100). No model, no opinion, no network call at scoring time: the same methodology version against the same bytes always produces this number, and every line above is a field of the report rather than a summary of it.
What the scan could actually read
A grade is only as meaningful as its coverage, so the scanner publishes its own depth before it publishes its result.
The scan read each tool’s name, description, input schema and annotations exactly as the server listed them the last time it answered us; no code was reviewed. We ask the server again about once a month, and a list that changed is graded again.
Tool surfaceread
Implementation sourcenot available
Package metadatanot available
Live transportnot available
The implementation source was not read — this reflects the declared tool metadata only.
Capability — what it could do if the model were manipulated
Tags derived from each tool’s schema and the implementation, not from what the tool calls itself. minimal is the level these add up to.
| Tool | Capability tags | Why the tag was assigned |
|---|---|---|
| list_coverage | no tags | |
| get_country_networks | no tags | |
| check_device | no tags | |
| check_bands | no tags | |
| find_devices | no tags | |
| project_report | no tags | |
| iot_readiness | no tags |
Toxic-flow graph
The lethal trifecta, checked as a graph rather than as a checklist: untrusted input, a sensitive source and an external sink have to meet before there is a path worth worrying about.
The public result for this release does not print the flow graph, so there is nothing to show here. That is not the same as "no paths were found": what the scan did read is above, under coverage.
Supply chain and provenance
Integrityfirst-seen
Surface digestab20fb981567a444
Scanned2026-10-21
This is the first scan of this surface here, so there is nothing yet to compare it against.
Every result on this tab comes from one deterministic pass over the published package — offline, rule by rule, and auditable line by line above. Same methodology version, same bytes, same score.
Release history
This is an address its publisher runs: which release it serves is theirs to choose, so there is nothing here to pin. The history below is for reading; the current release on file is 1.2.0.
1.2.0
undated
latestNo release note was published with this version.
—
no reviews yet
Who can review
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Sign in to write one
Any signed-in account that does not publish Band Atlas (Hyper Nexus) can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
No reviews yet
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.