Skip to main content
Glama
Sign In
Telique MCP

Telique MCP

by Ringer
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Telique MCP

Telecom data tools for AI assistants. Query LRN, CNAM, DNO, LERG routing tables, toll-free routing, and more — directly from Claude, ChatGPT, Copilot, Cursor, or Codex.

Install

Pick one install surface.

Surface

Authentication

Use it for

Hosted connector (recommended)

OAuth sign-in in your browser; no API key to copy

Claude, ChatGPT, Codex and any other client that supports remote MCP

npm stdio

Telique API key in ~/.telique/config.json

CI, offline use, clients without remote MCP

Direct REST/GraphQL API

Telique API key (x-api-token)

Your own code, not AI clients. See telique.ringer.tel

Recommended — Hosted connector

  • URL: https://api.telique.ringer.tel/mcp

Add the URL as a remote MCP server, then sign in with your Telique account when the browser opens. The connector gets its own credentials for each session, so never paste a Telique API key into your AI client for this surface.

Claude Code

claude mcp add -s user --transport http telique https://api.telique.ringer.tel/mcp

Then run /mcp in Claude Code and choose Authenticate.

Codex (CLI and Desktop)

codex mcp add telique --url https://api.telique.ringer.tel/mcp
codex mcp login telique

Known issue: Codex currently refuses to start sign-in for the hosted connector (OAuth authorization endpoint origin does not match the authorization server origin). A server-side fix is tracked in #13. Until it ships, use the npm stdio surface with Codex.

claude.ai, Claude Desktop and Claude mobile: open Customize → Connectors, choose Add connector, and add a custom connector with the URL. A connector added on claude.ai also appears in Claude Desktop and mobile.

ChatGPT: open Plugins, choose Add → Add custom MCP server, enter the URL with OAuth authentication, then Continue to sign in. Custom MCP servers depend on your ChatGPT plan and workspace settings.

To reconnect after signing out or revoking access, run the client's authenticate or login step again (/mcp in Claude Code, codex mcp login telique, or Connect in the claude.ai connector or ChatGPT plugin settings).

Switching from npm stdio? telique-mcp setup registers its stdio server as telique too. Remove it before adding the hosted connector (claude mcp remove -s user telique, codex mcp remove telique, or delete the telique entry from the client's JSON config) so the two surfaces don't shadow each other.

mcp.telique.ringer.tel is retired and no longer resolves. If a client still points at it, remove that entry and add the URL above.

npm stdio — advanced / offline

For CI, local development, or clients that don't support remote MCP. Stores a long-lived tlq_… token at ~/.telique/config.json.

npm install -g telique-mcp
telique-mcp setup

The setup wizard detects installed AI clients and registers automatically.

⚠️ Install only one surface. Running both exposes the same tools under overlapping namespaces and causes confusing shadowing of tool results.

Related MCP server: areacode-mcp

What You Get

Tool

What it does

lookup_tn

Full profile of any phone number (LRN, CNAM, DNO, LERG — all in one call)

lrn_lookup

Local Routing Number and carrier (SPID) for a phone number

cnam_lookup

Caller ID name for a phone number

dno_check

Check if a number is on the Do Not Originate list (spoofing indicator)

lerg_query

Query 27 LERG telecom routing tables (carriers, switches, rate centers, LATAs)

lerg_tandem

Tandem switch routing for an NPA-NXX

lerg_complex_query

Multi-table JOIN queries across LERG tables

lerg_table_info

List tables or get schema for any of 27 LERG tables

routelink_lookup

Carrier (CIC) or Responsible Org (ROR) for a toll-free number

routelink_ror_query

List toll-free numbers or CPRs managed by a Responsible Org

routelink_cpr

Full call routing decision tree for a toll-free number

graphql_query

GraphQL queries against LSMS (live porting data) or LERG (routing reference)

lrn_relationship_query

Find phone numbers by LRN, SPIDs by phone number, etc.

Example Queries

Once installed, just ask your AI assistant:

  • "Look up the caller ID for 303-629-8301"

  • "What carrier owns NPA-NXX 720-708?"

  • "Is 877-382-4357 on the Do Not Originate list?"

  • "Show me the tandem routing for 303-629"

  • "Who is the RespOrg for 800-221-1212?"

  • "Give me a full profile on 303-629-8301"

API Key

The hosted connector needs no API key; you sign in instead. The npm stdio surface and the direct API need one. Every account includes one, free accounts too: get yours at app.telique.ringer.tel. Free-account keys allow 10 requests per 60 seconds.

Enter your key during setup or update it later by running telique-mcp setup again.

Supported Clients

The hosted connector works with any client that supports remote MCP with OAuth (see Install).

For the npm stdio surface, the setup wizard auto-detects and registers with:

  • Claude Code

  • Claude Desktop

  • Cursor

  • GitHub Copilot (VS Code)

  • Codex CLI

  • Codex Desktop (macOS — also configured automatically when only the .app is installed; CLI and Desktop share ~/.codex/config.toml)

See INSTALL.md for manual configuration and platform-specific paths.

Links

Available Tools

8 tools
cnam_lookupA
Read-only

Look up the Caller Name (CNAM) for a phone number via TransUnion LIDB. Returns the calling_name (up to 15 characters), calling_name_status (available/unavailable), and presentation_indicator (allowed/restricted). Results are cached server-side for 24 hours.

Inputs: phone_number (required).

dno_checkA
Read-only

Check if a phone number is on the Do Not Originate (DNO) list. DNO numbers should never appear as a caller ID because they belong to entities that only receive calls (e.g., IRS, major banks). A match indicates potential caller ID spoofing. Supports prefix matching (3, 6, 7, or 10 digit patterns).

Inputs: phone_number (required).

lerg_table_infoA
Read-only

List all 27 LERG tables or get metadata/schema for a specific table. LERG is static telecom reference data. Key tables: lerg_1 (OCN/carrier directory), lerg_6 (NPA-NXX block assignments with switch, LATA, rate center), lerg_7 (switch details), lerg_7_sha (switch homing arrangements/tandems), lerg_12 (LRN registry).

Inputs: table_name.

lerg_tandemA
Read-only

Look up tandem routing information. Query by NPA+NXX, switch CLLI, tandem CLLI, or carrier name pattern. Returns tandem switch, OCN, LATA, and routing path via SQL JOINs across lerg_6, lerg_7_sha, and lerg_1.

Inputs: npa, nxx, name, limit, +3 more.

lrn_relationship_queryA
Read-only

Query relationships in the LSMS database. Find phone numbers by LRN, SPIDs by LRN or phone number, or LRNs by SPID or phone number. Queries live NPAC porting data (not static LERG reference data).

Inputs: value (required), query_type (required).

routelink_lookupA
Read-only

Look up toll-free number routing. Resolves a CRN (toll-free number) to its carrier (CIC), Responsible Organization (ROR), or both. CIC lookup interprets the CPR decision tree using the caller's ANI and LATA to determine which carrier handles the call.

Inputs: crn (required), lookup_type (required), ani, lata.

routelink_ror_queryA
Read-only

List toll-free numbers (TFNs) or Call Processing Records (CPRs) associated with a Responsible Organization (ROR). Use this to explore which toll-free numbers a specific organization manages.

Inputs: ror (required), resource_type (required), limit, offset.

telique_statusA
Read-only

Returns the Telique MCP server version, authentication mode, and API connectivity status. Use this when asked about the server version or connection status.

Inputs: no named parameters.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A4.3/5.0

    Scored across 8 tools

    Disambiguation5/5

    Each tool targets a unique telecom query function with no overlap: caller name, do-not-originate, LERG metadata, tandem routing, LRN porting, toll-free routing, and server status. Agent can reliably distinguish them.

    Naming Consistency5/5

    All tool names follow a predictable verb_noun pattern in snake_case, with clear prefixes per domain (cnam, dno, lerg, lrn, routelink, telique). Naming is uniform and easy to parse.

    Tool Count5/5

    With 8 tools, the server covers a focused but complete telecom lookup domain without excessive or minimal tools. Each tool earns its place.

    Completeness5/5

    The tool surface covers all essential telecom query types: CNAM, DNO, LERG reference, LRN porting, toll-free routing, and server metadata. No obvious dead ends or missing operations for its stated purpose.

    Maintenance

    ActivityMaintained
    ResponsivenessOutdated data

    Resources

    Related MCP Connectors

    Related MCP Servers

    • areacode-mcp

      riv-lc
      A
      license
      A
      quality
      D
      maintenance
      Provides North American (NANP) area code and phone number intelligence for AI agents, including area code lookup, phone validation, carrier info, city/state coverage, local time, and scam context.
      8
      55 npm
      MIT

    • telesign-mcp

      mdp18
      A
      license
      A
      quality
      D
      maintenance
      Enables AI assistants to send SMS messages, verify phone numbers via OTP, assess fraud risk, and access TeleSign API documentation through natural language.
      8
      4 npm
      Apache 2.0
    • TCXC MCP Server

      TCXC MCP Serverofficial

      TelecomsXChangeAPi
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables AI assistants to interact with the TelecomsXChange wholesale telecom API for voice termination, SMS, DID management, eSIM, and account operations through 55 tools and 7 guided workflows using natural language.
      3
      MIT