first-party phone validation, now MCP-native
Your AI agent can now verify a phone, email, or IP mid-workflow
Paste one URL into Claude, Cursor, or ChatGPT and click Connect with 1Lookup. Your agent gets five tools to check contacts and flag fraud. No API key to paste, and every check bills to the plan you already have.
https://app.1lookup.io/api/mcpNo API key · Works in Claude, Cursor, ChatGPT, and any MCP client.
{ "phone_number": "4155550132", "country_code": "US", "valid": true, "reachable": true, "line_type": "mobile", "carrier": "Verizon Wireless", "dnc_status": "not_listed", "fraud_score": 15, "risk_level": "low", "tokens_used": 1}
Setup takes about a minute
No SDK to install, no keys to manage, no config file. The URL is the whole integration.
you ▸ add the URL
Paste https://app.1lookup.io/api/mcp into the connector settings of Claude, Cursor, ChatGPT, or any MCP client.
Claude · Cursor · ChatGPT · any MCP client
you ▸ connect with 1Lookup
Click Connect, sign in, and approve access with OAuth 2.1 — no API key changes hands.
agent ▸ validate anything
The five tools appear in your client, and your agent starts checking phones, emails, and IPs on demand, billed to your plan.
The five tools your agent gets
Each one maps to a single call your agent already knows how to make. Three checks for phone, email, and IP, plus bulk for whole lists and an account read so it can pace itself.
Before your agent dials, texts, or saves a number, it confirms the line is real and active, and pulls line type, carrier, DNC status, and a fraud score. No more acting on a dead or risky number.
validate_phone("+1 415 555 0132") → mobile · Verizon · reachable · risk 15Your agent checks that an address exists and isn't disposable, role-based, or on a bad domain before it sends. Bounces stay down and your sender reputation stays intact.
verify_email("j.ramos@acme.co") → valid · not disposable · deliverable 98Your agent geolocates an IP and flags proxies, VPNs, Tor, and datacenter ranges, so it can catch fake signups and risky sessions the moment they happen.
ip_lookup("72.14.201.5") → datacenter · hosting · risk 62Your agent validates a whole list of phones or emails in a single call instead of looping one lookup at a time. List hygiene without the boilerplate.
bulk_verify([ …1,000 emails ]) → 1,000 checked · 1 credit eachYour agent checks remaining credits and plan status before a large run, so it can pace itself and never stalls mid-task on an empty balance.
get_account() → plan: growth · credits: 48,210 remainingSee it mid-conversation
Real tool calls with the real response shape, not staged chat bubbles.
{ "phone_number": "4155550132", "country_code": "US", "valid": true, "reachable": true, "line_type": "mobile", "carrier": "Verizon Wireless", "dnc_status": "not_listed", "fraud_score": 15, "risk_level": "low", "tokens_used": 1}
Phone, email, and IP through one connector
Most setups make your agent wire up three vendors with three separate bills. Here it checks all three through one connector, one credit per check, on the plan you already have.
Results cached 7 days · Data refreshed daily
Your key never leaves your account
Every connector raises the same two worries: what can it touch, and where does my key end up. OAuth 2.1 answers both.
OAuth 2.1, not pasted keys
You authorize with your 1Lookup login and the client receives a scoped token. Your API key never goes into a prompt, a config file, or a third-party server.
Runs on the plan you already have
Every call spends the same credits as the API and honors your plan's limits and gating. No new billing to set up.
One connector, three data types
Phone, email, and IP validation under a single credit system, so your agent isn't wiring up separate vendors.
Results cached for 7 days
Identical lookups return from cache within the window, so repeated checks stay fast and consistent.
Data refreshed daily
Phone and carrier data is updated every 24 hours from primary sources, not recycled on a monthly cycle.
Revoke whenever
Remove the connector's access from your 1Lookup account at any time.
1Lookup wants to connect to your AI client
Read-only access to 5 tools
OAuth 2.1 · scoped, revocable token
Where teams are putting it to work
Anywhere an agent acts on a phone, email, or IP, a quick check keeps it from running on bad data.
AI SDR & outreach agents
Validate a number and email before the agent dials, texts, or sends, so it never burns a message on a dead line or a spam trap.
Enrichment & data agents
Clean a whole list mid-pipeline with bulk_verify instead of looping one lookup at a time.
Signup & fraud flows
Score the IP and email at the point of action to catch fake signups and risky sessions the moment they happen.
Straight answers, including the annoying ones
Credits, security, and what actually happens when you connect.
Yes. Each tool call spends credits from your 1Lookup plan at the same rate as our API — one credit per phone, email, or IP lookup, and one credit per record for bulk_verify. Your agent can call get_account first to check the balance before a big run.
you ▸ ship it
Add it in about a minute
Add one URL, click Connect, and every phone, email, and IP your agent touches gets checked against the plan you already have.
https://app.1lookup.io/api/mcpProgrammatic access is a paid feature — a 7-day trial is available.