band-atlas

endpoint

https://www.aiotrf.com/mcp

protocol

streamable-http ·2025-06-18

authentication

none observed

public key

none — nobody has proven they own this listing · is it yours? claim it

karma

0 · newcomer

Is band-atlas live?

Yes — it answered the hub's last check (checked 2h ago). It answered 100% of checks over the last 30 days.

Is band-atlas free to use?

Yes — the hub reached it with no key and no payment.

What tools does band-atlas have?

7 tools: get_country_networks, find_devices, project_report, list_coverage, check_bands, check_device, iot_readiness.

Is band-atlas safe to connect?

The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.

Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.

• iot_readiness open 2h ago

  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.

  mcp-tool

  12345678910111213

  {
    "type": "object",
    "properties": {
      "countries": {
        "type": "array",
        "items": {
          "type": "string"
        },
        "description": "ISO codes or country names; at most 20; leave out for the top 20"
      }
    },
    "additionalProperties": false
  }

  arguments 13 lines copy
• get_country_networks unknown never probed

  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.

  mcp-tool

  12345678910111213

  {
    "type": "object",
    "required": [
      "country"
    ],
    "properties": {
      "country": {
        "type": "string",
        "description": "ISO 3166-1 alpha-2 code (us, de, br) or an English or Chinese country name"
      }
    },
    "additionalProperties": false
  }

  arguments 13 lines copy
• find_devices unknown never probed

  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.

  mcp-tool

  12345678910111213141516

  {
    "type": "object",
    "required": [
      "countries"
    ],
    "properties": {
      "countries": {
        "type": "array",
        "items": {
          "type": "string"
        },
        "description": "ISO codes or country names; at most 20"
      }
    },
    "additionalProperties": false
  }

  arguments 16 lines copy
• project_report unknown never probed

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

  mcp-tool

  123456789101112131415161718192021

  {
    "type": "object",
    "required": [
      "device",
      "countries"
    ],
    "properties": {
      "device": {
        "type": "string",
        "description": "Device id or name, for example mf833v, EG25-G, Quectel BG77"
      },
      "countries": {
        "type": "array",
        "items": {
          "type": "string"
        },
        "description": "ISO codes or country names (English or Chinese), up to 30"
      }
    },
    "additionalProperties": false
  }

  arguments 21 lines copy
• list_coverage unknown never probed

  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.

  mcp-tool

  12345

  {
    "type": "object",
    "properties": {},
    "additionalProperties": false
  }

  arguments 5 lines copy
• check_bands unknown 2h ago

  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.

  mcp-tool

  12345678910111213141516171819202122232425

  {
    "type": "object",
    "required": [
      "lte_bands",
      "countries"
    ],
    "properties": {
      "nr_bands": {
        "type": "string",
        "description": "Optional 5G NR bands, for example \"n1 n28 n78\""
      },
      "countries": {
        "type": "array",
        "items": {
          "type": "string"
        },
        "description": "ISO codes or country names; at most 10"
      },
      "lte_bands": {
        "type": "string",
        "description": "LTE bands, for example \"B1 B3 B5 B7 B8 B20 B28\" or \"1,3,20\""
      }
    },
    "additionalProperties": false
  }

  arguments 25 lines copy
• check_device unknown 2h ago

  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.

  mcp-tool

  123456789101112131415161718

  {
    "type": "object",
    "required": [
      "device",
      "country"
    ],
    "properties": {
      "device": {
        "type": "string",
        "description": "Device id or name, for example mf833v, ec25-e, Quectel EG25-G, Teltonika TRB140"
      },
      "country": {
        "type": "string",
        "description": "ISO code or country name"
      }
    },
    "additionalProperties": false
  }

  arguments 18 lines copy

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.