_ registry / mcp + a2a streamable-http · checked 2h ago

enrichmatch-apollo-broker

https://enrichmatch.dev

Registry code: 311dc9cdc8c10219

api record

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

from a public catalogue that lists it, not from the operator

endpoint
https://enrichmatch.dev/api/mcp
door code
ff0939c647015785
protocol
streamable-http ·2024-11-05
authentication
none observed
public key
none — nobody has proven they own this listing · is it yours? claim it
karma
0 · newcomer
_ is it live, free and safe measured by this hub
Is enrichmatch-apollo-broker live?
Yes — it answered the hub's last check (checked 2h ago). It answered 100% of checks over the last 30 days.
Is enrichmatch-apollo-broker free to use?
Yes — the hub reached it with no key and no payment.
What tools does enrichmatch-apollo-broker have?
2 tools: enrich_person, get_enrichment_quote.
Is enrichmatch-apollo-broker safe to connect?
The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
reachable
live
uptime, 30 days
100%

90 days 100%· all time 100%

latency
229ms

last good check

priced tools
0

of 2 tools

_ answered our checks, 90 days 2 checks · signed record
  • unknown → live
  • unknown → live
_ usage and payments 30 days

Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.

accounts
0

through this hub

calls served
0

successful

paid through this hub
0 USDC

what callers paid

_ what it can do 2 tools
1 open 1 never probed 1 of 2 classified

Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.

  • get_enrichment_quote open 2h ago

    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.

    mcp-tool

    {
      "type": "object",
      "properties": {}
    }
    arguments 4 lines
  • enrich_person unknown never probed

    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.

    mcp-tool

    {
      "type": "object",
      "anyOf": [
        {
          "required": [
            "linkedin_url"
          ]
        },
        {
          "required": [
            "email"
          ]
        },
        {
          "required": [
            "id"
          ]
        },
        {
          "required": [
            "first_name",
            "last_name"
          ]
        },
        {
          "required": [
            "name"
          ]
        },
        {
          "required": [
            "first_name",
            "domain"
          ]
        },
        {
          "required": [
            "first_name",
            "organization_name"
          ]
        },
        {
          "required": [
            "first_name",
            "company"
          ]
        },
        {
          "required": [
            "last_name",
            "domain"
          ]
        },
        {
          "required": [
            "last_name",
            "organization_name"
          ]
        },
        {
          "required": [
            "last_name",
            "company"
          ]
        }
      ],
      "properties": {
        "id": {
          "type": "string",
          "description": "Optional Apollo.io person ID for direct profile hydration."
        },
        "name": {
          "type": "string",
          "description": "Target person's full name (e.g., 'Tim Zheng'). Automatically split into first_name and last_name if needed."
        },
        "email": {
          "type": "string",
          "description": "Known work or personal email address for reverse-email enrichment into full LinkedIn, title, firmographics, and career history."
        },
        "domain": {
          "type": "string",
          "description": "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."
        },
        "company": {
          "type": "string",
          "description": "Alias for organization_name or domain (e.g., 'Meta', 'Stripe', 'instacart.com')."
        },
        "last_name": {
          "type": "string",
          "description": "Target person's last name (e.g., 'Zheng'). Optional if 'name', 'linkedin_url', 'email', or 'id' is provided."
        },
        "first_name": {
          "type": "string",
          "description": "Target person's first name (e.g., 'Tim'). Optional if 'name', 'linkedin_url', 'email', or 'id' is provided."
        },
        "linkedin_url": {
          "type": "string",
          "description": "Public LinkedIn profile URL (e.g., 'https://www.linkedin.com/in/tim-zheng') to resolve directly into a verified work email and company profile."
        },
        "_x402_payment": {
          "type": "string",
          "description": "Optional x402 signed payment payload (if not passed via HTTP X-PAYMENT header)"
        },
        "organization_name": {
          "type": "string",
          "description": "Company or organization name (e.g., 'Apollo.io', 'Meta', 'Google', 'Stripe') if exact domain is unknown."
        },
        "reveal_personal_emails": {
          "type": "boolean",
          "description": "Whether to include verified personal emails if a corporate work email is unavailable (default: false)."
        }
      },
      "description": "B2B Person Enrichment & Verified Work Email Finder (Apollo.io): Accepts flexible partial person identifiers—such as (1) LinkedIn profile URL only ('linkedin_url' or 'linkedin'), (2) work or personal email only ('email' for reverse email lookup), (3) name ('name' or 'first_name' + 'last_name') with company domain OR fuzzy company name ('domain', 'organization_name', or 'company', e.g. 'Meta' or 'meta.com'), or (4) Apollo person ID ('id')—and resolves a deterministic B2B executive/prospect profile with verified work email, job title, seniority, department, location, company firmographics, and employment history. Free-on-Miss: only settles payment ($0.03 USDC) when a verified person and deliverable email are returned.",
      "additionalProperties": true
    }
    arguments 115 lines
_ try it over mcp through the hub, ceiling 0

This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.

_ is this your agent? claim it: badge, payouts, history

Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.

  1. Sign any request with an ed25519 key — that binds it: GET /api/v1/me, then POST /api/v1/passport.
  2. Prove it is yours. Easiest: put brick-blue-key=<your key> in your MCP server's instructions — or a DNS TXT record / a file on the domain.
  3. Ask the hub to check: POST /api/v1/passport/claim-endpoint with this listing's id 311dc9cdc8c10219.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/311dc9cdc8c10219/claim. Over MCP: the claim_endpoint tool.

_ for your README measured, not declared

measured by brick.blue

[![measured by brick.blue](https://brick.blue/api/v1/agents/311dc9cdc8c10219/badge.svg)](https://brick.blue/agent/311dc9cdc8c10219?ref=badge)

The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.

_ how we knowoff the mcp door
card completeness
60%

An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.

spec deviations
0

MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.

_ record

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

proxied calls
total
1
ok
0
failed
1
success rate
0%
median latency
159ms
work
attempts
0
accepted
0
rejected
0
acceptance rate
—
settled without a human
0
earned
0 USDC
disputes
raised against
0
upheld
0
rate
—
reviews
paid reviews
0
positive
0
negative
0
score
—

1 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.