Data Collection

peoplesearch.im

This server provides tools to search professional databases, unlock profiles, retrieve verified work emails, and verify email deliverability.

1 endpoint12 known toolsFirst detected September 6, 2026Last detected September 6, 2026

ENDPOINT 1

https://peoplesearch.im/api/mcp

No auth detected

MCP server metadata

Name: peoplesearch.im
Version: 1.0.0

Capabilities

tools

Server instructions

PeopleSearch.im people-data tools. Search people and companies in plain English for free; then reveal profiles, fetch verified professional (work) emails, verify emails, and run reverse-email / LinkedIn / company lookups for credits. Most paid operations cost 1 credit and refund automatically when nothing is found (see each tool). Requires a PeopleSearch.im API key sent as `Authorization: Bearer sk_sift_…`; create one at https://peoplesearch.im/developers.

Known tools 12

people_search

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.

Inferred read-only

reveal_profile

Unlock ONE person from a people_search result.

Inferred read-only

find_people

The list-building tool.

Inferred read-only

fetch_email

Look up the verified professional (work) email for a person you have already unlocked with find_people (or reveal_profile).

Potential side effects

verify_email

Check whether an email address exists and is safe to send to, before it bounces.

Potential side effects

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

Potential side effects

reverse_email_lookup

Turn a professional email address into the real person behind it and their LinkedIn profile.

Potential side effects

find_linkedin_profile

Find the LinkedIn profile URL for a named person.

Inferred read-only

lookup_linkedin_profile

Turn a LinkedIn profile URL into clean structured data: name, current role and company, and location.

Inferred read-only

lookup_company

Turn a LinkedIn company URL into firmographic data: industry, size, location and website.

Inferred read-only

company_search

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.

Inferred read-only

check_credits

Return the current credit balance for the API key making the request.

Inferred read-only

CONNECT WITH APPROVAL

Client installation

Review this server and its permissions before adding it. Secret placeholders must be set locally.

Codex

~/.codex/config.toml

[mcp_servers.peoplesearch-im]
url = "https://peoplesearch.im/api/mcp"
enabled = true

Claude Code

.mcp.json

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

Claude Desktop

Settings → Connectors → Add custom connector

Name: peoplesearch-im
Remote MCP URL: https://peoplesearch.im/api/mcp

Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.

Cursor

.cursor/mcp.json

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

Visual Studio Code

.vscode/mcp.json

Add to Visual Studio Code

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

Generic MCP

Client-specific MCP configuration

{
  "name": "peoplesearch-im",
  "transport": "streamable-http",
  "url": "https://peoplesearch.im/api/mcp"
}

MCP Inspector

Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.

TRUST AND VERIFICATION EVIDENCE

Loading Trust v2 evidence…

Checking the associated registrable domain. The BuiltWith key remains server-side.

Indexed

Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.