Skip to content

PeopleSearch.im MCP server

im.peoplesearch/email-finderpeoplesearch.imstreamable-httpv1.2.0Scanned

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

14 tools: 11 change things and 3 only read.

Tools: 0 delete, 0 irreversible, 11 write, 3 read.
  • Reads private data · 7
  • Reads text others write · 13
  • Can send data out · 0
  • 9 findings

Tools listed without sign-in. Remote posture

With Anlyon

11 tools here change things. Govern them.

  • Anlyon lists the tools and adopts none.
  • Each tool you adopt gets approvals and receipts.
  • Your agent never holds the key.
Govern this server →

A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.

What the PeopleSearch.im MCP server can do

The PeopleSearch.im MCP server is published by peoplesearch.im, a domain the MCP Registry verified. It has 14 tools. It can create or change data (11 tools: reveal_profile, find_people, fetch_email, find_work_email and 7 more), but cannot delete data. 3 tools only read.

7 tools read private data (people_search, fetch_email, find_work_email and 4 more); 13 tools bring in text other people can write (people_search, reveal_profile, find_people and 10 more).

The fixed checks matched 9 findings (annotation-conflict). Each one comes with the text it matched.

Its remote endpoint lists its tools without sign-in, and its tools changed 2 times since Anlyon Radar first saw them.

Last scanned Nov 15, 2026, version 1.2.0.

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

14 tools

Changes things 11Claude Code: ask
  • fetch_emailLook up the verified professional (work) email for a person you have already unlocked with find_people (or reveal_profile).Reads private dataReads text others write1 finding

    Why it is in this group

    • The name "fetch_email" says "fetch": a word for reading.
    • The server marks it as not read-only (readOnlyHint: false).

    What it can reach

    • private-dataThe name "fetch_email" says "fetch" and "email": it reads mail.
    • private-dataThe description's first sentence says "email": it reads mail.
    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    • untrusted-inputThe name "fetch_email" says "fetch" and "email": it reads inbound email, which other people can write.
    • untrusted-inputThe description's first sentence says "email": it reads inbound email, which other people can write.

    Findings

    • Warn

      The server marks "fetch_email" as not read-only (readOnlyHint: false), and its words say it reads.

      Matched text

      annotations: {"readOnlyHint":false,"destructiveHint":false,"idempotentHint":true,"openWorldHint":true}; The name "fetch_email" says "fetch": a word for reading.

      What this check looks for
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Fetch a verified work email
    • readOnlyHint: false
    • idempotentHint: true
    • destructiveHint: false
    • openWorldHint: true
  • find_company_emailsGiven 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 leve…Reads private dataReads text others write1 finding

    Why it is in this group

    • The name "find_company_emails" says "find": a word for reading.
    • The server marks it as not read-only (readOnlyHint: false).

    What it can reach

    • private-dataThe name "find_company_emails" says "find" and "email": it reads mail.
    • private-dataThe description's first sentence says "email": it reads mail.
    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    • untrusted-inputThe name "find_company_emails" says "find" and "email": it reads inbound email, which other people can write.
    • untrusted-inputThe description's first sentence says "email": it reads inbound email, which other people can write.

    Findings

    • Warn

      The server marks "find_company_emails" as not read-only (readOnlyHint: false), and its words say it reads.

      Matched text

      annotations: {"readOnlyHint":false,"destructiveHint":false,"idempotentHint":false,"openWorldHint":true}; The name "find_company_emails" says "find": a word for reading.

      What this check looks for
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Find a company's emails
    • readOnlyHint: false
    • idempotentHint: false
    • destructiveHint: false
    • openWorldHint: true
  • find_email_from_linkedinGiven a LinkedIn profile URL, return that person's professional email address, verified live, with their current role and company.Reads private dataReads text others write1 finding

    Why it is in this group

    • The name "find_email_from_linkedin" says "find": a word for reading.
    • The server marks it as not read-only (readOnlyHint: false).

    What it can reach

    • private-dataThe name "find_email_from_linkedin" says "find" and "email": it reads mail.
    • private-dataThe description's first sentence says "email": it reads mail.
    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    • untrusted-inputThe name "find_email_from_linkedin" says "find" and "email": it reads inbound email, which other people can write.
    • untrusted-inputThe description's first sentence says "url": it reads web pages, which anyone can write.

    Findings

    • Warn

      The server marks "find_email_from_linkedin" as not read-only (readOnlyHint: false), and its words say it reads.

      Matched text

      annotations: {"readOnlyHint":false,"destructiveHint":false,"idempotentHint":false,"openWorldHint":true}; The name "find_email_from_linkedin" says "find": a word for reading.

      What this check looks for
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Find the email behind a LinkedIn profile
    • readOnlyHint: false
    • idempotentHint: false
    • destructiveHint: false
    • openWorldHint: true
  • find_linkedin_profileFind a named person's LinkedIn profile: its URL with their current title, company and location.Reads text others write1 finding

    Why it is in this group

    • The name "find_linkedin_profile" says "find": a word for reading.
    • The server marks it as not read-only (readOnlyHint: false).

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    • untrusted-inputThe description's first sentence says "find" and "url": it reads web pages, which anyone can write.

    Findings

    • Warn

      The server marks "find_linkedin_profile" as not read-only (readOnlyHint: false), and its words say it reads.

      Matched text

      annotations: {"readOnlyHint":false,"destructiveHint":false,"idempotentHint":false,"openWorldHint":true}; The name "find_linkedin_profile" says "find": a word for reading.

      What this check looks for
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Find a LinkedIn profile
    • readOnlyHint: false
    • idempotentHint: false
    • destructiveHint: false
    • openWorldHint: true
  • find_peopleThe list-building tool.Reads text others write1 finding

    Why it is in this group

    • The name "find_people" says "find": a word for reading.
    • The server marks it as not read-only (readOnlyHint: false).

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.

    Findings

    • Warn

      The server marks "find_people" as not read-only (readOnlyHint: false), and its words say it reads.

      Matched text

      annotations: {"readOnlyHint":false,"destructiveHint":false,"idempotentHint":true,"openWorldHint":true}; The name "find_people" says "find": a word for reading.

      What this check looks for
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Find & unlock a batch of people
    • readOnlyHint: false
    • idempotentHint: true
    • destructiveHint: false
    • openWorldHint: true
  • find_work_emailFind 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…Reads private dataReads text others write1 finding

    Why it is in this group

    • The name "find_work_email" says "find": a word for reading.
    • The server marks it as not read-only (readOnlyHint: false).

    What it can reach

    • private-dataThe name "find_work_email" says "find" and "email": it reads mail.
    • private-dataThe description's first sentence says "find" and "email": it reads mail.
    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    • untrusted-inputThe name "find_work_email" says "find" and "email": it reads inbound email, which other people can write.
    • untrusted-inputThe description's first sentence says "find" and "email": it reads inbound email, which other people can write.

    Findings

    • Warn

      The server marks "find_work_email" as not read-only (readOnlyHint: false), and its words say it reads.

      Matched text

      annotations: {"readOnlyHint":false,"destructiveHint":false,"idempotentHint":false,"openWorldHint":true}; The name "find_work_email" says "find": a word for reading.

      What this check looks for
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Find a person's work email
    • readOnlyHint: false
    • idempotentHint: false
    • destructiveHint: false
    • openWorldHint: true
  • lookup_companyTurn a LinkedIn company URL into firmographic data: industry, size, location and website.Reads text others write1 finding

    Why it is in this group

    • The name "lookup_company" says "lookup": a word for reading.
    • The server marks it as not read-only (readOnlyHint: false).

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    • untrusted-inputThe description's first sentence says "url": it reads web pages, which anyone can write.

    Findings

    • Warn

      The server marks "lookup_company" as not read-only (readOnlyHint: false), and its words say it reads.

      Matched text

      annotations: {"readOnlyHint":false,"destructiveHint":false,"idempotentHint":false,"openWorldHint":true}; The name "lookup_company" says "lookup": a word for reading.

      What this check looks for
    Description, as the server wrote it
    Turn a LinkedIn company URL into firmographic data: industry, size, location and website. Spends 1 credit, refunded if the company cannot be retrieved.

    Annotations the server declares

    • title: Look up a company
    • readOnlyHint: false
    • idempotentHint: false
    • destructiveHint: false
    • openWorldHint: true
  • lookup_linkedin_profileTurn a LinkedIn profile URL into clean structured data: name, current role and company, and location.Reads text others write1 finding

    Why it is in this group

    • The name "lookup_linkedin_profile" says "lookup": a word for reading.
    • The server marks it as not read-only (readOnlyHint: false).

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    • untrusted-inputThe description's first sentence says "url": it reads web pages, which anyone can write.

    Findings

    • Warn

      The server marks "lookup_linkedin_profile" as not read-only (readOnlyHint: false), and its words say it reads.

      Matched text

      annotations: {"readOnlyHint":false,"destructiveHint":false,"idempotentHint":false,"openWorldHint":true}; The name "lookup_linkedin_profile" says "lookup": a word for reading.

      What this check looks for
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Look up a LinkedIn profile
    • readOnlyHint: false
    • idempotentHint: false
    • destructiveHint: false
    • openWorldHint: true
  • reveal_profileUnlock ONE person from a people_search result.Reads text others writeNo findings

    Why it is in this group

    • The description's first verb is "unlock": a word for a change.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Reveal a person
    • readOnlyHint: false
    • idempotentHint: true
    • destructiveHint: false
    • openWorldHint: true
  • reverse_email_lookupTurn a professional email address into the real person behind it and their LinkedIn profile.Reads private dataReads text others write1 finding

    Why it is in this group

    • The name "reverse_email_lookup" says "lookup": a word for reading.
    • The server marks it as not read-only (readOnlyHint: false).

    What it can reach

    • private-dataThe name "reverse_email_lookup" says "lookup" and "email": it reads mail.
    • private-dataThe description's first sentence says "email": it reads mail.
    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    • untrusted-inputThe name "reverse_email_lookup" says "lookup" and "email": it reads inbound email, which other people can write.
    • untrusted-inputThe description's first sentence says "email": it reads inbound email, which other people can write.

    Findings

    • Warn

      The server marks "reverse_email_lookup" as not read-only (readOnlyHint: false), and its words say it reads.

      Matched text

      annotations: {"readOnlyHint":false,"destructiveHint":false,"idempotentHint":false,"openWorldHint":true}; The name "reverse_email_lookup" says "lookup": a word for reading.

      What this check looks for
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Reverse email lookup
    • readOnlyHint: false
    • idempotentHint: false
    • destructiveHint: false
    • openWorldHint: true
  • verify_emailCheck whether an email address exists and is safe to send to, before it bounces.Reads text others writeNo findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Verify an email address
    • readOnlyHint: false
    • idempotentHint: false
    • destructiveHint: false
    • openWorldHint: true
Only reads 3Show 3 read-only tools
  • check_creditsReturn the current credit balance for the API key making the request.No findings

    Why it is in this group

    • The description's first verb is "return": a word for reading.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Check credit balance
    • readOnlyHint: true
    • idempotentHint: true
    • destructiveHint: false
    • openWorldHint: false

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

No private-data, untrusted-input, outbound path in this server alone: no tool is tagged outbound.

Reads private data7
Reads files, mail, messages, databases, secrets, calendars or repositories.
Can send data out0
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

Tools listed without sign-in

Looked at Nov 20, 2026, 18:55 UTC, unchanged since Nov 6, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
yes
HTTP status of an anonymous initialize
200
tools/list served without credentials
yes
Tools that change things, listed without credentials
11
Protocol version
2025-06-18
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
https://peoplesearch.im/.well-known/oauth-protected-resource/api/mcp
Authorization servers
https://peoplesearch.im
Legacy HTTP+SSE transport
no
Dynamic client registration
yes
Client ID metadata documents
yes
  • WarnThe whole server

    The endpoint served tools/list without credentials, and the list has 11 tools that change things (11 write). Whether a call also works without credentials was not tested: tools are never called.

    Matched text

    https://peoplesearch.im/api/mcp: tools/list returned 14 tools to an anonymous client, including reveal_profile (write), find_people (write), fetch_email (write), find_work_email (write), verify_email (write) and 6 more

    What this check looks for

Posture changes

  1. Nov 6, 2026
    • Tools that change things, listed without credentials: 10 to 11

Findings

Matches of fixed checks, with the text they matched.

9 warn
  • The server marks "find_people" as not read-only (readOnlyHint: false), and its words say it reads.

    Matched text

    annotations: {"readOnlyHint":false,"destructiveHint":false,"idempotentHint":true,"openWorldHint":true}; The name "find_people" says "find": a word for reading.

    What this check looks for
  • The server marks "fetch_email" as not read-only (readOnlyHint: false), and its words say it reads.

    Matched text

    annotations: {"readOnlyHint":false,"destructiveHint":false,"idempotentHint":true,"openWorldHint":true}; The name "fetch_email" says "fetch": a word for reading.

    What this check looks for
  • The server marks "find_work_email" as not read-only (readOnlyHint: false), and its words say it reads.

    Matched text

    annotations: {"readOnlyHint":false,"destructiveHint":false,"idempotentHint":false,"openWorldHint":true}; The name "find_work_email" says "find": a word for reading.

    What this check looks for
  • The server marks "find_company_emails" as not read-only (readOnlyHint: false), and its words say it reads.

    Matched text

    annotations: {"readOnlyHint":false,"destructiveHint":false,"idempotentHint":false,"openWorldHint":true}; The name "find_company_emails" says "find": a word for reading.

    What this check looks for
  • The server marks "reverse_email_lookup" as not read-only (readOnlyHint: false), and its words say it reads.

    Matched text

    annotations: {"readOnlyHint":false,"destructiveHint":false,"idempotentHint":false,"openWorldHint":true}; The name "reverse_email_lookup" says "lookup": a word for reading.

    What this check looks for
  • The server marks "find_linkedin_profile" as not read-only (readOnlyHint: false), and its words say it reads.

    Matched text

    annotations: {"readOnlyHint":false,"destructiveHint":false,"idempotentHint":false,"openWorldHint":true}; The name "find_linkedin_profile" says "find": a word for reading.

    What this check looks for
Show 3 more findings
  • The server marks "lookup_linkedin_profile" as not read-only (readOnlyHint: false), and its words say it reads.

    Matched text

    annotations: {"readOnlyHint":false,"destructiveHint":false,"idempotentHint":false,"openWorldHint":true}; The name "lookup_linkedin_profile" says "lookup": a word for reading.

    What this check looks for
  • The server marks "find_email_from_linkedin" as not read-only (readOnlyHint: false), and its words say it reads.

    Matched text

    annotations: {"readOnlyHint":false,"destructiveHint":false,"idempotentHint":false,"openWorldHint":true}; The name "find_email_from_linkedin" says "find": a word for reading.

    What this check looks for
  • The server marks "lookup_company" as not read-only (readOnlyHint: false), and its words say it reads.

    Matched text

    annotations: {"readOnlyHint":false,"destructiveHint":false,"idempotentHint":false,"openWorldHint":true}; The name "lookup_company" says "lookup": a word for reading.

    What this check looks for

History

Changes to its tool definitions and to its remote endpoint, newest first.

  1. Tools2 changed.~2 changedView diff
  2. PostureRemote posture changed. Tools that change things, listed without credentials: 10 -> 11.View diff
    • Tools that change things, listed without credentials: 10 to 11
  3. Tools1 added, 5 changed.+1 added~5 changedView diff

Install

Pinned to version 1.2.0. Values in angle brackets are yours to fill in.

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

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__email-finder__people_search",
      "mcp__email-finder__company_search",
      "mcp__email-finder__check_credits"
    ],
    "ask": [
      "mcp__email-finder__reveal_profile",
      "mcp__email-finder__find_people",
      "mcp__email-finder__fetch_email",
      "mcp__email-finder__find_work_email",
      "mcp__email-finder__verify_email",
      "mcp__email-finder__find_company_emails",
      "mcp__email-finder__reverse_email_lookup",
      "mcp__email-finder__find_linkedin_profile",
      "mcp__email-finder__lookup_linkedin_profile",
      "mcp__email-finder__find_email_from_linkedin",
      "mcp__email-finder__lookup_company"
    ],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as email-finder. Review it before you use it.

Capability tags behind 13 rules
  • mcp__email-finder__people_search private-data, untrusted-input
  • mcp__email-finder__reveal_profile untrusted-input
  • mcp__email-finder__find_people untrusted-input
  • mcp__email-finder__fetch_email private-data, untrusted-input
  • mcp__email-finder__find_work_email private-data, untrusted-input
  • mcp__email-finder__verify_email untrusted-input
  • mcp__email-finder__find_company_emails private-data, untrusted-input
  • mcp__email-finder__reverse_email_lookup private-data, untrusted-input
  • mcp__email-finder__find_linkedin_profile untrusted-input
  • mcp__email-finder__lookup_linkedin_profile untrusted-input
  • mcp__email-finder__find_email_from_linkedin private-data, untrusted-input
  • mcp__email-finder__lookup_company untrusted-input
  • mcp__email-finder__company_search private-data, untrusted-input

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://radar.anlyon.com/api/v1/servers/im.peoplesearch/email-finder/verify?hash=29f835b9864df33aeb237d1df109092cc6b2bb1fad1f5ddaac0d7e28ce2ea58d" | jq -e '.changed == false'

Pinned hash 29f835b9864d, from Nov 15, 2026, 12:18 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/im.peoplesearch/email-finder/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for im.peoplesearch/email-finder
[![Anlyon Radar](https://radar.anlyon.com/badge/im.peoplesearch/email-finder.svg)](https://radar.anlyon.com/servers/im.peoplesearch/email-finder)

Source: MCP Registry. Synced Oct 21, 2026, 18:13 UTC.

PeopleSearch.im MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the PeopleSearch.im MCP server safe?

No scan can promise that. What its definitions show: 14 tools, 11 of which can change, send or delete something, and 9 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.

Can the PeopleSearch.im MCP server delete data?

No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.

Can the PeopleSearch.im MCP server do things that cannot be undone?

No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.

What tools does the PeopleSearch.im MCP server have?

14 tools: 11 write, 3 read. reveal_profile, find_people, fetch_email, find_work_email, verify_email, find_company_emails, reverse_email_lookup, find_linkedin_profile and 6 more.

Does the PeopleSearch.im MCP server need sign-in or OAuth?

Its remote endpoint listed its tools to an anonymous client, without sign-in.

Does the PeopleSearch.im MCP server send data to outside services?

None of its tools sends, posts or publishes, or takes a recipient, channel or URL.

Has the PeopleSearch.im MCP server changed its tools?

Yes, 2 times since Anlyon Radar started tracking it, most recently on Nov 15, 2026. Every change is on this page and in its Atom feed.