Servidor MCP de Telcodata

• Nombre en el registrous.telcodata/telcodataverificado en el registro MCP

El nombre en el registro está bajo telcodata.us. El registro solo permite usar ese espacio de nombres a quien demuestra control del dominio por DNS o HTTP.

• Estadorespondecomprobado el 2026-10-27
• Herramientas21
• El servidor se llamatelcodata-api
• Versión del servidor1.1.0
• Versión del protocolo2024-11-05

El 2026-10-27 el servidor respondió a initialize y tools/list sin iniciar sesión. Primera respuesta en 303 ms.

• Sus herramientas hacen todos los casos de uso comprobados: look up which carrier holds a phone number; find the switch and rate center for a number.
• Comprobado 6 de los 7 días necesarios para juzgar su fiabilidad.

Lo dicen reglas a partir de las mediciones de arriba. La primera llamada probable la elige un modelo de la lista de herramientas; lee su descripción antes de fiarte.

• Nota INITE MCPtras una semanala nota necesita 7 comprobaciones diarias: 6 hasta ahora
• Qué puede hacer un agente con él2 de 2 casos de uso
• Respondiómidiendo6 de las 7 comprobaciones diarias necesarias para mostrar el porcentaje
• Mediana de la primera respuesta278 ms
• Espacio en el contexto del agente≈ 4462 tokenslas definiciones de todas sus herramientas (21), que el agente lleva en cada turno
• Definiciones de herramientasB · 83 de 100
• Resultados tipados0 de 21 herramientasdeclaran outputSchema: el resultado llega tipado y se lee de una vez

• Parámetros sin descripción: en 1 de 21
• Sin indicar si solo lee o puede destruir: 21 de 21

Un programa comprueba el servidor una vez al día: initialize y tools/list, sin modelo. Los tokens son la longitud de las definiciones, a unos cuatro caracteres por token. La nota promedia seis comprobaciones del nombre, la descripción, el esquema y las anotaciones de cada herramienta; dice lo bien descritas que están, no si funcionan. La nota pondera solo lo medido: si responde (25%), si hace el trabajo del producto (25%), definiciones (20%), contexto (10%), uso (10%) y lo fácil que es conectarse (10%). Lo que no se midió queda fuera, y una instrucción oculta limita la nota a 40. El estado de los servidores MCP de los proveedores: método y números →

• get_me

  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.

• get_exchange

  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…

• search_record_history

  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…

• get_exchange_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…

• lookup_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…

• list_area_code_exchanges

  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…

• geocode_address

  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.

• search_ratecenter

  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…

• list_new_exchanges

  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…

• lookup_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.

• lookup_acna

  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.

• get_ocn_profile

  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.

• search_carrier_profiles_by_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.

• search_carrier_profiles_by_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.

• list_ocn_prefixes

  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…

• list_tandem_prefixes

  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…

• list_lata_prefixes

  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…

• list_state_area_codes

  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.

• get_switch

  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…

• list_downloads

  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.

• get_download_metadata

  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.