Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Apollo.io B2B Person Enrichment & Verified Email Finder (x402)

REMOTE · ENRICHMATCH.DEV

Apollo.io B2B Person Enrichment & Verified Work Email Finder via x402 on Base ($0.03, free on miss).

Available components

62 Trust /100

Last scanned (4 hours ago)

Scores higher than 44% of remote servers

Reachable. Last reached 5 Nov 2026.

Category CRM and Sales

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →

Endpoint Security63
Transport & Reachability100
Schema Quality & AI Usability54
  • AI-judged instruction clarity (good).Pass
  • Context-footprint check failed: tool/resource definitions use about 1686 tokens (~240/item across 7 items; 7 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management17
  • Stability observed for 5 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage96
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 87% of tool parameters carry a description.Partial
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 7 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 8 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities20
  • Spec-recency check failed: implements MCP spec 2024-11-05; the latest is 2026-07-28. See how to fix → Fail
Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 5 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.

  • 4 Nov 26 0
    • DNSSEC: unverified → fail ▼ security
    • HSTS header: unverified → pass ▲ security
    • TLS certificate: unverified → pass ▲ security
    • Injection markers: unverified → pass ▲ security
    • Transport: fail → pass ▲ security
    • Authorization: Authorisation not fully verified: no authorisation is required to call this server, and 7 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. security
    • The server rewrote its instructions, which are the text every model session reads security
    • Tool coverage: 100% → 87% ▼ functional
    • MCP protocol: unverified → fail ▼ functional
    • Endpoint reachability: unreachable → reachable ▲ functional
    • Schema quality: 289 → 240 ▲ functional
    • Stability: unverified → 0.13 ▲ functional
    • Tool coverage: unverified → 100 ▲ functional
    • Server version: 0.3.0 → 0.4.0 functional
    • New tool “search_people” functional
    • New tool “search_organizations” functional
    • New tool “enrich_organization” functional
    • New tool “bulk_enrich_people” functional
    • New tool “bulk_enrich_organizations” functional
    • “get_enrichment_quote” added an optional parameter “tool” cosmetic
  • 3 Nov 26 0
    • Endpoint reachability: reachable → unreachable ▼ security
    • Tool safety: pass → unverified ▼ security
    • DNSSEC: fail → unverified ▼ security
    • Stability: 0.07 → unverified ▼ security
    • TLS certificate: pass → unverified ▼ security
    • HSTS header: pass → unverified ▼ security
    • Transport: pass → fail ▼ security
    • Authorization: Authorisation not yet verified: we couldn't confirm whether this endpoint requires it. security
    • Capabilities: fail → unverified ▼ functional
    • Tool coverage: 100 → unverified ▼ functional
    • First check of Schema quality: unverified functional
  • 2 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.

  • 1 Nov 26 0
    • Stability: unverified → 0.03 ▲ functional
  • 31 Oct 26 60

    First indexed and scored.

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 5 Nov 2026 · Probed https://enrichmatch.dev/api/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=enrichmatch.dev CN=YR2,O=Let's Encrypt,C=US 30 Oct 2026 28 Jan 2027 RSA 2048 SHA256-RSA 5013fe399b381446279f7e9e6da006db3cf
SANs: enrichmatch.dev
CN=YR2,O=Let's Encrypt,C=US (CA) CN=Root YR,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 RSA 2048 SHA256-RSA 4ebd24947e24d394802d84a52fd5b319
CN=Root YR,O=ISRG,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 RSA 4096 SHA256-RSA f24b6d17f9d9ad7cb1c9fea78782699f

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of enrichmatch.dev. — Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
dev. present 60074 8 Verified
enrichmatch.dev. absent Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200
Header Value
strict-transport-security max-age=63072000

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://enrichmatch.dev/api/mcp Verified 200
http (plaintext) http://enrichmatch.dev/api/mcp HTTPS enforced 308 https://enrichmatch.dev/api/mcp
MCP tools · 7 exposed · ~1,652 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
bulk_enrich_organizations ~156

PAID ($0.015 USDC / record via x402 on Base — Free-on-Miss: Priced per domain submitted ($0.015 each); settled only if at least one organization is found; $0.00 if none.): Batch company enrichment for high-throughput agents (1 to 10 domains per call). Free-on-Miss: settled only if at least one organization is found; $0.00 if zero organizations resolved.

NameTypeReqDescription
_x402_paymentstring–Optional x402 signed payment payload (if not passed via HTTP X-PAYMENT header)
domainsarrayyesArray of 1 to 10 company domains (e.g. ['apollo.io', 'stripe.com']).

No output schema declared.

No examples provided.

bulk_enrich_people ~203

PAID ($0.025 USDC / record via x402 on Base — Free-on-Miss: Priced per record submitted ($0.025 each); charged for all submitted records if ≥ 1 email is found; $0.00 if none. Submit has_email: true IDs from search_people's unlock hint.): Batch person enrichment for high-throughput agents (1 to 10 profiles per call). Free-on-Miss: settled only if at least one record returns a deliverable email; $0.00 if zero deliverable emails found. Charged for all submitted records if ≥ 1 email is found. Submit has_email: true IDs from search_people's unlock hint.

NameTypeReqDescription
_x402_paymentstring–Optional x402 signed payment payload (if not passed via HTTP X-PAYMENT header)
detailsarrayyesArray of 1 to 10 person identifier objects.
reveal_personal_emailsboolean––

No output schema declared.

No examples provided.

enrich_organization ~162

PAID ($0.02 USDC / call via x402 on Base — Free-on-Miss: Settled ($0.02) only if organization is resolved; $0.00 if not found.): Enriches full organization profile by company domain. Returns founded year, employee count, industry, funding history, annual revenue, tech stack, departmental headcount, and HQ phone line. Free-on-Miss: $0.00 charged if domain not found.

NameTypeReqDescription
_x402_paymentstring–Optional x402 signed payment payload (if not passed via HTTP X-PAYMENT header)
domainstring–Company primary domain (e.g. 'instacart.com').
organization_namestring–Company brand name (fallback).

No output schema declared.

No examples provided.

enrich_person ~512

PAID ($0.03 USDC via x402 on Base — Free-on-Miss: $0.00 charged if no deliverable email is found): Verified B2B Person Enrichment, Work Email Finder & LinkedIn-to-Email Resolver powered by Apollo.io. Accepts partial identifiers—(1) first_name + last_name + company domain or organization_name, (2) LinkedIn profile URL (linkedin_url), or (3) email (reverse email lookup)—and returns a deterministic JSON profile with deliverable work email, verification status, job title, seniority (founder, C-suite, VP, director), company firmographics (headcount, industry, founded year), and full employment history. Zero signup or API key required.

NameTypeReqDescription
_x402_paymentstring–Optional x402 signed payment payload (if not passed via HTTP X-PAYMENT header)
companystring–Alias for organization_name or domain (e.g., 'Meta', 'Stripe', 'instacart.com').
domainstring–Company website domain or URL (e.g., 'apollo.io', 'stripe.com'). Also accepts a company name (e.g., 'Meta', 'Google') and automatically resolves the canonical domain.
emailstring–Known work or personal email address for reverse-email enrichment into full LinkedIn, title, firmographics, and career history.
first_namestring–Target person's first name (e.g., 'Tim'). Optional if 'name', 'linkedin_url', 'email', or 'id' is provided.
idstring–Optional Apollo.io person ID for direct profile hydration.
last_namestring–Target person's last name (e.g., 'Zheng'). Optional if 'name', 'linkedin_url', 'email', or 'id' is provided.
linkedin_urlstring–Public LinkedIn profile URL (e.g., 'https://www.linkedin.com/in/tim-zheng') to resolve directly into a verified work email and company profile.
namestring–Target person's full name (e.g., 'Tim Zheng'). Automatically split into first_name and last_name if needed.
organization_namestring–Company or organization name (e.g., 'Apollo.io', 'Meta', 'Google', 'Stripe') if exact domain is unknown.
reveal_personal_emailsboolean–Whether to include verified personal emails if a corporate work email is unavailable (default: false).

No output schema declared.

No examples provided.

get_enrichment_quote ~86

FREE pre-flight discovery tool: Inspect live x402 pricing ($0.03 USDC on Base, Free-on-Miss), deterministic JSON input/output schema, SLA latency telemetry, and recent verifiable Base settlement txHashes for Apollo.io B2B Person Enrichment & Work Email Lookup.

NameTypeReqDescription
toolstring–Optional tool name to inspect pricing and schema for a specific product.

No output schema declared.

No examples provided.

search_organizations ~200

PAID ($0.02 USDC / page via x402 on Base — Free-on-Miss: Settled ($0.02) only if ≥ 1 company returned; $0.00 if zero results.): Discover target accounts by name, keywords, domain list, locations, and headcount. Returns firmographic summaries and primary domains with next_step links to company firmographics or people search.

NameTypeReqDescription
_x402_paymentstring–Optional x402 signed payment payload (if not passed via HTTP X-PAYMENT header)
domainsarray–Specific company domains.
employee_rangesarray–Headcount ranges (e.g. ['51,200']).
keywordsstring–Keywords or tags.
organization_locationsarray–HQ locations.
organization_namestring–Company name search (e.g. 'Instacart').
pageinteger––
per_pageinteger––

No output schema declared.

No examples provided.

search_people ~333

PAID ($0.01 USDC / page via x402 on Base — Free-on-Miss: Priced at $0.01 USDC per page; settled on-chain only if at least one result has has_email: true ($0.00 charged if zero reachable leads found).): Search professionals across 275M+ profiles. Returns partial identities with masked last names and no emails; use next_step (enrich_person) or unlock (bulk_enrich_people) with the returned Apollo IDs to resolve verified deliverable work emails. Free-on-Miss: settled only if at least one result has reachable email (has_email: true); $0.00 charged if zero reachable leads found.

NameTypeReqDescription
_x402_paymentstring–Optional x402 signed payment payload (if not passed via HTTP X-PAYMENT header)
employee_rangesarray–Headcount ranges (e.g. ['1,10', '51,200', '1001,5000']).
keywordsstring–Keyword search across bio and experience.
organization_domainsarray–Company primary domains (e.g. ['apollo.io', 'stripe.com']).
organization_idsarray–Apollo organization IDs from search_organizations.
pageinteger––
per_pageinteger––
person_locationsarray–Geographic locations (e.g. ['San Francisco', 'United States']).
person_senioritiesarray–Seniority levels.
person_titlesarray–Job titles to filter by (e.g. ['CEO', 'VP Sales']).

No output schema declared.

No examples provided.

Install

How do I install the Apollo.io B2B Person Enrichment & Verified Email Finder… MCP server?

Apollo.io B2B Person Enrichment & Verified Email Finder… is a hosted endpoint at https://enrichmatch.dev/api/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

remote · enrichmatch.dev

# add to Claude Code
claude mcp add --transport http nrorvem-apollo-person-enrichment 'https://enrichmatch.dev/api/mcp'
Common questions

What is the Apollo.io B2B Person Enrichment & Verified Email Finder… MCP server?

Apollo.io B2B Person Enrichment & Verified Email Finder… is an MCP server listed in the public MCP registry as io.github.Nrorvem/apollo-person-enrichment. Apollo.io B2B Person Enrichment & Verified Work Email Finder via x402 on Base ($0.03, free on miss). This page covers its hosted endpoint (https://enrichmatch.dev/api/mcp).

Is the Apollo.io B2B Person Enrichment & Verified Email Finder… MCP server safe to use?

Apollo.io B2B Person Enrichment & Verified Email Finder… scores 62 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the Apollo.io B2B Person Enrichment & Verified Email Finder… MCP server expose?

Apollo.io B2B Person Enrichment & Verified Email Finder… exposes 7 tools: get_enrichment_quote, search_people, search_organizations, enrich_person, enrich_organization, and 2 more. Their descriptions and schemas cost roughly 1,652 tokens of context every time the server is loaded.

Does the Apollo.io B2B Person Enrichment & Verified Email Finder… MCP server require authentication?

No. We connected to Apollo.io B2B Person Enrichment & Verified Email Finder… without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the Apollo.io B2B Person Enrichment & Verified Email Finder… MCP server still maintained?

Apollo.io B2B Person Enrichment & Verified Email Finder… is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.