@pipeworx/leadmagic

Connect: https://pipeworx.io/mcp — every tool in the catalog, including @pipeworx/leadmagic’s. Install: one-click buttons

Connect to just the @pipeworx/leadmagic pack

https://gateway.pipeworx.io/leadmagic/mcp — only @pipeworx/leadmagic’s own tools, nothing else in the catalog.

No MCP client? Skip the connection: POST https://gateway.pipeworx.io/v1/tools/search_packs {"query":"..."} to find a tool below, GET /v1/tools/<name> for its schema, POST the same URL with arguments for the data — see For AI agents.

Tools: 1

Find a work email by name + company domain, via LeadMagic’s B2B data API (leadmagic.io). Every email returned is already SMTP-validated on LeadMagic’s side. Part of the enrich-waterfall finder rotation (fleet #2860).

Tools

  • leadmagic_find_email(first_name, last_name, domain, _apiKey) — work email, employment verification, and company fields; a confirmed no-match is free on LeadMagic’s own billing.

Auth

BYO only. Pass your LeadMagic API key as _apiKey (header X-API-Key). Get one at https://leadmagic.io. No platform key (D4).

Data sources

  • https://api.leadmagic.io/v1/people/email-finder — email finder.

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

  • Auth header + live endpoint confirmed by edge probe. No-key POST to /v1/people/email-finder returned HTTP 401 with LeadMagic’s own structured problem+json body naming X-API-Key (case-insensitive) or Authorization: Bearer <key> as the two accepted forms. This pack uses X-API-Key.
  • Response shape is from vendor docs only (https://leadmagic.io/docs/api-reference/email-finder, read 2026-10-08):
    • hit: { email, status: "valid", credits_consumed: 1, message, employment_verified, company_name, company_industry, mx_provider }
    • no match: { email: null, status: null, credits_consumed: 0, message, first_name, last_name, domain } The no-match case is a fully-populated 200 with email: null — this pack decides hit-vs-miss on email, never the envelope, matching the waterfall’s house rule (same trap findymail documents for its own API).
  • Not verified (no key held): the exact set of status values beyond "valid" on a live call (docs only show the one example), and whether a malformed domain produces a 4xx or a clean no-match.

Tools

  • leadmagic_find_email — Find a work email by first name, last name and company domain, via LeadMagic. Every email returned is already SMTP/deliverability-validated on LeadMagic’s side; a confirmed no-match is free (0 credits

Tools

  • leadmagic_find_email — Find a work email by first name, last name and company domain, via LeadMagic. Every email returned is already SMTP/deliverability-validated on LeadMagic's side; a confirmed no-match is free (0 credits

Regenerated from source · build October 9, 2026