im.peoplesearch/email-finder

Est-ce que im.peoplesearch/email-finder est sûr ?

Au dernier audit MCP Hub, le serveur MCP « im.peoplesearch/email-finder » est classé « Non encore testé ». Référencé dans l'annuaire. Seul le pentest comportemental fait foi, et il n'a pas encore été exécuté sur ce serveur. Le verdict est réévalué en continu ; consultez la fiche pour l'état à jour.

Méthode : MCP Hub analyse la description de chaque outil (couche 1) et, pour le verdict fort, exécute le serveur dans une micro-VM isolée avec leurres et réseau bloqué (couche 2). On publie des noms et des compteurs, jamais le contenu brut renvoyé par un outil.

Les 13 outils

• check_credits≈ 118 tokens

  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.

  Paramètres, retour & exemple (0)

  Exemple d'appel

  {"name": "check_credits", "arguments": {}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• company_search≈ 265 tokens

  Search a global company database and get matching companies with industry, size, location and website. Three ways to ask: a company's website ('warmly.ai') returns that one company, the most exact way to identify one; a company's name ('Warmly') returns the companies of that name; a description in plain English ('Series B fintech companies in London with 50-200 employees') returns the companies that fit it. Searching companies is FREE and spends no credits. It also works before a PeopleSearch.im account is connected: without one it returns up to 3 companies per search, up to 10 searches a day.

  Paramètres, retour & exemple (1)

  Paramètres

  • query · string · requis
    A company's website, a company's name, or the companies you want described in plain English.

  Exemple d'appel

  {"name": "company_search", "arguments": {"query": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• fetch_email≈ 230 tokens

  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.

  Paramètres, retour & exemple (1)

  Paramètres

  • profile_id · string · requis
    The `id` of a person returned by find_people (or reveal_profile).

  Exemple d'appel

  {"name": "fetch_email", "arguments": {"profile_id": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• find_company_emails≈ 208 tokens

  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.

  Paramètres, retour & exemple (1)

  Paramètres

  • domain_or_company · string · requis
    A company domain (preferred, e.g. acme.com) or company name.

  Exemple d'appel

  {"name": "find_company_emails", "arguments": {"domain_or_company": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• find_linkedin_profile≈ 217 tokens

  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.

  Paramètres, retour & exemple (3)

  Paramètres

  • last_name · string · requis
    The person's last name.
  • first_name · string · requis
    The person's first name.
  • company_or_domain · string · optionnel
    Optional but recommended: the company name or domain they work at, to disambiguate common names.

  Exemple d'appel

  {"name": "find_linkedin_profile", "arguments": {"last_name": "texte", "first_name": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• find_people≈ 1901 tokens

  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.

  Paramètres, retour & exemple (3)

  Paramètres

  • count · integer · optionnel
    How many people to unlock, 1-100 (default 25). Spends up to this many credits.
  • query · string · optionnel
    Who you are looking for, in plain English (role, seniority, industry, company, company size, location). Parsed for you. A company's website identifies it exactly, alone or in brackets after its name ('Head of Growth at Linear (linear.app)'). Optional when `filters` is given, where it is only a label.
  • filters · object · optionnel
    Exact filters, recommended for AI agents and programs: state each part of the request instead of a sentence. Values inside one list are alternatives (OR); different fields must all match (AND). Give a few variants where people word things differently (titles: ["M&A Associate", "Investment Banking Associate"]). When filters are given, `query` is only a label and is not parsed.

  Exemple d'appel

  {"name": "find_people", "arguments": {"count": 1, "query": "texte", "filters": {}}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• find_work_email≈ 303 tokens

  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.

  Paramètres, retour & exemple (3)

  Paramètres

  • last_name · string · requis
    The person's last name.
  • first_name · string · requis
    The person's first name.
  • company_or_domain · string · requis
    The company they work at: its domain (best, e.g. acme.com) or its name.

  Exemple d'appel

  {"name": "find_work_email", "arguments": {"last_name": "texte", "first_name": "texte", "company_or_domain": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• lookup_company≈ 153 tokens

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

  Paramètres, retour & exemple (1)

  Paramètres

  • linkedin_company_url · string · requis
    A LinkedIn company URL, e.g. https://linkedin.com/company/…

  Exemple d'appel

  {"name": "lookup_company", "arguments": {"linkedin_company_url": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• lookup_linkedin_profile≈ 158 tokens

  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.

  Paramètres, retour & exemple (1)

  Paramètres

  • linkedin_url · string · requis
    A LinkedIn profile URL, e.g. https://linkedin.com/in/…

  Exemple d'appel

  {"name": "lookup_linkedin_profile", "arguments": {"linkedin_url": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• people_search≈ 2103 tokens

  Search a global professional database for people and get a sample of matches plus the true total match count. Ask with `filters` (recommended: state each part exactly, for example {"job_titles": ["M&A Associate", "Investment Banking Associate"], "locations": ["Frankfurt", "Munich"], "industries": ["Investment Banking"], "schools": ["University of Mannheim"]}) or with `query`, a plain-English sentence that is parsed for you (for example 'Heads of Marketing at Series B SaaS in New York'). 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 check that the right people come back before you pay, and refine the filters if they do not. To look up one named person, give `first_name` and `last_name` with their company or company domain when known. For a kind of employer no industry names exactly, use `company_keywords` (words its own description contains, for example ["hostel"] or ["SEO"] with industries ["Marketing Services"]). If nothing matches exactly, the search broadens itself: a job title is read more broadly first (`broadenedRole` gives the title as asked and as searched), then the least essential filters are dropped and `broadenedBy` names them; `ignored` lists any filter that could not be applied. To get a person's real name, LinkedIn and verified email, pass their token to reveal_profile, or use find_people with the same filters to unlock a batch in one call. It also works before a PeopleSearch.im account is connected: without one it returns up to 3 previews per search, up to 10 searches a day.

  Paramètres, retour & exemple (3)

  Paramètres

  • limit · integer · optionnel
    How many masked previews to return (1-25, default 10). This does not limit the reported total.
  • query · string · optionnel
    Who you are looking for, in plain English (role, seniority, industry, company, company size, location). Parsed for you. A company's website identifies it exactly, alone or in brackets after its name ('Head of Growth at Linear (linear.app)'). Optional when `filters` is given, where it is only a label.
  • filters · object · optionnel
    Exact filters, recommended for AI agents and programs: state each part of the request instead of a sentence. Values inside one list are alternatives (OR); different fields must all match (AND). Give a few variants where people word things differently (titles: ["M&A Associate", "Investment Banking Associate"]). When filters are given, `query` is only a label and is not parsed.

  Exemple d'appel

  {"name": "people_search", "arguments": {"limit": 1, "query": "texte", "filters": {}}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• reveal_profile≈ 294 tokens

  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.

  Paramètres, retour & exemple (2)

  Paramètres

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

  Exemple d'appel

  {"name": "reveal_profile", "arguments": {"token": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• reverse_email_lookup≈ 180 tokens

  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.

  Paramètres, retour & exemple (1)

  Paramètres

  • email · string · requis
    The email address to identify, e.g. jordan@acme.com.

  Exemple d'appel

  {"name": "reverse_email_lookup", "arguments": {"email": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• verify_email≈ 167 tokens

  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.

  Paramètres, retour & exemple (1)

  Paramètres

  • email · string · requis
    The email address to verify, e.g. jordan@acme.com.

  Exemple d'appel

  {"name": "verify_email", "arguments": {"email": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

C'est votre serveur ?

Revendiquez-le sur l'espace créateur (preuve GitHub, domaine ou npm) pour afficher le badge « propriétaire vérifié » et lancer un pentest comportemental à la demande afin d'obtenir le badge « Vérifié ».

Créer un compte / revendiquer →

Source

https://peoplesearch.im/api/mcp