PeopleSearch.im is answering right now. Last checked 4 min ago. It exposes 12 tools.
Plain-English people search with verified work emails, email verification and LinkedIn lookup.
Uptime history
12 days of history · worst day 30%
12 days agonow
100.0%
Uptime 24h
92 of 92 checks
12
Tools
read from the server
317 ms
Response time
average over 24h
open, no key
Access
streamable-http
Nothing serious here today
Today is the operative word: we check PeopleSearch.im every 15 minutes and re-read its code on every release. Watch it and you find out the day that stops being true.
Connect this server
Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 4 min ago.
run in your terminal
claude mcp add email-finder --transport http https://peoplesearch.im/api/mcp~/Library/Application Support/Claude/claude_desktop_config.json
{
"mcpServers": {
"email-finder": {
"url": "https://peoplesearch.im/api/mcp"
}
}
}~/.codex/config.toml
[mcp_servers.email-finder]
url = "https://peoplesearch.im/api/mcp".cursor/mcp.json
{
"mcpServers": {
"email-finder": {
"url": "https://peoplesearch.im/api/mcp"
}
}
}.vscode/mcp.json
{
"mcpServers": {
"email-finder": {
"url": "https://peoplesearch.im/api/mcp"
}
}
}Available tools 12
Read directly from the server with tools/list, grouped by what they act on.
If a tool disappears, we record the date.
company
company_search
Search a global company database in plain English (for example 'Series B fintech companies in London with 50-200 employees') and get matching companies with industry, size, location and website. Searching companies is FREE and spends no credits.
find_company_emails
Given a company domain or name, return the contactable role-based email addresses discovered for that organization (such as contact@, sales@, support@), each with a confidence level. Use this for reaching a company inbox, not a specific named person (for a named person use find_people or find_linkedin_profile). Spends 2 credits, refunded if none are found.
lookup
lookup_company
Turn a LinkedIn company URL into firmographic data: industry, size, location and website. Spends 1 credit, refunded if the company cannot be retrieved.
lookup_linkedin_profile
Turn a LinkedIn profile URL into clean structured data: name, current role and company, and location. Spends 2 credits, refunded if the profile cannot be retrieved.
people
find_people
The list-building tool. Re-runs a plain-English people search and unlocks up to `count` full profiles in ONE atomic charge: 1 credit per newly unlocked person, and anyone you already own is free. Returns each person's real name, title, company, location, LinkedIn URL and an `id`. Emails are NOT fetched here (that is a separate credit): after unlocking, call fetch_email with each person's `id` to get their verified work email. WARNING for autonomous use: this can spend up to `count` credits in a single call, so choose `count` deliberately and confirm with the user before large batches. Returns an out-of-credits error instead of overspending.
people_search
Search a global professional database in plain English (for example 'Heads of Marketing at Series B SaaS in New York') and get a sample of matching people plus the true total match count. Results are masked previews (a masked name, role, industry, company size and location) and each one carries an opaque `token`. Searching is FREE and spends no credits: use it to validate that the right people exist before you pay. To get a person's real name, LinkedIn and verified email, pass their token to reveal_profile, or use find_people to unlock a batch in one call.
credits
check_credits
Return the current credit balance for the API key making the request. Free and read-only. Use it before a large find_people call to confirm there are enough credits.
email
fetch_email
Look up the verified professional (work) email for a person you have already unlocked with find_people (or reveal_profile). Pass their `id`. Spends 1 credit, refunded automatically if no email is found. The lookup is live: if it returns emailStatus 'searching', call fetch_email again with the same id (no extra charge) to collect the result once it resolves. Returns a professional address, never a personal one; not every person has a findable work email.
linkedin
find_linkedin_profile
Find the LinkedIn profile URL for a named person. Provide their first and last name; adding the company or domain sharply improves the match. Spends 2 credits, refunded if no confident match is found.
reveal
reveal_profile
Unlock ONE person from a people_search result. Pass the `token` from that result. Spends 1 credit and returns the full profile: real name, current title and company, location and LinkedIn URL. Set `include_email` to true to also look up their verified professional (work) email in the same call, which spends 1 more credit that is refunded if no email is found. Revealing the same person again is free (idempotent). The email is looked up live and may take a moment: if it returns emailStatus 'searching', call reveal_profile again with the same token (no extra charge) to collect it.
reverse
reverse_email_lookup
Turn a professional email address into the real person behind it and their LinkedIn profile. Best for work emails; free-mailbox addresses often have no public profile to match. Spends 13 credits (this is the single most expensive lookup), refunded automatically if no match is found.
verify
verify_email
Check whether an email address exists and is safe to send to, before it bounces. Returns a deliverability verdict (deliverable, undeliverable, or unknown) without sending anything. Spends 1 credit, refunded if no verdict can be reached.
Endpoints
| URL | Transport | State | Latency | Checked |
|---|---|---|---|---|
| https://peoplesearch.im/api/mcp | streamable-http | answering | 306 ms | 4 min ago |
Alternatives to PeopleSearch.im
same job, measured the same wayProspeo MCP Server
by prospeo
Prospeo: Find, search, and enrich people and companies with verified emails and mobile numbers.
Leadloadz
by ali1041
B2B lead search and email verification MCP server
Snov MCP Server
by snov
Snov.io: lead discovery, email verification, enrichment, CRM, and LinkedIn automation actions.
Anymail Finder
by anymailfinder
Find verified work emails from a name, company, role or LinkedIn URL, and verify emails you have.
CLI
by kanta
Kanta Verify, Find, and Database: email verification, email finding, and B2B contact search.
SalesQL
by salesql
Find verified B2B emails and phone numbers; search and enrich people and companies for prospecting.
MCP People Finder
by mambabuilt
Find people at a company by role, seniority and department, with verified business emails.
Emailfinder MCP
by xinxinhenaixin
Find verified professional emails by name, domain, LinkedIn, or role.
PeopleSearch.im — questions
Answers built from our own checks of this server.
What can PeopleSearch.im do?
It exposes 12 tools, read directly from the server on our last check. Among them: check_credits, company_search, fetch_email, find_company_emails, find_linkedin_profile, find_people and 6 more. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README.
How MCP servers expose tools in the first place →
What is PeopleSearch.im mostly used for?
Its tools cluster around people, lookup and company. That is what this server is built to work with — the grouping comes from the actual tool names, not from a category we assigned.
Is PeopleSearch.im working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 92 of 92 checks got a reply (100.0%), average response time 317 ms. The bar chart above shows every period we have measured.
How do I connect PeopleSearch.im?
Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.
Does PeopleSearch.im need an API key?
No. PeopleSearch.im completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 12 of them are readable on this page. This is what we observed, not what the docs claim.
How fast is PeopleSearch.im?
It answers our handshake in 317 ms on average, which is faster than 48% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.