# PeopleSearch.im (remote · peoplesearch.im)

Plain-English people search with verified work emails, email verification and LinkedIn lookup.

- Trust score: 79/100 (medium)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-20

## Components

- remote · `peoplesearch.im`: 79/100 (this document), [markdown](https://verifymcp.io/servers/im-peoplesearch-email-finder/api-mcp.md), [page](https://verifymcp.io/servers/im-peoplesearch-email-finder/api-mcp)

## Channel facts

- Endpoint: `https://peoplesearch.im/api/mcp`
- Transports: `streamable-http`
- Auth: `required`
- Version: `1.0.0`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-09-20.

- **Endpoint Security**: 80/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 80/100
  - AI-judged instruction clarity (excellent).
  - 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.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 47/100
  - Stability observed for 14 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 12 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 13 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 60/100
  - Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28.

## Install

### 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.

### Claude

```bash
claude mcp add --transport http im-peoplesearch-email-finder 'https://peoplesearch.im/api/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "im-peoplesearch-email-finder": {
      "url": "https://peoplesearch.im/api/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "im-peoplesearch-email-finder": {
      "type": "http",
      "url": "https://peoplesearch.im/api/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.im-peoplesearch-email-finder]
url = "https://peoplesearch.im/api/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "im-peoplesearch-email-finder": {
      "type": "remote",
      "url": "https://peoplesearch.im/api/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add im-peoplesearch-email-finder --url 'https://peoplesearch.im/api/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  im-peoplesearch-email-finder:
    url: "https://peoplesearch.im/api/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "im-peoplesearch-email-finder": {
      "Transport": "http",
      "Url": "https://peoplesearch.im/api/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add im-peoplesearch-email-finder -t streamable-http -u 'https://peoplesearch.im/api/mcp'
```

### Other

```json
{
  "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.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-09-19 (score 79, +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.

### 2026-09-17 (score 78, +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.

### 2026-09-14 (score 77, +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.

### 2026-09-12 (score 76, +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.

### 2026-09-10 (score 75, +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.

### 2026-09-09 (score 74, +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.

### 2026-09-07 (score 73, +1)

- [functional improvement] Stability: unverified → 0.03

### 2026-09-06 (score 72)

First indexed and scored.

## MCP tools (12)

### `people_search` (~189 tokens)

Search people

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.

Input parameters:

- `limit` (integer): How many masked previews to return (1-25, default 10). This does not limit the reported total.
- `query` (string, required): Who you are looking for, in plain English. Include role, seniority, industry, company stage/size, and location as needed.

### `reveal_profile` (~187 tokens)

Reveal a person

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.

Input parameters:

- `include_email` (boolean): Also fetch the person's verified professional email (a second credit, refunded if none is found). Default false.
- `token` (string, required): The opaque `token` of a person returned by people_search.

### `find_people` (~198 tokens)

Find & unlock a batch of 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.

Input parameters:

- `count` (integer): How many people to unlock, 1-100 (default 25). Spends up to this many credits.
- `query` (string, required): Who you want, in plain English (same grammar as people_search).

### `fetch_email` (~129 tokens)

Fetch a verified work 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.

Input parameters:

- `profile_id` (string, required): The `id` of a person returned by find_people (or reveal_profile).

### `verify_email` (~82 tokens)

Verify an email address

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.

Input parameters:

- `email` (string, required): The email address to verify, e.g. jordan@acme.com.

### `find_company_emails` (~111 tokens)

Find a company's 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.

Input parameters:

- `domain_or_company` (string, required): A company domain (preferred, e.g. acme.com) or company name.

### `reverse_email_lookup` (~86 tokens)

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.

Input parameters:

- `email` (string, required): The email address to identify, e.g. jordan@acme.com.

### `find_linkedin_profile` (~104 tokens)

Find a 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.

Input parameters:

- `company_or_domain` (string): Optional but recommended: the company name or domain they work at, to disambiguate common names.
- `first_name` (string, required): The person's first name.
- `last_name` (string, required): The person's last name.

### `lookup_linkedin_profile` (~68 tokens)

Look up a 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.

Input parameters:

- `linkedin_url` (string, required): A LinkedIn profile URL, e.g. https://linkedin.com/in/…

### `lookup_company` (~65 tokens)

Look up a company

Turn a LinkedIn company URL into firmographic data: industry, size, location and website. Spends 1 credit, refunded if the company cannot be retrieved.

Input parameters:

- `linkedin_company_url` (string, required): A LinkedIn company URL, e.g. https://linkedin.com/company/…

### `company_search` (~70 tokens)

Search companies

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.

Input parameters:

- `query` (string, required): The companies you want, in plain English.

### `check_credits` (~42 tokens)

Check credit balance

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.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/im-peoplesearch-email-finder/api-mcp#diagnostics

## Score history

- 2026-09-20: 79
- 2026-09-19: 79
- 2026-09-18: 78
- 2026-09-17: 78
- 2026-09-16: 77
- 2026-09-15: 77
- 2026-09-14: 77
- 2026-09-13: 76
- 2026-09-12: 76
- 2026-09-11: 75
- 2026-09-10: 75
- 2026-09-09: 74
- 2026-09-08: 73
- 2026-09-07: 73
- 2026-09-06: 72

## Common questions

### 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.

## Links

- Remote endpoint: https://peoplesearch.im/api/mcp
- Authorisation metadata: https://peoplesearch.im/.well-known/oauth-protected-resource/api/mcp
- Website: https://peoplesearch.im/mcp
- Changelog RSS feed: https://verifymcp.io/servers/im-peoplesearch-email-finder/api-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/im-peoplesearch-email-finder/api-mcp.json
- HTML version of this page: https://verifymcp.io/servers/im-peoplesearch-email-finder/api-mcp