# us.telcodata/telcodata (remote · api.telcodata.us)

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

- Trust score: 66/100 (medium)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- remote · `api.telcodata.us`: 66/100 (this document), [markdown](https://verifymcp.io/servers/us-telcodata-telcodata/api.md), [page](https://verifymcp.io/servers/us-telcodata-telcodata/api)

## Channel facts

- Endpoint: `https://api.telcodata.us/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.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**: 63/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation not fully verified: no authorisation is required to call this server, and 21 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.
  - 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**: 69/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 3576 tokens (~170/item across 21 items; 21 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 30/100
  - Stability observed for 9 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 97/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 92% 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 21 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 22 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 20/100
  - Spec-recency check failed: implements MCP spec 2024-11-05; the latest is 2026-07-28.

## Install

### How do I install the us.telcodata/telcodata MCP server?

us.telcodata/telcodata is a hosted endpoint at https://api.telcodata.us/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 us-telcodata-telcodata 'https://api.telcodata.us/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "us-telcodata-telcodata": {
      "url": "https://api.telcodata.us/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "us-telcodata-telcodata": {
      "type": "http",
      "url": "https://api.telcodata.us/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.us-telcodata-telcodata]
url = "https://api.telcodata.us/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "us-telcodata-telcodata": {
      "type": "remote",
      "url": "https://api.telcodata.us/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add us-telcodata-telcodata --url 'https://api.telcodata.us/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  us-telcodata-telcodata:
    url: "https://api.telcodata.us/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "us-telcodata-telcodata": {
      "Transport": "http",
      "Url": "https://api.telcodata.us/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add us-telcodata-telcodata -t streamable-http -u 'https://api.telcodata.us/mcp'
```

### Other

```json
{
  "mcpServers": {
    "us-telcodata-telcodata": {
      "type": "http",
      "url": "https://api.telcodata.us/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-04 (score 66, +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-11-01 (score 65, +1)

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

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

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

### 2026-10-28 (score 63, +1)

- [functional improvement] Stability: unverified → 0.03

### 2026-10-27 (score 62)

First indexed and scored.

## MCP tools (21)

### `get_me` (~83 tokens)

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

Input parameters:

- `api_key` (string): TelcoData API key. Optional if TELCODATA_MCP_API_KEY is set or the HTTP MCP request provides Authorization/X-API-Key.

### `get_exchange` (~234 tokens)

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

Input parameters:

- `api_key` (string): TelcoData API key. Optional if TELCODATA_MCP_API_KEY is set or the HTTP MCP request provides Authorization/X-API-Key.
- `include_blocks` (boolean): Include individual thousands-block rows for number-pooling detail.
- `npa` (string, required): 3-digit NANP area code.
- `nxx` (string, required): 3-digit NANP central-office/exchange code.

### `search_record_history` (~363 tokens)

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

Input parameters:

- `api_key` (string): TelcoData API key. Optional if TELCODATA_MCP_API_KEY is set or the HTTP MCP request provides Authorization/X-API-Key.
- `clli` (string): Optional 6- to 11-character CLLI or CLLI prefix used to find switch changes.
- `field` (string): Optional lowercase tracked field name, such as company, ocn, switch, ratecenter, or type.
- `limit` (integer): Maximum results; defaults to 100 and is capped by the API's configured maximum page size.
- `npa` (string): Optional 3-digit NANP area code filter.
- `nxx` (string): Optional 3-digit central-office/exchange code filter.
- `ocn` (string): Optional 4-character Operating Company Number filter.
- `source` (string): Optional tracked source name, not an archive filename.
- `thousands` (integer): Optional thousands-block filter: 0-9 for a pooled block or -1 for the whole-prefix/default record.

### `get_exchange_thousands` (~235 tokens)

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

Input parameters:

- `api_key` (string): TelcoData API key. Optional if TELCODATA_MCP_API_KEY is set or the HTTP MCP request provides Authorization/X-API-Key.
- `npa` (string, required): 3-digit NANP area code.
- `nxx` (string, required): 3-digit NANP central-office/exchange code.
- `thousands` (integer, required): Seventh digit of the number, 0-9; use -1 only for the whole-prefix/default aggregate.

### `lookup_tn` (~180 tokens)

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

Input parameters:

- `api_key` (string): TelcoData API key. Optional if TELCODATA_MCP_API_KEY is set or the HTTP MCP request provides Authorization/X-API-Key.
- `tn` (string, required): Dialable phone number in national or international format.

### `list_area_code_exchanges` (~207 tokens)

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

Input parameters:

- `api_key` (string): TelcoData API key. Optional if TELCODATA_MCP_API_KEY is set or the HTTP MCP request provides Authorization/X-API-Key.
- `include_blocks` (boolean): Return all thousands-block rows instead of one row per NPA-NXX prefix.
- `npa` (string, required): 3-digit NANP area code.

### `geocode_address` (~123 tokens)

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

Input parameters:

- `api_key` (string): TelcoData API key. Optional if TELCODATA_MCP_API_KEY is set or the HTTP MCP request provides Authorization/X-API-Key.
- `city` (string)
- `language` (string)
- `postal_code` (string)
- `state` (string)
- `street` (string)

### `search_ratecenter` (~247 tokens)

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

Input parameters:

- `api_key` (string): TelcoData API key. Optional if TELCODATA_MCP_API_KEY is set or the HTTP MCP request provides Authorization/X-API-Key.
- `include_blocks` (boolean): Return all thousands-block rows instead of one row per NPA-NXX prefix.
- `ratecenter` (string, required): Telecom rate-center name; case-insensitive input is accepted.
- `state` (string, required): 2-letter state/province/NANP country area code used by TelcoData records.

### `list_new_exchanges` (~166 tokens)

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

Input parameters:

- `api_key` (string): TelcoData API key. Optional if TELCODATA_MCP_API_KEY is set or the HTTP MCP request provides Authorization/X-API-Key.
- `end_date` (string): Inclusive end date in YYYY-MM-DD format.
- `start_date` (string): Inclusive start date in YYYY-MM-DD format.
- `state` (string): Optional 2-letter state/province/NANP country area code filter.

### `lookup_cic` (~101 tokens)

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

Input parameters:

- `api_key` (string): TelcoData API key. Optional if TELCODATA_MCP_API_KEY is set or the HTTP MCP request provides Authorization/X-API-Key.
- `cic` (string, required): 4-digit carrier identification code.

### `lookup_acna` (~95 tokens)

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

Input parameters:

- `acna` (string, required): 3-letter ACNA carrier abbreviation.
- `api_key` (string): TelcoData API key. Optional if TELCODATA_MCP_API_KEY is set or the HTTP MCP request provides Authorization/X-API-Key.

### `get_ocn_profile` (~113 tokens)

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

Input parameters:

- `api_key` (string): TelcoData API key. Optional if TELCODATA_MCP_API_KEY is set or the HTTP MCP request provides Authorization/X-API-Key.
- `ocn` (string, required): 4-character alphanumeric Operating Company Number.

### `search_carrier_profiles_by_rmd_id` (~112 tokens)

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

Input parameters:

- `api_key` (string): TelcoData API key. Optional if TELCODATA_MCP_API_KEY is set or the HTTP MCP request provides Authorization/X-API-Key.
- `rmd_id` (string, required): FCC RMD filing identifier.

### `search_carrier_profiles_by_frn` (~93 tokens)

List carrier profiles sharing an FCC Registration Number (FRN). Use to group related OCNs, carrier names, and RMD records under a common FCC registration.

Input parameters:

- `api_key` (string): TelcoData API key. Optional if TELCODATA_MCP_API_KEY is set or the HTTP MCP request provides Authorization/X-API-Key.
- `frn` (string, required): FCC Registration Number.

### `list_ocn_prefixes` (~184 tokens)

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

Input parameters:

- `api_key` (string): TelcoData API key. Optional if TELCODATA_MCP_API_KEY is set or the HTTP MCP request provides Authorization/X-API-Key.
- `ocn` (string, required): 4-character alphanumeric Operating Company Number.

### `list_tandem_prefixes` (~200 tokens)

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

Input parameters:

- `api_key` (string): TelcoData API key. Optional if TELCODATA_MCP_API_KEY is set or the HTTP MCP request provides Authorization/X-API-Key.
- `tandem_clli` (string, required): Tandem switch CLLI or CLLI prefix, 6 to 11 alphanumeric characters.

### `list_lata_prefixes` (~179 tokens)

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

Input parameters:

- `api_key` (string): TelcoData API key. Optional if TELCODATA_MCP_API_KEY is set or the HTTP MCP request provides Authorization/X-API-Key.
- `lata` (string, required): 3- or 4-digit LATA number.

### `list_state_area_codes` (~109 tokens)

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

Input parameters:

- `api_key` (string): TelcoData API key. Optional if TELCODATA_MCP_API_KEY is set or the HTTP MCP request provides Authorization/X-API-Key.
- `state` (string, required): 2-letter state/province/NANP country area code used by TelcoData records.

### `get_switch` (~161 tokens)

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

Input parameters:

- `api_key` (string): TelcoData API key. Optional if TELCODATA_MCP_API_KEY is set or the HTTP MCP request provides Authorization/X-API-Key.
- `clli` (string, required): Full 11-character switch CLLI code.

### `list_downloads` (~87 tokens)

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

Input parameters:

- `api_key` (string): TelcoData API key. Optional if TELCODATA_MCP_API_KEY is set or the HTTP MCP request provides Authorization/X-API-Key.

### `get_download_metadata` (~104 tokens)

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

Input parameters:

- `api_key` (string): TelcoData API key. Optional if TELCODATA_MCP_API_KEY is set or the HTTP MCP request provides Authorization/X-API-Key.
- `download_hash` (string, required): Opaque download hash returned by list_downloads.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/us-telcodata-telcodata/api#diagnostics

## Score history

- 2026-11-05: 66
- 2026-11-04: 66
- 2026-11-03: 65
- 2026-11-02: 65
- 2026-11-01: 65
- 2026-10-31: 64
- 2026-10-30: 64
- 2026-10-29: 63
- 2026-10-28: 63
- 2026-10-27: 62

## Common questions

### What is the us.telcodata/telcodata MCP server?

us.telcodata/telcodata is an MCP server listed in the public MCP registry as us.telcodata/telcodata. North American telephone numbering data: carriers, rate centers, OCNs, and number history. This page covers its hosted endpoint (https://api.telcodata.us/mcp).

### Is the us.telcodata/telcodata MCP server safe to use?

us.telcodata/telcodata scores 66 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 us.telcodata/telcodata MCP server expose?

us.telcodata/telcodata exposes 21 tools: get_me, get_exchange, search_record_history, get_exchange_thousands, lookup_tn, and 16 more. Their descriptions and schemas cost roughly 3,376 tokens of context every time the server is loaded.

### Does the us.telcodata/telcodata MCP server require authentication?

No. We connected to us.telcodata/telcodata without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the us.telcodata/telcodata MCP server still maintained?

us.telcodata/telcodata 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://api.telcodata.us/mcp
- Authorisation metadata: https://api.telcodata.us/.well-known/oauth-protected-resource/mcp
- Website: https://www.telcodata.us/
- Changelog RSS feed: https://verifymcp.io/servers/us-telcodata-telcodata/api.xml
- Changelog JSON feed: https://verifymcp.io/servers/us-telcodata-telcodata/api.json
- HTML version of this page: https://verifymcp.io/servers/us-telcodata-telcodata/api