Spec Driven Development
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Description from the maker (original English)
Which cellular IoT modules work on which networks: 465 networks, 172 countries, device verdicts
These three are never merged into one score: opinions, measurements and popularity are different things.
We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.
Pick the AI app you use, then copy the settings.
You need
Which app do you use?
Pick your app above. We remember it, so next time the button says “Install in …”.
Works in Claude on the web, desktop and mobile:
https://www.aiotrf.com/mcpRun this in your terminal
claude mcp add --transport http band-atlas https://www.aiotrf.com/mcpPaste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"band-atlas": {
"url": "https://www.aiotrf.com/mcp"
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
Paste into .vscode/mcp.json in your project
{
"servers": {
"band-atlas": {
"type": "http",
"url": "https://www.aiotrf.com/mcp"
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
ChatGPT connects only to servers on the internet:
https://www.aiotrf.com/mcpMenu names can differ slightly by plan and over time.
Your choice stays on this device in a cookie; no account needed.
These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.
Tool names and descriptions exactly as the server reported them on Nov 7, 2026. The maker wrote them, not us; we show them as plain text.
list_coverageList 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_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, RedCap, LTE-M and NB-IoT, with switch-off dates.
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. Use list_coverage for device ids, or check_bands for a device that is not listed.
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 rules as Band Atlas: bands cross-checked by two sources are scored, coverage bands under 1 GHz weigh do
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. Useful to pick the fewest SKUs for a multi-country deployment.
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) and where it does not work, plus a link to the full report on the website (PDF, share link, ask an
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%), LTE-M and NB-IoT confirmed on at least one network (30%), 5G and RedCap (20%), device fit (20%), w
We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 9, 2026
The registry name was verified with the GitHub account 365724-ctrl, which owns the repo
We have not read this repo from GitHub yet
We have not read this repo from GitHub yet
Responded in 601 ms (HTTP 200)
No sign-in needed
Read 7 tool descriptions and found no hidden instructions to the AI
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
It passed 3 of 3 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.
The registry does not list a required key, though some servers ask you to sign in on first use.
It runs in the maker’s cloud. Connect over the internet with nothing to install, but what you send passes through the maker’s servers.
The GitHub repo last changed –, and the latest version (1.2.0) reached the registry 21 days ago.
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. It connects by URL, so apps that accept remote MCP servers work too, such as ChatGPT in developer mode.
In the same category: Spec Driven Development, Remote Desktop Commander, bot2bot
Servers in the same category from other makers, sorted by stars.
Reading a card:↓ Downloads per weeki★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.
Let your AI assistant message the bots of family and friends.
Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.
Which cellular IoT modules and devices work on which networks, country by country — 4G/5G bands of 465 networks in 172 countries, 2G/3G switch-offs, LTE-M / NB-IoT / 5G RedCap availability, eSIM by network, an IoT readiness index for every country, and network-by-network verdicts for 39 modules, DTUs, industrial routers, vehicle trackers and dongles.
| File | Contents | Rows |
|---|---|---|
atlas.json | Everything in one JSON file | — |
bands.csv | 4G/5G band reference | 148 |
iot_networks.csv | LTE-M and NB-IoT networks | 208 |
model_verdicts.csv | Every module and device rated on every network, with the bands it lacks | 18135 |
models.csv | Modules and IoT devices (DTUs, routers, trackers): bands and sources | 39 |
network_bands.csv | The 4G/5G bands each network uses | 1732 |
networks.csv | Networks: market, operator, technologies and switch-off status | 465 |
pulse.csv | Network pulse: industry indicators over time, with sources | 48 |
redcap_networks.csv | 5G RedCap launches, deployments and trials | 27 |
sources.csv | Sources and evidence grades (A official / B industry / C distributors and media) | 476 |
sunset.csv | 2G, 3G and NB-IoT switch-off events | 77 |
readiness.json / readiness.csv | Global IoT readiness index: score, rank and the four parts (coverage, LTE-M/NB-IoT, 5G and RedCap, device fit) per country | 172 |
quality.json | The data-quality checks run before every update, and the cross-verification shares | — |
esim.json | Consumer eSIM availability by network | — |
A device is rated good on a network when it supports the bands that carry the network's service, limited when it lacks some of them (typically a coverage band), and no when it cannot attach. missing_bands lists what is lacking. Receive-only bands (for example LTE B29 and B32) are not counted as bands that can carry a connection alone. Third-party bands come from each maker's datasheets, wiki or product pages; listing a product is not an endorsement.
The same data answers through an MCP server (7 tools: band check, country, operator, project report, IoT readiness and more) and a public JSON API with an OpenAPI description. See https://www.aiotrf.com/en/ai/band-atlas/developers/.
Use the "Cite this repository" button (from CITATION.cff), or:
Hyper Nexus (2026). *Band Atlas: cellular IoT bands, networks and device verdicts* [data set]. https://www.aiotrf.com/ai/band-atlas/ — CC BY 4.0
CC BY 4.0 — free to use, share and adapt, including commercially, as long as you give credit:
Band Atlas · Hyper Nexus (https://www.aiotrf.com/ai/band-atlas/), CC BY 4.0
Found something out of date? Open an issue with a link to the operator's or maker's announcement, or use the correction button on any page of the live tool. Networks are re-checked every quarter.
哪些蜂窝物联网模组与设备,能在哪个国家的哪张网络上使用:172 个国家 465 张网络的 4G/5G 频段、2G/3G 退网时间、LTE-M / NB-IoT / 5G RedCap 状态,以及 39 款模组、DTU、工业路由器、车载定位器与数据卡的逐网评级。每一项数据都附来源与证据等级;数据核对日期 2026-10-06,每天自动同步。另有 172 个国家的物联网联接就绪指数和各网络的 eSIM 开通情况。
| 文件 | 内容 | 行数 |
|---|---|---|
atlas.json | 全部数据(JSON) | — |
bands.csv | 4G/5G 频段参数 | 148 |
iot_networks.csv | LTE-M 与 NB-IoT 网络 | 208 |
model_verdicts.csv | 每款模组与设备在每张网络上的评级与缺少的频段 | 18135 |
models.csv | 模组与物联网设备(DTU、路由器、定位器):频段与来源 | 39 |
network_bands.csv | 每张网络在用的 4G/5G 频段 | 1732 |
networks.csv | 网络清单(国家、运营商、技术与退网状态) | 465 |
pulse.csv | 网络脉搏:行业指标的历史数据与来源 | 48 |
redcap_networks.csv | 5G RedCap 商用、部署与试验 | 27 |
sources.csv | 来源清单与证据等级(A 官方 / B 行业 / C 经销商与媒体) | 476 |
sunset.csv | 2G、3G 与 NB-IoT 退网事件 | 77 |
readiness.json / readiness.csv | 全球物联网联接就绪指数:每个国家的分数、排名与四个分项(覆盖、LTE-M/NB-IoT、5G 与 RedCap、设备适配) | 172 |
quality.json | 每次更新前运行的数据校验与交叉印证比例 | — |
esim.json | 各网络的手机 eSIM 开通情况 | — |
授权:CC BY 4.0,可自由使用、分享和修改(包括商业用途),注明出处即可:
全球频段通 · 超级联接(https://www.aiotrf.com/ai/band-atlas/),CC BY 4.0