_ registry / mcp streamable-http · checked 1h ago

ListPlus

https://listplus.ai

Registry code: 7aadaef127fd4b1f

api record

# ListPlus agent API

ListPlus checks contact data with 100+ data-quality checks — typos in e-mail

endpoint
https://listplus.ai/mcp
protocol
streamable-http ·2025-06-18
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 ListPlus live?
Yes — it answered the hub's last check (checked 1h ago). It answered 100% of checks over the last 30 days.
Is ListPlus free to use?
Yes — the hub reached it with no key and no payment.
What tools does ListPlus have?
6 tools: get_job, enrich_records, verify_email, find_person, check_records, what_can_you_do.
Is ListPlus 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
354ms

last good check

priced tools
0

of 6 tools

_ answered our checks, 90 days 1 checks · signed record
  • 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 6 tools
1 open 5 never probed 1 of 6 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.

  • what_can_you_do open 1h ago

    FREE — what ListPlus can do for you: every action, the fields we can fill with their price per record, the free limits, and (with a key) your balance and day budget. Call this first if unsure.

    mcp-tool

    {
  "type": "object",
  "properties": {
    "language": {
      "enum": [
        "en",
        "de"
      ],
      "type": "string",
      "description": "Language of `tell_your_user` (default en)"
    }
  },
  "additionalProperties": false
}
    arguments 14 lines
  • get_job unknown never probed

    FREE (key) — the state of an enrich_records job; when it ended, the records with the fields we found (in the order you sent them).

    mcp-tool

    {
  "type": "object",
  "required": [
    "job_id"
  ],
  "properties": {
    "job_id": {
      "type": "string",
      "maxLength": 60,
      "minLength": 3
    },
    "language": {
      "enum": [
        "en",
        "de"
      ],
      "type": "string",
      "description": "Language of `tell_your_user` (default en)"
    }
  },
  "additionalProperties": false
}
    arguments 22 lines
  • enrich_records unknown never probed

    PAID (needs a key) — per record from a name + company: work e-mail ≈2.39, at most 9 credits; mobile ≈3.84, at most 12; job title ≈1.41, at most 13.5. Charged per hit for e-mail and phone. Use estimate:true first for the exact price of YOUR records (free, no key). Fills fields of contact records (work e-mail, mobile, job title, LinkedIn profile, company, domain, industry, size, place). The records go into the key's agent list in ListPlus (the user can open it); waits up to 25 s, then answers with a job_id to poll (get_job).

    mcp-tool

    {
  "type": "object",
  "required": [
    "records",
    "fields"
  ],
  "properties": {
    "fields": {
      "type": "array",
      "items": {
        "type": "string"
      },
      "minItems": 1,
      "description": "Fields to fill: email, phone, job_title, linkedin_profile_url, company_name, domain, industry, city, country"
    },
    "records": {
      "type": "array",
      "items": {
        "type": "object",
        "propertyNames": {
          "type": "string"
        },
        "additionalProperties": {}
      },
      "minItems": 1,
      "description": "Records as JSON objects. Any key names (e.g. first_name, last_name, email, company_name, domain, linkedin_profile_url, job_title, phone, country, city — or Vorname, Firma, Mail …); the answer says how each key was read."
    },
    "estimate": {
      "type": "boolean",
      "description": "true = only the price for these records, nothing runs (free, no key needed)"
    },
    "language": {
      "enum": [
        "en",
        "de"
      ],
      "type": "string",
      "description": "Language of `tell_your_user` (default en)"
    },
    "request_id": {
      "type": "string",
      "maxLength": 100,
      "description": "Your id for this call — a repeat with it gets the same job"
    },
    "max_credits": {
      "type": "number",
      "description": "The most this call may cost (default: the key's day budget left)",
      "exclusiveMinimum": 0
    }
  },
  "additionalProperties": false
}
    arguments 52 lines
  • verify_email unknown never probed

    PAID (needs a key) — 0.3 credits per address (an address checked in the last 7 days costs nothing): is the e-mail address deliverable (valid, invalid, catch_all, unknown)? Up to 25 addresses per call, answered at once.

    mcp-tool

    {
  "type": "object",
  "required": [
    "emails"
  ],
  "properties": {
    "emails": {
      "type": "array",
      "items": {
        "type": "string",
        "maxLength": 200
      },
      "maxItems": 25,
      "minItems": 1
    },
    "language": {
      "enum": [
        "en",
        "de"
      ],
      "type": "string",
      "description": "Language of `tell_your_user` (default en)"
    }
  },
  "additionalProperties": false
}
    arguments 26 lines
  • find_person unknown 1h ago

    FREE (rate-limited) — find a person: name, job title, company, location, LinkedIn profile, how sure. Give first_name + last_name + company (or domain), a LinkedIn URL, a work e-mail, or a question in `query` ("CFO of Tink in Berlin"). No e-mail or phone in the answer — those are enrich_records.

    mcp-tool

    {
  "type": "object",
  "properties": {
    "name": {
      "type": "string",
      "maxLength": 200,
      "description": "Full name, when there is no split"
    },
    "email": {
      "type": "string",
      "maxLength": 200,
      "description": "A WORK e-mail (not Gmail etc.)"
    },
    "query": {
      "type": "string",
      "maxLength": 300
    },
    "domain": {
      "type": "string",
      "maxLength": 200
    },
    "company": {
      "type": "string",
      "maxLength": 200
    },
    "eu_only": {
      "type": "boolean",
      "description": "Only services in the EU (skips one US web index)"
    },
    "language": {
      "enum": [
        "en",
        "de"
      ],
      "type": "string",
      "description": "Language of `tell_your_user` (default en)"
    },
    "last_name": {
      "type": "string",
      "maxLength": 100
    },
    "first_name": {
      "type": "string",
      "maxLength": 100
    },
    "linkedin_url": {
      "type": "string",
      "maxLength": 300
    }
  },
  "additionalProperties": false
}
    arguments 52 lines
  • check_records unknown 1h ago

    FREE (up to 25 records without a key, 1000 with one) — check contact records for errors with 100+ checks: typos in e-mail domains, role mailboxes (office@), duplicates and near-duplicates, phone codes that do not fit the country, LinkedIn status text in names, placeholders … Returns findings per record with proposed fixes. Nothing is stored or changed.

    mcp-tool

    {
  "type": "object",
  "required": [
    "records"
  ],
  "properties": {
    "ai": {
      "type": "boolean",
      "description": "Also run the AI checks (fake names, a person's name as company, department instead of job title, city vs country) — PAID, needs a key; the price range is in `options`"
    },
    "records": {
      "type": "array",
      "items": {
        "type": "object",
        "propertyNames": {
          "type": "string"
        },
        "additionalProperties": {}
      },
      "minItems": 1,
      "description": "Records as JSON objects. Any key names (e.g. first_name, last_name, email, company_name, domain, linkedin_profile_url, job_title, phone, country, city — or Vorname, Firma, Mail …); the answer says how each key was read."
    },
    "language": {
      "enum": [
        "en",
        "de"
      ],
      "type": "string",
      "description": "Language of `tell_your_user` (default en)"
    },
    "categories": {
      "type": "array",
      "items": {
        "type": "string"
      },
      "description": "Only these areas: name, email, company, linkedin, job_title, phone, address, gender, duplicates, completeness, cross_field, compliance, campaign"
    }
  },
  "additionalProperties": false
}
    arguments 40 lines
_ try it 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 7aadaef127fd4b1f.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/7aadaef127fd4b1f/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/7aadaef127fd4b1f/badge.svg)](https://brick.blue/agent/7aadaef127fd4b1f?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 know
card completeness
100%

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
0
ok
0
failed
0
success rate
—
median latency
—
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
—

0 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.