mcpbeat Sign in

PeopleSearch.im MCP Server

by peoplesearch Your server? Claim it
answering

PeopleSearch.im is answering right now. Last checked 4 min ago. It exposes 14 tools.

People search, LinkedIn lookup and verified work emails for AI agents. First search needs no login.

Uptime history 63 days of history · worst day 0%
63 days agonow
8.7%
Uptime 24h
8 of 92 checks
14
Tools
read from the server
385 ms
Response time
average over 24h
open, no key
Access
streamable-http

What changed 37

Every tool that appeared, vanished or quietly changed what it asks for. Recorded since 26 September 2026. No other catalogue keeps this.

4 Nov 4 tool descriptions were rewritten company_search, find_linkedin_profile, find_people and 1 more
4 Nov 2 tools changed the parameters they ask for find_linkedin_profile, find_people
4 Nov a tool appeared find_email_from_linkedin
28 Oct 2 tools changed the parameters they ask for find_people, people_search
28 Oct a tool description was rewritten verify_email
23 Oct 2 tools changed the parameters they ask for find_people, people_search
19 Oct 2 tools changed the parameters they ask for find_people, people_search
18 Oct 2 tools changed the parameters they ask for find_people, people_search
17 Oct 2 tools changed the parameters they ask for find_people, people_search
13 Oct 3 tools changed the parameters they ask for company_search, find_people, people_search
and 16 more, back to 26 September 2026

PeopleSearch.im does not always answer

Over the last week it answered 16.2% of our checks. We check every 15 minutes, so you hear about the next outage within the hour — not from your users.

Three servers free · no card

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
Settings → Connectors → Add custom connector, then paste this address
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
{
  "servers": {
    "email-finder": {
      "type": "http",
      "url": "https://peoplesearch.im/api/mcp"
    }
  }
}

Available tools 14

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 and get matching companies with industry, size, location and website. Three ways to ask: a company's website ('warmly.ai') returns that one company, the most exact way to identify one; a company's name ('Warmly') returns the companies of that name; a description in plain English ('Series B fintech companies in London with 50-200 employees') returns the companies that fit it. Searching companies uses no credits. It also works before a PeopleSearch.im account is connected: without one it returns up to 3 companies per search, up to 10 searches a day.
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.
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.
find_email_from_linkedin
Given a LinkedIn profile URL, return that person's professional email address, verified live, with their current role and company. Use this when you have someone's LinkedIn page and need to email them; for a name and company without a URL use find_work_email. Spends 3 credits, refunded if no email is 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. Runs a people search exactly as people_search does (the same `filters` or `query`, including its automatic broadening, reported in `broadenedBy`) and unlocks up to `count` full profiles in ONE atomic charge: 1 credit per newly unlocked person, and anyone you already own is free. Pass the same filters you checked with people_search, so you pay for the people you saw. Returns each person's real name, title, company, location, LinkedIn URL and an `id`. Set `include_email` to true when the user wants to contact them: each person's verified work email is looked up in the same call, 1 more credit each, refunded when none is found (lookups still running are collected free with fetch_email and the id). Without it, call fetch_email with each person's `id` later. WARNING for autonomous use: this can spend up to `count` credits in a single call (twice that with emails), 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 for people and get a sample of matches plus the true total match count. Ask with `filters` (recommended: state each part exactly, for example {"job_titles": ["M&A Associate", "Investment Banking Associate"], "locations": ["Frankfurt", "Munich"], "industries": ["Investment Banking"], "schools": ["University of Mannheim"]}) or with `query`, a plain-English sentence that is parsed for you (for example 'Heads of Marketing at Series B SaaS in New York'). Results are masked previews (a masked name, role, industry, company size and location) and each one carries an opaque `token`. Searching uses no credits: use it to check that the right people come back before revealing anyone, and refine the filters if they do not. To look up one named person, give `first_name` and `last_name` with their company or company domain when known. For a kind of employer no industry names exactly, use `company_keywords` (words its own description contains, for example ["hostel"] or ["SEO"] with industries ["Marketing Services"]). If nothing matches exactly, the search broadens itself: a job title is read more broadly first (`broadenedRole` gives the title as asked and as searched), then the least essential filters are dropped and `broadenedBy` names them; `ignored` lists any filter that could not be applied. To get a person's real name, LinkedIn and verified email, pass their token to reveal_profile, or use find_people with the same filters to unlock a batch in one call. It also works before a PeopleSearch.im account is connected: without one it returns up to 3 previews per search, up to 10 searches a day.
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.
linkedin
find_linkedin_profile
Find a named person's LinkedIn profile: its URL with their current title, company and location. Give their first and last name, plus their company (name or website) and/or job title when you know them. A name only one person has is found from the name alone; when several people share it, the answer says how many and nothing is charged, so call again with their company or job title. 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. Checks the format and the domain's mail servers, then asks the mail provider about the exact mailbox, without sending anything. Returns `verdict`: deliverable, undeliverable, risky (a disposable address) or unknown (the mail server neither confirmed nor rejected the mailbox), with `reason`. Spends 1 credit for the mailbox check; a malformed address or a domain that takes no email is answered free, and an unknown is refunded.
work
find_work_email
Find and verify the professional (work) email of a person you can name: give their first name, last name and the company they work at (its domain, such as acme.com, matches best; a company name also works). Returns the address with a confidence label (Verified or Likely) and their LinkedIn profile when it can be matched. Spends 2 credits, refunded automatically if no email is found. People who asked to be removed from PeopleSearch.im are never looked up. To find people you cannot name yet, use people_search or find_people, then fetch_email.

Endpoints

URLTransportStateLatencyChecked
https://peoplesearch.im/api/mcp streamable-http answering 258 ms 4 min ago

Alternatives to PeopleSearch.im

same job, measured the same way
Scrupp
by wismhero-maker

Export LinkedIn, Sales Navigator and Apollo searches; find decision makers and verified work emails

47 installs/wk local only
InvestorLists.vc investor database
by investorlists

Person-checked US VC firms and startup investors with verified work emails and LinkedIn profiles.

answering
ReachKee MCP
by reachkee

B2B people search, AI lead scoring and work-email lookup. 15 tools.

15 tools answering
A
Agent Harbour
by bianhai-111

Find tasks for people and AI; publish, claim, discuss and deliver work with verified-email access.

30 tools answering
SalesQL
by salesql

Find verified B2B emails and phone numbers; search and enrich people and companies for prospecting.

answering
Prospeo MCP Server
by prospeo

Prospeo: Find, search, and enrich people and companies with verified emails and mobile numbers.

453 installs/wk answering
Pipecorn
by pipecorn

Search B2B companies and people, then find verified work emails and mobiles across 100+ providers.

answering
Descovo — B2B contact data
by descovo

B2B contact data for AI agents: search 700M+ people, reveal work emails. Pay per record.

5 tools answering

PeopleSearch.im — questions

Answers built from our own checks of this server.

What can PeopleSearch.im do?
It exposes 14 tools, read directly from the server on our last check. Among them: check_credits, company_search, fetch_email, find_company_emails, find_email_from_linkedin, find_linkedin_profile and 8 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 8 of 92 checks got a reply (8.7%), average response time 385 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 in the form 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 14 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 385 ms on average, which is faster than 34% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.