protogrid

Search / us.telcodata/telcodata

telcodata

R1· needs a key

North American telephone numbering data: carriers, rate centers, OCNs, and number history.

v1.0.0 · active · website · descriptor JSON · versions

An agent can connect on its own if it already holds TELCODATA_TOKEN.Remote endpoint behind a static API key or header. The registry never sees the value; the agent fills the placeholder.
Quality80good
Trust61of 100
Uptime, 30 days93%
Latency p50222 ms

Connect

8 clients · secrets stay placeholders
{
  "mcpServers": {
    "telcodata": {
      "type": "http",
      "url": "https://api.telcodata.us/mcp",
      "headers": {
        "Authorization": "Bearer ${TELCODATA_TOKEN}"
      }
    }
  }
}
claude mcp add --transport http telcodata https://api.telcodata.us/mcp --header "Authorization: Bearer ${TELCODATA_TOKEN}"
[mcp_servers.telcodata]
url = "https://api.telcodata.us/mcp"
bearer_token_env_var = "TELCODATA_TOKEN"
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "telcodata": {
      "type": "remote",
      "url": "https://api.telcodata.us/mcp",
      "enabled": true,
      "headers": {
        "Authorization": "Bearer {env:TELCODATA_TOKEN}"
      }
    }
  }
}
{
  "mcpServers": {
    "telcodata": {
      "type": "http",
      "url": "https://api.telcodata.us/mcp",
      "headers": {
        "Authorization": "Bearer ${TELCODATA_TOKEN}"
      }
    }
  },
  "deeplink": "cursor://anysphere.cursor-deeplink/mcp/install?name=telcodata&config=eyJ0eXBlIjoiaHR0cCIsInVybCI6Imh0dHBzOi8vYXBpLnRlbGNvZGF0YS51cy9tY3AiLCJoZWFkZXJzIjp7IkF1dGhvcml6YXRpb24iOiJCZWFyZXIgJHtURUxDT0RBVEFfVE9LRU59In19"
}
{
  "servers": {
    "telcodata": {
      "type": "http",
      "url": "https://api.telcodata.us/mcp",
      "headers": {
        "Authorization": "Bearer ${TELCODATA_TOKEN}"
      }
    }
  }
}
{
  "mcpServers": {
    "telcodata": {
      "httpUrl": "https://api.telcodata.us/mcp",
      "headers": {
        "Authorization": "Bearer ${TELCODATA_TOKEN}"
      }
    }
  }
}
extensions:
  "telcodata":
    enabled: true
    name: "telcodata"
    type: streamable_http
    uri: "https://api.telcodata.us/mcp"
    headers:
      "Authorization": "Bearer ${TELCODATA_TOKEN}"
    timeout: 300

Placeholders to fill from your own secret store: ${TELCODATA_TOKEN}. The registry never accepts secret values.

Quality 80 / 100good

protocol75 · weight 25
  • warn
    protocol.modernnewest supported version is 2024-11-05; 2026-07-28 not supported, older versions are deprecated until 2027-07-28
  • n/a
    protocol.statelessonly applies to 2026-07-28 servers
  • pass
    protocol.transportstreamable HTTP
  • n/a
    protocol.list_ttlonly applies to 2026-07-28 servers
authorizationn/a · weight 15
  • n/a
    auth.prm, auth.as_metadata, auth.cimdno remote uses OAuth
  • n/a
    auth.secret_in_urlno templated URL
tool hygiene75 · weight 30
  • pass
    tools.descriptionsevery tool has a description
  • pass
    tools.description_lengthdescriptions are concise
  • pass
    tools.schemasevery tool has an object input schema
  • fail
    tools.annotationsno tool declares readOnlyHint or destructiveHint, so clients cannot tell safe calls from risky ones
  • fail
    tools.directory_hintsno tool declares all four of readOnlyHint, destructiveHint, idempotentHint and openWorldHint; missing: lookup_cic (readOnlyHint, destructiveHint, idempotentHint, openWorldHint); lookup_acna (readOnlyHint, destructiveHint, idempotentHint, openWorldHint); get_me (readOnlyHint, destructiveHint, idempotentHint, openWorldHint); …
  • pass
    tools.token_costabout 4,246 tokens to load every tool
  • pass
    tools.api_dumptools are not a one-to-one API dump
  • pass
    tools.hidden_textno hidden text in tool names, descriptions, schemas or annotations
stability100 · weight 15
  • pass
    stability.changesno tool changes in 30 days
  • pass
    stability.rug_pullno tool changed its meaning under the same name
  • pass
    stability.new_linksno tool change named a new site
dependenciesn/a · weight 15
  • n/a
    deps.known_vulns, deps.mcp_sdk_version, deps.resolvableno npm or PyPI package

21 tools, about 4,246 tokens to load them all · tool set 24b012815d41 · checked 2026-11-14 06:30 UTC

Tool changes

No tool definition changes recorded. A server's first observation is its baseline; later probes record what changes.

Checks run on what our credential-free, read-only probes observe; tools are never called and no code audit is performed. How it is computed.

Trust 61 / 100

no-repository
provenance55
liveness27
freshness100
hygiene80

+dns-namespace +website -unreachable(1 failures) +updated-18d-ago -no-repository

Derived from observable signals (official registry feed and our own credential-free probes); no code audit performed. How it is computed.

Endpoints

remoteauthreachableuptime 30dp50protocollast ok
https://api.telcodata.us/mcp streamable-httpapi_key ${TELCODATA_TOKEN}no (1 failures)93%222 ms2024-11-052026-11-13

Tools (21)

geocode_addressGeocode a U.S. street address with TelcoData's local TIGER/Line database. For Canadian addresses, return the direct Natural Resources Canada Geolocator URL instead of proxying the Canadian query.
get_download_metadataFetch metadata for a specific paid download without transferring file contents. Use after list_downloads when the user asks about one dataset's suggested filename, access level, availability, file existence, or last-updated time.
get_exchangeLook up a single NANP NPA-NXX exchange/prefix. Use when the user has an area code plus exchange such as 425-555, or when deriving the prefix from a phone number is unnecessary. Set include_blocks=true when the user needs portability/pooling detail, the responsible carrier may vary by thousands digit, or the answer should show all block-level assignments. TelcoData fields commonly include npa, exchange/NXX, thousands, state, country, ratecenter, company, ocn, lata, switch CLLI, and tandem CLLI. A thousands value of -1 represents the whole prefix/default aggregate; 0-9 are individual thousand-number pooling blocks.
get_exchange_thousandsLook up one thousands block within an NPA-NXX. Use when the user gives the seventh digit of a NANP number, such as 425-555-4XXX, or asks who owns/routes a specific block. If no block row exists, the tool reports whether it used the -1 aggregate/default row. TelcoData fields commonly include npa, exchange/NXX, thousands, state, country, ratecenter, company, ocn, lata, switch CLLI, and tandem CLLI. A thousands value of -1 represents the whole prefix/default aggregate; 0-9 are individual thousand-number pooling blocks.
get_meReturn the authenticated TelcoData account profile for the provided API key. Use this to confirm entitlement level, API access, expiration, and identity before explaining why a query or download may be unavailable.
get_ocn_profileFetch carrier profile details for a 4-character Operating Company Number (OCN). Use when the user asks who an OCN belongs to, wants carrier type/country, or needs FCC FRN/RMD and Canadian registration/contact fields tied to that carrier.
get_switchFetch central-office/switch detail for one 11-character CLLI code. Use when the user asks about a switch, wire center, location, equipment/switch type, LATA, tandem, point code, or English name tied to a CLLI. The officetype field contains space-separated raw NECA Tariff 4 office-capability codes; it is not the equipment model in switchtype. For prefixes served by a switch, start with get_exchange or related prefix-listing tools.
list_area_code_exchangesList all exchanges/prefixes in a NANP area code. Use for area-code inventory, coverage, or 'what prefixes exist in 425' questions. Set include_blocks=true only when the user asks for every thousand block or pooling-level detail, because that can return many more rows. TelcoData fields commonly include npa, exchange/NXX, thousands, state, country, ratecenter, company, ocn, lata, switch CLLI, and tandem CLLI. A thousands value of -1 represents the whole prefix/default aggregate; 0-9 are individual thousand-number pooling blocks.
list_downloadsList paid downloadable TelcoData datasets visible to the authenticated user, including entitlement/access flags. Use when the user asks what bulk data files, CSVs, database dumps, or paid downloads their account can access.
list_lata_prefixesList prefixes in a Local Access and Transport Area (LATA). Use for regional telecom market/routing questions such as all prefixes in a LATA. LATAs are telecom routing/market areas and do not necessarily match states, cities, or area codes. TelcoData fields commonly include npa, exchange/NXX, thousands, state, country, ratecenter, company, ocn, lata, switch CLLI, and tandem CLLI. A thousands value of -1 represents the whole prefix/default aggregate; 0-9 are individual thousand-number pooling blocks.
list_new_exchangesList newly assigned TelcoData exchanges for a date range. Use for recent numbering activity, new prefix reports, and state-filtered change monitoring. Defaults to the last 30 days when dates are omitted; pass explicit YYYY-MM-DD dates when the user gives a period. Results are exchange-level additions, not live telephone-number assignment events.
list_ocn_prefixesList NPA-NXX prefixes assigned to an Operating Company Number (OCN). Use when the user asks where a carrier operates, what prefixes belong to a carrier, or wants to pivot from an OCN profile into numbering footprint. Combine with get_ocn_profile for carrier identity fields. TelcoData fields commonly include npa, exchange/NXX, thousands, state, country, ratecenter, company, ocn, lata, switch CLLI, and tandem CLLI. A thousands value of -1 represents the whole prefix/default aggregate; 0-9 are individual thousand-number pooling blocks.
list_state_area_codesList NANP area codes for a state, province, or supported NANP country/territory code. Use for quick geography-to-NPA mapping before deeper area-code or rate-center queries.
list_tandem_prefixesList prefixes routed via a tandem switch CLLI. Use for routing and interconnection questions, or when the user has a tandem CLLI and wants all served prefixes. The input may be a 6- to 11-character CLLI prefix; broader prefixes can return more rows. TelcoData fields commonly include npa, exchange/NXX, thousands, state, country, ratecenter, company, ocn, lata, switch CLLI, and tandem CLLI. A thousands value of -1 represents the whole prefix/default aggregate; 0-9 are individual thousand-number pooling blocks.
lookup_acnaLook up CIC rows by 3-letter Access Customer Name Abbreviation (ACNA). Use when the user has an ACNA and wants associated carrier identification codes or carrier names.
lookup_cicLook up a 4-digit Carrier Identification Code (CIC/PIC) record. Use for questions about long-distance carrier selection codes, 1010 dialing, or mapping a CIC to carrier/ACNA data.
lookup_tnNormalize a dialable telephone number to E.164 and identify country metadata. Prefer this whenever the user gives a full phone number. For NANP numbers, it returns the most specific TelcoData exchange or thousands-block record and shows whether the lookup used block detail or fallback. TelcoData fields commonly include npa, exchange/NXX, thousands, state, country, ratecenter, company, ocn, lata, switch CLLI, and tandem CLLI. A thousands value of -1 represents the whole prefix/default aggregate; 0-9 are individual thousand-number pooling blocks.
search_carrier_profiles_by_frnList carrier profiles sharing an FCC Registration Number (FRN). Use to group related OCNs, carrier names, and RMD records under a common FCC registration.
search_carrier_profiles_by_rmd_idList carrier profiles sharing an FCC Robocall Mitigation Database filing ID. Use to connect multiple OCNs or brands to the same RMD filing/contact when investigating carrier identity, voice providers, or robocall-mitigation relationships.
search_ratecenterSearch exchanges/prefixes for a rate center within a state, province, or NANP country code. Use for local-service geography questions such as 'prefixes in the Seattle rate center' or 'which exchanges are in Hamilton, BM'. Rate-center names are telecom rate-center labels, not always postal city names. Set include_blocks=true for pooling detail. TelcoData fields commonly include npa, exchange/NXX, thousands, state, country, ratecenter, company, ocn, lata, switch CLLI, and tandem CLLI. A thousands value of -1 represents the whole prefix/default aggregate; 0-9 are individual thousand-number pooling blocks.
search_record_historySearch TelcoData's tracked source-record changes in reverse chronological order. Use this for questions about when an NPA-NXX or thousands block changed carrier, OCN, CLLI/switch, assignment status, rate center, or another tracked field. Filters are combined, and omitting all filters returns the most recent changes. Initial baseline-load events are excluded. Multi-field record changes are returned together as structured old/new JSON values rather than one unrelated result per changed field. The clli filter matches switch-related changes and accepts a 6- to 11-character CLLI or prefix. Use field for a lowercase source field name, source for the tracked source name, and limit to cap results.

Schemas: list_tools.

Similar MCP servers

Official server.json
{
  "name": "us.telcodata/telcodata",
  "$schema": "https://static.modelcontextprotocol.io/schemas/2025-12-11/server.schema.json",
  "remotes": [
    {
      "url": "https://api.telcodata.us/mcp",
      "type": "streamable-http",
      "headers": [
        {
          "name": "Authorization",
          "isSecret": true,
          "isRequired": true,
          "description": "Your TelcoData.US API key (Bearer token)"
        }
      ]
    }
  ],
  "version": "1.0.0",
  "websiteUrl": "https://www.telcodata.us/",
  "description": "North American telephone numbering data: carriers, rate centers, OCNs, and number history."
}