Prospeo MCP server

@pipeworx/prospeo

Find a person's verified work email by name + company domain, via Prospeo's person-enrichment API (prospeo.io). Part of the enrich-waterfall finder rotation (fleet #2860).

Part of Pipeworx — an MCP gateway connecting AI agents to 1745+ live data sources. This is an independent, unofficial integration — not affiliated with, endorsed by, or published by the upstream provider.

Tools

— returns the verified email only when Prospeo actually reveals it; a masked/unrevealed guess is reported as not found.

• prospeofindemail(firstname, lastname, domain, companyname?, apiKey)

Auth

BYO only. Pass your Prospeo API key as _apiKey. Get one at https://app.prospeo.io/api. No platform key — PII vendors are never platform-keyed (Bruce default D4).

Data sources

finding.

• https://api.prospeo.io/enrich-person — person enrichment, used for email

Verification notes (fleet #2860, 2026-10-08, no vendor key held)

{"reqstatus":false,"errorcode":"DEPRECATED","error_toast":"...migrate by using our new APIs: https://prospeo.io/api-docs"}. Several third-party write-ups (Apify, Pipedream, a glama.ai MCP server) still document this path — do not copy them. The live replacement is POST /enrich-person, used here.

• The old /email-finder endpoint is DEAD. Edge-probed live: HTTP 400

https://prospeo.io/api-docs/authentication. Edge-probed with no key: HTTP 400 {"error":true,"errorcode":"INVALIDAPI_KEY"} on the real /enrich-person endpoint — confirms the header name and that the endpoint is live and auth-gated. This pack's refusal message says "Prospeo requires an API key... get one at app.prospeo.io/api."

• Auth header confirmed live. X-KEY: per

read 2026-10-08) — we hold no Prospeo key, so no live successful call was made. The documented example:

• Response shape is from vendor docs only (https://prospeo.io/api-docs/enrich-person,

{ "error": false, "free_enrichment": false,
    "person": { "person_id": "...", "first_name": "Eoghan", "last_name": "Mccabe",
      "email": { "status": "VERIFIED", "revealed": true, "email": "eoghan.*****@intercom.com" } },
    "company": { "company_id": "...", "name": "Intercom" } }

Note the doc's own example masks the address (eoghan.**@intercom.com) even with revealed: true — this pack's parser only accepts an email string that does NOT contain , so a masked/teaser address from a live call will correctly fall through to found: false rather than being handed back as a usable contact. This is the one thing a live key would need to confirm: whether a fully-paid reveal always returns the full address un-masked. Flagged as not verified below.

address unmasked; exact behaviour of onlyverifiedemail: true when Prospeo has only a guessed (unverified) address.

• Not verified (no key held): whether a successful paid call returns the

Quick Start

Add to your MCP client (Claude Desktop, Cursor, Windsurf, etc.):

{
  "mcpServers": {
    "prospeo": {
      "url": "https://gateway.pipeworx.io/prospeo/mcp"
    }
  }
}

What this endpoint actually serves

tools/list at https://gateway.pipeworx.io/prospeo/mcp returns the tools in the table above plus the shared Pipeworx meta-tools — askpipeworx, discovertools, search_within, remember/recall and the rest of the gateway-wide set. So the tool count you see is larger than this table: a single-pack endpoint currently lists roughly 30 shared tools alongside the pack's own. The connection's initialize response states its exact scope, and is the authoritative answer for a given day.

Shortened. The full README is on GitHub.