PeopleSearch.im
REMOTE · PEOPLESEARCH.IM · SCANNED SEP 20
Plain-English people search with verified work emails, email verification and LinkedIn lookup.
Available components
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 Security80
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- 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
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability80
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 1432 tokens (~119/item across 12 items; 12 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 Management47
- Stability observed for 14 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
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 12 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 13 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
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'
{
"mcpServers": {
"im-peoplesearch-email-finder": {
"url": "https://peoplesearch.im/api/mcp"
}
}
} {
"servers": {
"im-peoplesearch-email-finder": {
"type": "http",
"url": "https://peoplesearch.im/api/mcp"
}
}
} [mcp_servers.im-peoplesearch-email-finder] url = "https://peoplesearch.im/api/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"im-peoplesearch-email-finder": {
"type": "remote",
"url": "https://peoplesearch.im/api/mcp",
"enabled": true
}
}
} openclaw mcp add im-peoplesearch-email-finder --url 'https://peoplesearch.im/api/mcp' --transport streamable-http
mcp_servers:
im-peoplesearch-email-finder:
url: "https://peoplesearch.im/api/mcp" {
"McpServers": {
"im-peoplesearch-email-finder": {
"Transport": "http",
"Url": "https://peoplesearch.im/api/mcp"
}
}
} assistant mcp add im-peoplesearch-email-finder -t streamable-http -u 'https://peoplesearch.im/api/mcp'
{
"mcpServers": {
"im-peoplesearch-email-finder": {
"type": "http",
"url": "https://peoplesearch.im/api/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
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.
- 19 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 40 to 43. That category is still filling its 30-day observation window: 12 days of observed history at the previous scan, 13 at this one. The score rises as the window fills, whether or not the server changes.
- 17 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes.
- 14 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.
- 12 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.
- 10 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.
- 9 Sept 26 +1
No change was recorded against any check on this day. Schema Quality & AI Usability went from 77 to 80. Other categories moved too: Stability & Change Management rose 3.
- 7 Sept 26 +1
- Stability: unverified → 0.03 ▲ functional
- 6 Sept 26 72
First indexed and scored.
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 20 Sept 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 Aug 2026 | 16 Nov 2026 | RSA 2048 | SHA256-RSA | 6ab438f3ceee7b5d6f033aa20c02ed9075f |
| 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 No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| 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=() |
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 ~70
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.
| Name | Type | Req | Description |
|---|---|---|---|
| query | string | yes | The companies you want, 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_linkedin_profile Find a LinkedIn profile ~104
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.
| Name | Type | Req | Description |
|---|---|---|---|
| company_or_domain | string | – | Optional but recommended: the company name or domain they work at, to disambiguate common names. |
| 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.
find_people Find & unlock a batch of people ~198
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.
| Name | Type | Req | Description |
|---|---|---|---|
| count | integer | – | How many people to unlock, 1-100 (default 25). Spends up to this many credits. |
| query | string | yes | Who you want, in plain English (same grammar as people_search). |
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 ~189
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.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | How many masked previews to return (1-25, default 10). This does not limit the reported total. |
| query | string | yes | Who you are looking for, in plain English. Include role, seniority, industry, company stage/size, and location as needed. |
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 ~82
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.
| Name | Type | Req | Description |
|---|---|---|---|
| string | yes | The email address to verify, e.g. jordan@acme.com. |
No output schema declared.
No examples provided.
What is the PeopleSearch.im MCP server?
PeopleSearch.im is an MCP server listed in the public MCP registry as im.peoplesearch/email-finder. Plain-English people search with verified work emails, email verification and LinkedIn lookup. This page covers its hosted endpoint (https://peoplesearch.im/api/mcp).
Is the PeopleSearch.im MCP server safe to use?
PeopleSearch.im scores 79 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 12 tools: people_search, reveal_profile, find_people, fetch_email, verify_email, and 7 more. Their descriptions and schemas cost roughly 1,331 tokens of context every time the server is loaded.
Does the PeopleSearch.im MCP server require authentication?
No. We connected to PeopleSearch.im without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
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 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.