PeopleSearch.im

im.peoplesearchPublished by peoplesearch.imOfficial publisherv1.2.0Updated Oct 27, 2026

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

Overview

AI-generated overview

Remote MCP server for searching people and companies, unlocking LinkedIn profiles, and finding or verifying professional work emails.

What you can do
  • Search a global professional database for people, with filters and a reported total match count
  • Unlock individual profiles for name, title, company, location and LinkedIn URL, or build lists of up to a set count in one charge
  • Find, verify and reverse-look-up professional work email addresses, including role-based company inboxes
  • Look up LinkedIn profiles and companies for structured data, and search a company database by domain, name or description
  • Check the remaining credit balance before larger runs
When to use it
Useful for recruiting, sales prospecting or research where an assistant needs to find people at companies, build contact lists, or confirm that a work email is deliverable before outreach.
Requirements
Remote streamable HTTP endpoint; no local install. An optional API key can be sent in the Authorization header; without it, a few searches per day work anonymously and other tools sign in with OAuth. Paid lookups draw on a credit balance.
Before you install
Most lookups spend credits, including the reverse email lookup at 13 credits, so costs add up; check the balance first. The server returns personal data such as names, locations, LinkedIn URLs and work emails, which carries privacy and data-protection obligations. An API key in the Authorization header is a secret to protect.

Installation

In SourceWeft

  1. Open PeopleSearch.im in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/im.peoplesearch%2Femail-finder/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "peoplesearch-im": {
      "type": "http",
      "url": "https://peoplesearch.im/api/mcp"
    }
  }
}

Tools

13

reveal_profile

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.

Parameterstokenrequiredinclude_email

find_people

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

Parameterscountqueryfilters

fetch_email

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.

Parametersprofile_idrequired

find_work_email

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

Parameterslast_namerequiredfirst_namerequiredcompany_or_domainrequired

verify_email

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.

Parametersemailrequired

find_company_emails

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.

Parametersdomain_or_companyrequired

reverse_email_lookup

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.

Parametersemailrequired

find_linkedin_profile

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.

Parameterslast_namerequiredfirst_namerequiredcompany_or_domain

lookup_linkedin_profile

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.

Parameterslinkedin_urlrequired

lookup_company

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.

Parameterslinkedin_company_urlrequired

check_credits

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.

Takes no parameters.

Version history

3
  1. v1.2.0LatestOct 12, 2026
  2. v1.1.0Sep 26, 2026
  3. v1.0.0Sep 16, 2026

Score

72% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listedRequired15 pts
  • DescriptionRequired15 pts
  • Logo10 pts

    Publish an icon in the registry entry.

  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.