Use numlookupapi with AI agents (MCP)
numlookupapi ships a hosted Model Context Protocol (MCP) server. AI agents and assistants — Claude, Cursor, VS Code and any other MCP-capable client — can call the API as native tools, no SDK or glue code required.
https://api.numlookupapi.com/mcp
Connect in seconds
Using Claude Code:
claude mcp add --transport http numlookupapi https://api.numlookupapi.com/mcp --header "apikey: YOUR_API_KEY"
Or add it to any MCP client configuration:
{
"mcpServers": {
"numlookupapi": {
"url": "https://api.numlookupapi.com/mcp",
"headers": { "apikey": "YOUR_API_KEY" }
}
}
}
With the configuration above, every request needs your API key, including the MCP handshake and listing the tools. Sign up for a free API key and send it as the apikey header.
Sign in instead of an API key
MCP clients that support sign-in (OAuth), such as Claude’s custom connectors, can sign in instead of sending a key. In Claude, open Settings → Connectors → Add custom connector and enter https://api.numlookupapi.com/mcp. The client opens a sign-in page on app.numlookupapi.com: sign in or sign up, and approve the connection (as the team’s owner or an admin). The client then holds a key of your team that lasts an hour and renews itself; its tool calls count against your plan like any other request. You can disconnect it at any time under API keys → Connected apps in the dashboard. For your own code, use an API key.
Available tools
| Tool | Endpoint | Description |
|---|---|---|
validateNumber | GET /v1/validate/{number} | Validate a phone number |
validateBatch | POST /v1/validate | Validate many phone numbers at once |
getStatus | GET /v1/status | Account quota status |
Tool calls are metered like regular API requests and return the same machine-readable errors, so your agent always knows how to proceed. Full details in the MCP documentation.