Lookup MCP server

VeriRoute Intel MCP Server

Tells your agent whether a number is safe to call or text right now. Live reads of the U.S. and Canadian phone networks — carrier of record, line type, LRN, CNAM caller ID, spam/scam reputation, SMS deliverability, and a TCPA 8 a.m.–9 p.m. calling-window verdict — plus bulk lookups. Every query gets a fresh dip, never stale cached data. Free sandbox key, no card required. Pay per lookup with no minimums.

This is a hosted (remote) MCP server — nothing to install or run.

return deterministic sample data with zero charges, perfect for wiring an agent up before funding.

• Endpoint: https://verirouteintel.com/api/mcp (Streamable HTTP, JSON-RPC 2.0)
• Auth: Authorization: Bearer
• Docs: https://verirouteintel.com/api-docs/mcp
• Get a key: https://verirouteintel.com/dashboard/api-keys — free sandbox test keys

Connect

Claude Code (CLI)

claude mcp add --transport http vri https://verirouteintel.com/api/mcp \
  --header "Authorization: Bearer YOUR_API_KEY"

Claude.ai / Claude Desktop

Add a custom connector with URL https://verirouteintel.com/api/mcp and header Authorization: Bearer YOURAPIKEY.

Cursor and other MCP clients (mcp.json)

{
  "mcpServers": {
    "vri": {
      "url": "https://verirouteintel.com/api/mcp",
      "headers": { "Authorization": "Bearer YOUR_API_KEY" }
    }
  }
}

Tools

Billing

Live keys pay the same per-lookup rates as the REST API from a prepaid balance. Every result reports what it cost; failed lookups are never charged, and a call that would exceed your available balance is refused up front.

Use cases

• Clean calling lists before dialing (dead/ported/VoIP detection)
• Check your own outbound caller IDs for "Spam Likely" labeling
• Verify line type before sending SMS
• Enrich CRM records with live carrier data — from inside an agent workflow

© First Light Holdings, LLC, DBA VeriRoute Intel · Terms · Privacy

Directories

Published in the Official MCP Registry as com.verirouteintel/lookup · Smithery · MCP.so

Local stdio (CI, offline, or clients without remote MCP)

A zero-dependency Node shim, published to npm, forwards to the hosted server:

VRI_API_KEY=YOUR_API_KEY npx veriroute-intel-mcp

Or in an mcp.json-style client config:

{
  "mcpServers": {
    "vri": {
      "command": "npx",
      "args": ["-y", "veriroute-intel-mcp"],
      "env": { "VRI_API_KEY": "YOUR_API_KEY" }
    }
  }
}

Discovery works without a key; tool calls need one (free sandbox test keys return sample data with zero charges). Prefer the hosted endpoint whenever your client supports remote MCP.