Phone Intel MCP Server已验证已精选

What is Phone Intel MCP?

One HTTP (or MCP) call turns a US phone number into a dossier:

• Carrier and line type (mobile, landline, VoIP, toll-free)
• Business match — name, category, address, 7-day hours, open-now, Google rating, Yelp rating
• Caller name where CNAM is available
• Reputation — composite spam-risk score (0–100), robocall / DNC / VoIP-risk flags
• Classification — business, consumer_mobile, consumer_landline, voip, toll_free, or unknown, so the agent knows what tier of answer it got

Built for voice-AI agents (Vapi, Retell, Bland, OpenAI Realtime, and vertical builders on top of them) that need to know who is behind an inbound number — or whether an outbound number is a legitimate business — in under 2 seconds.

Payment

$0.03 USDC per lookup, on Base mainnet, via x402 v1. No signup, no API key, no credit card. The paying wallet needs USDC on Base and nothing else; the facilitator pays gas. You are charged only on a 2xx response — malformed numbers, vendor failures, and rate-limit rejections never settle.

Endpoints

• REST: GET https://phone-intel-mcp.fly.dev/lookup/{phone}
• MCP (Streamable HTTP): POST https://phone-intel-mcp.fly.dev/mcp — tool phone_intel.lookup
• Health: GET https://phone-intel-mcp.fly.dev/health (free, no rate limit)

Example response

{
  "phone": "+15165551234",
  "number_classification": "business",
  "carrier": { "name": "Spectrum Business", "type": "landline" },
  "caller_name": "GARDEN CITY HARDWARE",
  "business_match": {
    "name": "Garden City Hardware",
    "category": "Hardware Stores",
    "address": { "line1": "100 Franklin Ave", "city": "Garden City", "state": "NY", "postal": "11530" },
    "is_open_now": true,
    "rating": { "stars": 4.6, "count": 212 }
  },
  "reputation": { "spam_risk_score": 3, "is_known_robocall": false, "is_dnc_listed": null }
}

Limits

US numbers only (+1). Anything else returns 400 not_us_number. 100 paid lookups per minute per paying wallet. One request in flight per wallet at a time. p95 under 2 seconds on cache hit; up to about 3.4s on a cold business lookup. v1 accepts externally-owned-account (EOA) signatures only. Smart-contract wallets (ERC-1271 / 6492: Safe, Coinbase Smart Wallet, Argent, etc.) are not supported in v1.

See the full README for the x402 payment flow, MCP integration code, error taxonomy, and degraded-section handling.