Connect the PersonIQ MCP server and Claude gains 18 tools for US people search, reverse phone lookup, property and owner records, identity verification and source-cited web research. It works in Claude Desktop, Claude Code and Claude web, takes about a minute, and requires no code.
Sign in to the developer console, declare a permissible purpose, and generate a key. It begins pk_live_ and is shown once. 4 tools are free to call, so you can verify the connection before buying credits.
Open Settings, go to Developer, and edit the MCP configuration file. Add the personiq entry, then restart Claude.
{
"mcpServers": {
"personiq": {
"url": "https://mcp.personiq.io/mcp",
"headers": {
"Authorization": "Bearer pk_live_YOUR_KEY"
}
}
}
}One command in your terminal. Add --scope user to make it available in every project rather than just this one.
claude mcp add --transport http personiq https://mcp.personiq.io/mcp \
--header "Authorization: Bearer pk_live_YOUR_KEY"Add a custom connector pointing at https://mcp.personiq.io/mcp — the /mcp path is required, the bare domain returns 404. No key is involved: PersonIQ is a full OAuth 2.1 authorization server with PKCE and dynamic client registration, so Claude registers itself, sends you to a PersonIQ consent screen, and you tick the scopes you want to grant. Untick anything you do not want the connector to have — narrowing always works, and widening is impossible even if the consent page were tampered with.
Ask Claude: “What is my PersonIQ balance?” The get_account tool is free, so a correct answer proves authentication without spending anything. If Claude says it has no such tool, the client has not reloaded its MCP config — restart it.
“Who is calling me from 661-555-0100?”
Reverse phone lookup, then carrier and spam risk on the same number.
“Find Jane Doe in Austin, TX and tell me which of her phone numbers is current.”
One person search, then reasoning over the returned phone history.
“Pull every absentee-owned single family home in ZIP 93312 with high equity, then unlock the top five owners.”
A filtered property search, then a quoted unlock on each parcel you pick.
“Does the phone number on this lead form actually belong to the name on it?”
An identity match with a confidence score, before you spend a dime on outreach.
“Research this person on the public web and cite your sources.”
A source-cited intelligence pass matched to the verified identity.
“Who owns 123 Main St, Bakersfield CA, and how do I reach them?”
An address lookup, an owner unlock, and a resident skip trace.
Yes, once you connect the PersonIQ MCP server. Claude then has a reverse phone lookup tool plus a separate carrier and spam intelligence tool, and it picks between them based on what you asked for. Without a connected data source, Claude has no access to phone records at all.
Claude Desktop, Claude Code and the Claude web app. Desktop and Code take the endpoint URL with an API key header. The web app connects as a custom connector over OAuth, where you approve scopes on a consent screen instead of pasting a key.
No, and you should not. Desktop and Code read the key from a config file, and the web connector uses OAuth so no key is involved. A key pasted into a conversation ends up in the transcript.
Not on the expensive tools. Anything costing more than one credit returns a quote that Claude must confirm before the call runs, and every response tells you what it cost and what your balance is now. Cheap reads run directly.
Ask Claude to list its PersonIQ tools, or ask it for your account balance — get_account is free to call, so it confirms authentication without spending anything.
Using ChatGPT instead? Connect the ChatGPT custom connector →