telcodata

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

我该使用它吗

质量与安全性

A
描述质量
99%
模式完整度
97%
命名质量
95%
投毒风险
80%
权限匹配度
100%
协议合规性
100%

发现(4)

  • HIGHTool poisoning patterns detected
  • LOWTool 'lookup_acna' description lacks action verb在 lookup_acna 中
  • LOWTool 'search_carrier_profiles_by_rmd_id' name length outside 3-30 range在 search_carrier_profiles_by_rmd_id 中
  • INFOTool description contains placeholder or incomplete text在 get_exchange_thousands 中

基于对工具定义和协议合规性的自动分析。

上下文开销

~4,208token 数(工具定义)
~1.2 KB典型响应大小
对注意力有显著影响(占 128k 上下文窗口的 3.29%)

这是每次将服务器的工具加载到模型上下文窗口时所消耗的大致 token 数。数值越高,可用于其他任务的注意力就越少。

安装

一键安装

将以下内容添加到你的 `claude_desktop_config.json` 文件中:

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

远程端点

https://api.telcodata.us/mcpstreamable-http

它能做什么

工具清单

工具(21)

🟢 只读🟡 写入🔴 删除⚪ 未知
🟢get_me(api_key)

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.

输入模式

{
  "type": "object",
  "properties": {
    "api_key": {
      "description": "TelcoData API key. Optional if TELCODATA_MCP_API_KEY is set or the HTTP MCP request provides Authorization/X-API-Key.",
      "type": "string"
    }
  }
}
🟡get_exchange(api_key, include_blocks, npa, nxx)

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.

输入模式

{
  "type": "object",
  "properties": {
    "api_key": {
      "description": "TelcoData API key. Optional if TELCODATA_MCP_API_KEY is set or the HTTP MCP request provides Authorization/X-API-Key.",
      "type": "string"
    },
    "include_blocks": {
      "default": false,
      "description": "Include individual thousands-block rows for number-pooling detail.",
      "type": "boolean"
    },
    "npa": {
      "description": "3-digit NANP area code.",
      "pattern": "^[2-9]\\d{2}$",
      "type": "string"
    },
    "nxx": {
      "description": "3-digit NANP central-office/exchange code.",
      "pattern": "^[2-9]\\d{2}$",
      "type": "string"
    }
  },
  "required": [
    "npa",
    "nxx"
  ]
}
🟢search_record_history(api_key, clli, field, limit, npa, ...)

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.

输入模式

{
  "type": "object",
  "properties": {
    "api_key": {
      "description": "TelcoData API key. Optional if TELCODATA_MCP_API_KEY is set or the HTTP MCP request provides Authorization/X-API-Key.",
      "type": "string"
    },
    "clli": {
      "description": "Optional 6- to 11-character CLLI or CLLI prefix used to find switch changes.",
      "pattern": "^[A-Z0-9]{6,11}$",
      "type": "string"
    },
    "field": {
      "description": "Optional lowercase tracked field name, such as company, ocn, switch, ratecenter, or type.",
      "pattern": "^[a-z_]{1,64}$",
      "type": "string"
    },
    "limit": {
      "description": "Maximum results; defaults to 100 and is capped by the API's configured maximum page size.",
      "minimum": 1,
      "type": "integer"
    },
    "npa": {
      "description": "Optional 3-digit NANP area code filter.",
      "pattern": "^[2-9]\\d{2}$",
      "type": "string"
    },
    "nxx": {
      "description": "Optional 3-digit central-office/exchange code filter.",
      "pattern": "^[2-9]\\d{2}$",
      "type": "string"
    },
    "ocn": {
      "description": "Optional 4-character Operating Company Number filter.",
      "pattern": "^[A-Z0-9]{4}$",
      "type": "string"
    },
    "source": {
      "description": "Optional tracked source name, not an archive filename.",
      "maxLength": 128,
      "minLength": 1,
      "type": "string"
    },
    "thousands": {
      "description": "Optional thousands-block filter: 0-9 for a pooled block or -1 for the whole-prefix/default record.",
      "maximum": 9,
      "minimum": -1,
      "type": "integer"
    }
  }
}
🟢get_exchange_thousands(api_key, npa, nxx, thousands)

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.

输入模式

{
  "type": "object",
  "properties": {
    "api_key": {
      "description": "TelcoData API key. Optional if TELCODATA_MCP_API_KEY is set or the HTTP MCP request provides Authorization/X-API-Key.",
      "type": "string"
    },
    "npa": {
      "description": "3-digit NANP area code.",
      "pattern": "^[2-9]\\d{2}$",
      "type": "string"
    },
    "nxx": {
      "description": "3-digit NANP central-office/exchange code.",
      "pattern": "^[2-9]\\d{2}$",
      "type": "string"
    },
    "thousands": {
      "description": "Seventh digit of the number, 0-9; use -1 only for the whole-prefix/default aggregate.",
      "maximum": 9,
      "minimum": -1,
      "type": "integer"
    }
  },
  "required": [
    "npa",
    "nxx",
    "thousands"
  ]
}
⚪lookup_tn(api_key, tn)

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.

输入模式

{
  "type": "object",
  "properties": {
    "api_key": {
      "description": "TelcoData API key. Optional if TELCODATA_MCP_API_KEY is set or the HTTP MCP request provides Authorization/X-API-Key.",
      "type": "string"
    },
    "tn": {
      "description": "Dialable phone number in national or international format.",
      "type": "string"
    }
  },
  "required": [
    "tn"
  ]
}
🟡list_area_code_exchanges(api_key, include_blocks, npa)

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.

输入模式

{
  "type": "object",
  "properties": {
    "api_key": {
      "description": "TelcoData API key. Optional if TELCODATA_MCP_API_KEY is set or the HTTP MCP request provides Authorization/X-API-Key.",
      "type": "string"
    },
    "include_blocks": {
      "default": false,
      "description": "Return all thousands-block rows instead of one row per NPA-NXX prefix.",
      "type": "boolean"
    },
    "npa": {
      "description": "3-digit NANP area code.",
      "pattern": "^[2-9]\\d{2}$",
      "type": "string"
    }
  },
  "required": [
    "npa"
  ]
}
⚪geocode_address(api_key, city, language, postal_code, state, ...)

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.

输入模式

{
  "type": "object",
  "properties": {
    "api_key": {
      "description": "TelcoData API key. Optional if TELCODATA_MCP_API_KEY is set or the HTTP MCP request provides Authorization/X-API-Key.",
      "type": "string"
    },
    "city": {
      "type": "string"
    },
    "language": {
      "enum": [
        "en",
        "fr"
      ],
      "type": "string"
    },
    "postal_code": {
      "type": "string"
    },
    "state": {
      "type": "string"
    },
    "street": {
      "type": "string"
    }
  }
}
🟡search_ratecenter(api_key, include_blocks, ratecenter, state)

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.

输入模式

{
  "type": "object",
  "properties": {
    "api_key": {
      "description": "TelcoData API key. Optional if TELCODATA_MCP_API_KEY is set or the HTTP MCP request provides Authorization/X-API-Key.",
      "type": "string"
    },
    "include_blocks": {
      "default": false,
      "description": "Return all thousands-block rows instead of one row per NPA-NXX prefix.",
      "type": "boolean"
    },
    "ratecenter": {
      "description": "Telecom rate-center name; case-insensitive input is accepted.",
      "type": "string"
    },
    "state": {
      "description": "2-letter state/province/NANP country area code used by TelcoData records.",
      "pattern": "^[A-Z]{2}$",
      "type": "string"
    }
  },
  "required": [
    "state",
    "ratecenter"
  ]
}
🟡list_new_exchanges(api_key, end_date, start_date, state)

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.

输入模式

{
  "type": "object",
  "properties": {
    "api_key": {
      "description": "TelcoData API key. Optional if TELCODATA_MCP_API_KEY is set or the HTTP MCP request provides Authorization/X-API-Key.",
      "type": "string"
    },
    "end_date": {
      "description": "Inclusive end date in YYYY-MM-DD format.",
      "format": "date",
      "type": "string"
    },
    "start_date": {
      "description": "Inclusive start date in YYYY-MM-DD format.",
      "format": "date",
      "type": "string"
    },
    "state": {
      "description": "Optional 2-letter state/province/NANP country area code filter.",
      "pattern": "^[A-Z]{2}$",
      "type": "string"
    }
  }
}
⚪lookup_cic(api_key, cic)

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.

输入模式

{
  "type": "object",
  "properties": {
    "api_key": {
      "description": "TelcoData API key. Optional if TELCODATA_MCP_API_KEY is set or the HTTP MCP request provides Authorization/X-API-Key.",
      "type": "string"
    },
    "cic": {
      "description": "4-digit carrier identification code.",
      "pattern": "^\\d{4}$",
      "type": "string"
    }
  },
  "required": [
    "cic"
  ]
}
⚪lookup_acna(acna, api_key)

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.

输入模式

{
  "type": "object",
  "properties": {
    "acna": {
      "description": "3-letter ACNA carrier abbreviation.",
      "pattern": "^[A-Z]{3}$",
      "type": "string"
    },
    "api_key": {
      "description": "TelcoData API key. Optional if TELCODATA_MCP_API_KEY is set or the HTTP MCP request provides Authorization/X-API-Key.",
      "type": "string"
    }
  },
  "required": [
    "acna"
  ]
}
🟢get_ocn_profile(api_key, ocn)

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.

输入模式

{
  "type": "object",
  "properties": {
    "api_key": {
      "description": "TelcoData API key. Optional if TELCODATA_MCP_API_KEY is set or the HTTP MCP request provides Authorization/X-API-Key.",
      "type": "string"
    },
    "ocn": {
      "description": "4-character alphanumeric Operating Company Number.",
      "pattern": "^[A-Z0-9]{4}$",
      "type": "string"
    }
  },
  "required": [
    "ocn"
  ]
}
🟢search_carrier_profiles_by_rmd_id(api_key, rmd_id)

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.

输入模式

{
  "type": "object",
  "properties": {
    "api_key": {
      "description": "TelcoData API key. Optional if TELCODATA_MCP_API_KEY is set or the HTTP MCP request provides Authorization/X-API-Key.",
      "type": "string"
    },
    "rmd_id": {
      "description": "FCC RMD filing identifier.",
      "pattern": "^[A-Za-z0-9._:-]{1,32}$",
      "type": "string"
    }
  },
  "required": [
    "rmd_id"
  ]
}
🟢search_carrier_profiles_by_frn(api_key, frn)

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

输入模式

{
  "type": "object",
  "properties": {
    "api_key": {
      "description": "TelcoData API key. Optional if TELCODATA_MCP_API_KEY is set or the HTTP MCP request provides Authorization/X-API-Key.",
      "type": "string"
    },
    "frn": {
      "description": "FCC Registration Number.",
      "pattern": "^[A-Za-z0-9._:-]{1,32}$",
      "type": "string"
    }
  },
  "required": [
    "frn"
  ]
}
🟢list_ocn_prefixes(api_key, ocn)

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.

输入模式

{
  "type": "object",
  "properties": {
    "api_key": {
      "description": "TelcoData API key. Optional if TELCODATA_MCP_API_KEY is set or the HTTP MCP request provides Authorization/X-API-Key.",
      "type": "string"
    },
    "ocn": {
      "description": "4-character alphanumeric Operating Company Number.",
      "pattern": "^[A-Z0-9]{4}$",
      "type": "string"
    }
  },
  "required": [
    "ocn"
  ]
}
🟢list_tandem_prefixes(api_key, tandem_clli)

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.

输入模式

{
  "type": "object",
  "properties": {
    "api_key": {
      "description": "TelcoData API key. Optional if TELCODATA_MCP_API_KEY is set or the HTTP MCP request provides Authorization/X-API-Key.",
      "type": "string"
    },
    "tandem_clli": {
      "description": "Tandem switch CLLI or CLLI prefix, 6 to 11 alphanumeric characters.",
      "pattern": "^[A-Z0-9]{6,11}$",
      "type": "string"
    }
  },
  "required": [
    "tandem_clli"
  ]
}
🟢list_lata_prefixes(api_key, lata)

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.

输入模式

{
  "type": "object",
  "properties": {
    "api_key": {
      "description": "TelcoData API key. Optional if TELCODATA_MCP_API_KEY is set or the HTTP MCP request provides Authorization/X-API-Key.",
      "type": "string"
    },
    "lata": {
      "description": "3- or 4-digit LATA number.",
      "pattern": "^\\d{3,4}$",
      "type": "string"
    }
  },
  "required": [
    "lata"
  ]
}
🟢list_state_area_codes(api_key, state)

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.

输入模式

{
  "type": "object",
  "properties": {
    "api_key": {
      "description": "TelcoData API key. Optional if TELCODATA_MCP_API_KEY is set or the HTTP MCP request provides Authorization/X-API-Key.",
      "type": "string"
    },
    "state": {
      "description": "2-letter state/province/NANP country area code used by TelcoData records.",
      "pattern": "^[A-Z]{2}$",
      "type": "string"
    }
  },
  "required": [
    "state"
  ]
}
🟢get_switch(api_key, clli)

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.

输入模式

{
  "type": "object",
  "properties": {
    "api_key": {
      "description": "TelcoData API key. Optional if TELCODATA_MCP_API_KEY is set or the HTTP MCP request provides Authorization/X-API-Key.",
      "type": "string"
    },
    "clli": {
      "description": "Full 11-character switch CLLI code.",
      "pattern": "^[A-Z]{6}[A-Z0-9]{5}$",
      "type": "string"
    }
  },
  "required": [
    "clli"
  ]
}
🟢list_downloads(api_key)

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.

输入模式

{
  "type": "object",
  "properties": {
    "api_key": {
      "description": "TelcoData API key. Optional if TELCODATA_MCP_API_KEY is set or the HTTP MCP request provides Authorization/X-API-Key.",
      "type": "string"
    }
  }
}
🟢get_download_metadata(api_key, download_hash)

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.

输入模式

{
  "type": "object",
  "properties": {
    "api_key": {
      "description": "TelcoData API key. Optional if TELCODATA_MCP_API_KEY is set or the HTTP MCP request provides Authorization/X-API-Key.",
      "type": "string"
    },
    "download_hash": {
      "description": "Opaque download hash returned by list_downloads.",
      "type": "string"
    }
  },
  "required": [
    "download_hash"
  ]
}

社区

评价此服务器

证据

最近观测

已验证未记录版本21 个工具