# Band Atlas (Hyper Nexus) (remote · www.aiotrf.com)

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

- Trust score: 80/100 (high trust)
- Change this week: +4
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- remote · `www.aiotrf.com`: 80/100 (this document), [markdown](https://verifymcp.io/servers/365724-ctrl-band-atlas/www.md), [page](https://verifymcp.io/servers/365724-ctrl-band-atlas/www)

## Channel facts

- Endpoint: `https://www.aiotrf.com/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.2.0`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-05.

- **Endpoint Security**: 80/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 74/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 894 tokens (~127/item across 7 items; 7 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 57/100
  - Stability observed for 17 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 7 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 8 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 60/100
  - Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28.

## Install

### How do I install the Band Atlas (Hyper Nexus) MCP server?

Band Atlas (Hyper Nexus) is a hosted endpoint at https://www.aiotrf.com/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add --transport http 365724-ctrl-band-atlas 'https://www.aiotrf.com/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "365724-ctrl-band-atlas": {
      "url": "https://www.aiotrf.com/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "365724-ctrl-band-atlas": {
      "type": "http",
      "url": "https://www.aiotrf.com/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.365724-ctrl-band-atlas]
url = "https://www.aiotrf.com/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "365724-ctrl-band-atlas": {
      "type": "remote",
      "url": "https://www.aiotrf.com/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add 365724-ctrl-band-atlas --url 'https://www.aiotrf.com/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  365724-ctrl-band-atlas:
    url: "https://www.aiotrf.com/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "365724-ctrl-band-atlas": {
      "Transport": "http",
      "Url": "https://www.aiotrf.com/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add 365724-ctrl-band-atlas -t streamable-http -u 'https://www.aiotrf.com/mcp'
```

### Other

```json
{
  "mcpServers": {
    "365724-ctrl-band-atlas": {
      "type": "http",
      "url": "https://www.aiotrf.com/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-05 (score 80, +1)

No change was recorded against any check on this day. Stability & Change Management went from 53 to 57. That category is still filling its 30-day observation window: 16 days of observed history at the previous scan, 17 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-03 (score 79, +1)

No change was recorded against any check on this day. Stability & Change Management went from 47 to 50. That category is still filling its 30-day observation window: 14 days of observed history at the previous scan, 15 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-01 (score 78, +1)

No change was recorded against any check on this day. Stability & Change Management went from 40 to 43. That category is still filling its 30-day observation window: 12 days of observed history at the previous scan, 13 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-30 (score 77, +1)

No change was recorded against any check on this day. Stability & Change Management went from 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-27 (score 76, +1)

No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-25 (score 75, +1)

No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-23 (score 74, +1)

No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-21 (score 73, +1)

No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.

## MCP tools (7)

### `list_coverage` (~54 tokens)

List countries and devices

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.

### `get_country_networks` (~110 tokens)

A country's networks

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.

Input parameters:

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

### `check_device` (~105 tokens)

Will this device work in this country

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.

Input parameters:

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

### `check_bands` (~165 tokens)

Check any band list

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.

Input parameters:

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

### `find_devices` (~72 tokens)

Devices that work in these countries

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.

Input parameters:

- `countries` (array, required): ISO codes or country names; at most 20

### `project_report` (~122 tokens)

Project report for several countries

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

Input parameters:

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

### `iot_readiness` (~149 tokens)

IoT connectivity readiness by country

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.

Input parameters:

- `countries` (array): ISO codes or country names; at most 20; leave out for the top 20

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/365724-ctrl-band-atlas/www#diagnostics

## Score history

- 2026-11-05: 80
- 2026-11-04: 79
- 2026-11-03: 79
- 2026-11-02: 78
- 2026-11-01: 78
- 2026-10-31: 77
- 2026-10-30: 77
- 2026-10-29: 76
- 2026-10-28: 76
- 2026-10-27: 76
- 2026-10-26: 75
- 2026-10-25: 75
- 2026-10-24: 74
- 2026-10-23: 74
- 2026-10-22: 73
- 2026-10-21: 73
- 2026-10-20: 72
- 2026-10-19: 72

## Common questions

### What is the Band Atlas (Hyper Nexus) MCP server?

Band Atlas (Hyper Nexus) is an MCP server listed in the public MCP registry as io.github.365724-ctrl/band-atlas. Which cellular IoT modules work on which networks: 465 networks, 172 countries, device verdicts. This page covers its hosted endpoint (https://www.aiotrf.com/mcp).

### Is the Band Atlas (Hyper Nexus) MCP server safe to use?

Band Atlas (Hyper Nexus) scores 80 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

### What tools does the Band Atlas (Hyper Nexus) MCP server expose?

Band Atlas (Hyper Nexus) exposes 7 tools: list_coverage, get_country_networks, check_device, check_bands, find_devices, and 2 more. Their descriptions and schemas cost roughly 777 tokens of context every time the server is loaded.

### Does the Band Atlas (Hyper Nexus) MCP server require authentication?

No. We connected to Band Atlas (Hyper Nexus) without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the Band Atlas (Hyper Nexus) MCP server still maintained?

Band Atlas (Hyper Nexus) is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://www.aiotrf.com/mcp
- Repository: https://github.com/365724-ctrl/band-atlas-data
- Website: https://www.aiotrf.com/en/ai/band-atlas/developers/
- Changelog RSS feed: https://verifymcp.io/servers/365724-ctrl-band-atlas/www.xml
- Changelog JSON feed: https://verifymcp.io/servers/365724-ctrl-band-atlas/www.json
- HTML version of this page: https://verifymcp.io/servers/365724-ctrl-band-atlas/www