PeopleSearch.im
REMOTE · PEOPLESEARCH.IM
People search, LinkedIn lookup and verified work emails for AI agents. First search needs no login.
Available components
Last scanned (9 hours ago)
Scores higher than 99% of remote servers
Reachable. Last reached 5 Nov 2026.
Category CRM and Sales
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security97
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation is enforced on tool calls, advertised via RFC 9728 protected-resource metadata. Discovery is public, which costs nothing: no tool can be invoked without a token. View diagnostics → Pass
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
- The authorisation server supports Client ID Metadata Documents, the current MCP client-registration mechanism. View diagnostics → Pass
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability70
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 2648 tokens (~189/item across 14 items; 14 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 14 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 15 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 4 Nov 26 −1
- Tool “find_people” rewrote its description, which is the text the model reads security
- “find_people” added an optional parameter “include_email” cosmetic
- 1 Nov 26 0
- Tool “company_search” rewrote its description, which is the text the model reads security
- Tool “people_search” rewrote its description, which is the text the model reads security
- 31 Oct 26 +1
- New tool “find_email_from_linkedin” functional
- 29 Oct 26 −1
- Tool “find_linkedin_profile” rewrote its description, which is the text the model reads security
- “find_linkedin_profile” added an optional parameter “job_title” cosmetic
- “find_linkedin_profile” reworded the description of “company_or_domain” cosmetic
- 28 Oct 26 0
- Tool “verify_email” rewrote its description, which is the text the model reads security
- 13 Oct 26 0
- Tool “company_search” rewrote its description, which is the text the model reads security
- “company_search” reworded the description of “query” cosmetic
- “find_people” reworded the description of “query” cosmetic
- “people_search” reworded the description of “query” cosmetic
- 11 Oct 26 0
- The server rewrote its instructions, which are the text every model session reads security
- Tool “company_search” rewrote its description, which is the text the model reads security
- Tool “people_search” rewrote its description, which is the text the model reads security
- 10 Oct 26 0
- Tool “people_search” rewrote its description, which is the text the model reads security
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 5 Nov 2026 · Probed https://peoplesearch.im/api/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=peoplesearch.im | CN=YR2,O=Let's Encrypt,C=US | 18 Oct 2026 | 16 Jan 2027 | RSA 2048 | SHA256-RSA | 54262069ecf44bc37bb5cb4e0580ad5c975 |
| SANs: peoplesearch.im | ||||||
| CN=YR2,O=Let's Encrypt,C=US (CA) | CN=Root YR,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | RSA 2048 | SHA256-RSA | 4ebd24947e24d394802d84a52fd5b319 |
| CN=Root YR,O=ISRG,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | RSA 4096 | SHA256-RSA | f24b6d17f9d9ad7cb1c9fea78782699f |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of peoplesearch.im. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| im. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Enforced and verified
The endpoint asked for a token and published valid RFC 9728 metadata describing how to get one.
| Result | Enforced and verified |
|---|---|
| Enforced | On tool calls |
| HTTP status | 200 |
WWW-Authenticate challenge Bearer resource_metadata="https://peoplesearch.im/.well-known/oauth-protected-resource/api/mcp", scope="peoplesearch"
Bearer resource_metadata="https://peoplesearch.im/.well-known/oauth-protected-resource/api/mcp", scope="peoplesearch" | Header | Value |
|---|---|
| strict-transport-security | max-age=31536000; includeSubDomains |
| content-security-policy | default-src 'self'; script-src 'self' 'unsafe-inline' 'unsafe-eval' https://js.stripe.com https://platform.twitter.com; style-src 'self' 'unsafe-inline' https://fonts.googleapis.com; img-src 'self' data: blob: https:; media-src 'self' https: blob:; font-src 'self' https://fonts.gstatic.com; connect-src 'self' https://*.supabase.co wss://*.supabase.co https://api.stripe.com; worker-src 'self' blob:; frame-src 'self' https://js.stripe.com https://hooks.stripe.com https://www.youtube-nocookie.com https://www.youtube.com https://player.vimeo.com https://www.loom.com https://www.dailymotion.com https://platform.twitter.com; frame-ancestors 'self' http://localhost:* https://o-mega.ai https://*.o-mega.ai https://founden.ai https://*.founden.ai https://*.founden.co https://*.e2b.app https://*.vercel.app; object-src 'none'; base-uri 'self' |
| x-content-type-options | nosniff |
| referrer-policy | strict-origin-when-cross-origin |
| permissions-policy | camera=(), microphone=(), geolocation=(), browsing-topics=() |
Protected resource metadata
| Document | https://peoplesearch.im/.well-known/oauth-protected-resource/api/mcp |
|---|---|
| Retrieved | Yes |
| Resource | https://peoplesearch.im/api/mcp |
| Authorisation server | https://peoplesearch.im |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://peoplesearch.im/api/mcp | Verified | 200 | |
| http (plaintext) | http://peoplesearch.im/api/mcp | HTTPS enforced | 308 | https://peoplesearch.im/api/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
check_credits Check credit balance ~42
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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
company_search Search companies ~154
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.
| Name | Type | Req | Description |
|---|---|---|---|
| query | string | yes | A company's website, a company's name, or the companies you want described in plain English. |
No output schema declared.
No examples provided.
fetch_email Fetch a verified work email ~129
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.
| Name | Type | Req | Description |
|---|---|---|---|
| profile_id | string | yes | The `id` of a person returned by find_people (or reveal_profile). |
No output schema declared.
No examples provided.
find_company_emails Find a company's emails ~111
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.
| Name | Type | Req | Description |
|---|---|---|---|
| domain_or_company | string | yes | A company domain (preferred, e.g. acme.com) or company name. |
No output schema declared.
No examples provided.
find_email_from_linkedin Find the email behind a LinkedIn profile ~100
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.
| Name | Type | Req | Description |
|---|---|---|---|
| linkedin_url | string | yes | A LinkedIn profile URL, e.g. https://www.linkedin.com/in/… |
No output schema declared.
No examples provided.
find_linkedin_profile Find a LinkedIn profile ~203
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.
| Name | Type | Req | Description |
|---|---|---|---|
| company_or_domain | string | – | The company they work at, as its name or website (acme.com). Needed for a name several people share, together with or instead of job_title. |
| first_name | string | yes | The person's first name. |
| job_title | string | – | Their job title ("Head of Sales"). Tells apart people who share a name, together with or instead of company_or_domain. |
| last_name | string | yes | The person's last name. |
No output schema declared.
No examples provided.
find_people Find & unlock a batch of people ~452
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.
| Name | Type | Req | Description |
|---|---|---|---|
| count | integer | – | How many people to unlock, 1-100 (default 25). Spends up to this many credits. |
| filters | object | – | Exact filters, recommended for AI agents and programs: state each part of the request instead of a sentence. Values inside one list are alternatives (OR); different fields must all match (AND). Give… |
| include_email | boolean | – | Also look up each unlocked person's verified professional email (1 more credit each, refunded if none is found). Default false. |
| query | string | – | Who you are looking for, in plain English (role, seniority, industry, company, company size, location). Parsed for you. A company's website identifies it exactly, alone or in brackets after its name… |
No output schema declared.
No examples provided.
find_work_email Find a person's work email ~183
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.
| Name | Type | Req | Description |
|---|---|---|---|
| company_or_domain | string | yes | The company they work at: its domain (best, e.g. acme.com) or its name. |
| first_name | string | yes | The person's first name. |
| last_name | string | yes | The person's last name. |
No output schema declared.
No examples provided.
lookup_company Look up a company ~65
Turn a LinkedIn company URL into firmographic data: industry, size, location and website. Spends 1 credit, refunded if the company cannot be retrieved.
| Name | Type | Req | Description |
|---|---|---|---|
| linkedin_company_url | string | yes | A LinkedIn company URL, e.g. https://linkedin.com/company/… |
No output schema declared.
No examples provided.
lookup_linkedin_profile Look up a LinkedIn profile ~68
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.
| Name | Type | Req | Description |
|---|---|---|---|
| linkedin_url | string | yes | A LinkedIn profile URL, e.g. https://linkedin.com/in/… |
No output schema declared.
No examples provided.
people_search Search people ~550
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.
| Name | Type | Req | Description |
|---|---|---|---|
| filters | object | – | Exact filters, recommended for AI agents and programs: state each part of the request instead of a sentence. Values inside one list are alternatives (OR); different fields must all match (AND). Give… |
| limit | integer | – | How many masked previews to return (1-25, default 10). This does not limit the reported total. |
| query | string | – | Who you are looking for, in plain English (role, seniority, industry, company, company size, location). Parsed for you. A company's website identifies it exactly, alone or in brackets after its name… |
No output schema declared.
No examples provided.
reveal_profile Reveal a person ~187
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.
| Name | Type | Req | Description |
|---|---|---|---|
| include_email | boolean | – | Also fetch the person's verified professional email (a second credit, refunded if none is found). Default false. |
| token | string | yes | The opaque `token` of a person returned by people_search. |
No output schema declared.
No examples provided.
reverse_email_lookup Reverse email lookup ~86
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.
| Name | Type | Req | Description |
|---|---|---|---|
| string | yes | The email address to identify, e.g. jordan@acme.com. |
No output schema declared.
No examples provided.
verify_email Verify an email address ~137
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.
| Name | Type | Req | Description |
|---|---|---|---|
| string | yes | The email address to verify, e.g. jordan@acme.com. |
No output schema declared.
No examples provided.
How do I install the PeopleSearch.im MCP server?
PeopleSearch.im is a hosted endpoint at https://peoplesearch.im/api/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · peoplesearch.im
claude mcp add --transport http im-peoplesearch-email-finder 'https://peoplesearch.im/api/mcp'
What is the PeopleSearch.im MCP server?
PeopleSearch.im is an MCP server listed in the public MCP registry as im.peoplesearch/email-finder. People search, LinkedIn lookup and verified work emails for AI agents. First search needs no login. This page covers its hosted endpoint (https://peoplesearch.im/api/mcp).
Is the PeopleSearch.im MCP server safe to use?
PeopleSearch.im scores 93 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the PeopleSearch.im MCP server expose?
PeopleSearch.im exposes 14 tools: people_search, reveal_profile, find_people, fetch_email, find_work_email, and 9 more. Their descriptions and schemas cost roughly 2,467 tokens of context every time the server is loaded.
Does the PeopleSearch.im MCP server require authentication?
Yes. PeopleSearch.im asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.
Is the PeopleSearch.im MCP server still maintained?
PeopleSearch.im is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.