MCP Server - Connect AI Agents to Phone Intelligence

Overview

The Model Context Protocol (MCP) is the open standard AI assistants use to call external tools. VeriRoute Intel runs a hosted MCP server, so an agent can check a number's current carrier, line type, or spam reputation — or submit a bulk job — in the middle of its own workflow, with no SDK or integration code.

MCP https://verirouteintel.com/api/mcp

Transport: Streamable HTTP (JSON-RPC 2.0 over POST). Works with every MCP client that supports HTTP servers with bearer authentication.

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 (custom connector)

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

Cursor / other MCP clients (mcp.json)

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

Authentication

Use your existing VeriRoute Intel API key as the bearer token — the same key that works on the REST API. Get one from Dashboard → API Keys. Requests without a valid key are refused before anything is processed.

Tools

Tool	What it does
`vri_number_lookup`	Live intelligence for one number: carrier of record, line type, LRN routing, porting activation date; optionally CNAM, spam reputation, and messaging provider (`products`: lrn, cnam, spam, messaging).
`vri_spam_check`	Spam / scam / robocall reputation for one number.
`vri_sms_deliverability`	One verdict for outreach agents: can this number receive SMS, and is now a reasonable time to send? Returns line type, VoIP flag, spam reputation, the recipient's approximate local time, and an 8am–9pm calling-window flag with plain-language reasons. Deliverability signals only — not a legal compliance determination. Every lookup result also carries a `recipient_local` block (timezone, local time, calling-window flag).
`vri_bulk_lookup`	Up to 100 numbers in one call, same product options.
`vri_submit_job`	Submit an async bulk job (up to 10,000 numbers). Balance is reserved up front; the job runs in the background. Larger lists: use `POST /api/v1/jobs`.
`vri_bulk_status`	Progress and status of one of your bulk jobs by `job_id`.

Sandbox

A test key (from Dashboard → Sandbox) works over MCP too: the lookup tools return deterministic sample data for the sandbox magic numbers — no charges, nothing real dipped. Perfect for wiring an agent up before funding.

Billing

Live keys pay the same per-lookup rates as the REST API, deducted from your prepaid balance. Every result reports what it cost (total_charged); failed lookups are not charged. A call that would exceed your available balance is refused up front with the amount needed.

Raw JSON-RPC

For clients you build yourself — one POST per message:

curl -s https://verirouteintel.com/api/mcp \
  -H "Authorization: Bearer YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "jsonrpc": "2.0", "id": 1, "method": "tools/call",
    "params": {
      "name": "vri_number_lookup",
      "arguments": { "phone_number": "13364086644", "products": ["lrn", "spam"] }
    }
  }'

Find us in the MCP ecosystem

This server is published as com.verirouteintel/lookup in the Official MCP Registry, and listed on Smithery and MCP.so. The reference repo lives at GitHub.

MCP Server – Phone Intelligence for AI Agents