MCP server

Let your agent check a phone number, an email address or an IP before it acts on it. Four tools, one URL.

Connect

Add a remote MCP server with this URL and an Authorization header.

https://lookuplab.io/api/mcp

Claude Code

claude mcp add lookuplab https://lookuplab.io/api/mcp --transport http --header "Authorization: Bearer YOUR_API_KEY"

Cursor (mcp.json)

{
  "mcpServers": {
    "lookuplab": {
      "url": "https://lookuplab.io/api/mcp",
      "headers": { "Authorization": "Bearer YOUR_API_KEY" }
    }
  }
}

Tools

Tool	Arguments	Returns
phone_lookup	number, caller_name	valid, line_type, carrier, city, state, ported, lrn, ocn, caller_name
email_verify	email	valid, reason, has_mx, mx_provider, disposable, role_account, smtp
ip_lookup	ip	country, city, timezone, asn, org, hosting, proxy, vpn, tor
dns_check	domain, check, selector	parsed record and issues

What agents do with it

A support agent checks whether the number a customer typed is a mobile before offering to text them.
A sales agent scores an inbound lead on VoIP, disposable email and datacenter IP before booking a call.
A deliverability agent audits SPF, DKIM and DMARC for a new sending domain and writes the fix list.

Questions

Does the MCP server need an API key?

Yes. Tool calls without a key return UPGRADE_REQUIRED. Trial keys with 1,000 credits are free.

Which clients work?

Claude Desktop and Claude Code, Cursor, Windsurf, n8n's MCP Client node, and anything that speaks MCP over streamable HTTP.

Is it the same data as the REST API?

Identical. Same engines, same credits, same caching.

Does it support SSE?

The server answers JSON-RPC over HTTP POST. Clients that require a server-sent events stream are not supported yet.

Get a key