mcpbeat

Lead Enrichment API MCP Server

io.github.Compuute/lead-enrichment
answering

Lead Enrichment API is answering right now. Last checked moments ago. It exposes 3 tools.

Curated EU AI/Sec/DevTools/Fintech B2B leads, Claude-scored. MCP+x402. Free 250/mo.

The linked repository no longer exists on GitHub — it was deleted or made private.

Uptime history 40 hours of history
40 hours agonow
100.0%
Uptime 24h
92 of 92 checks
3
Tools
read from the server
544 ms
Response time
average over 24h
open, no key
Access
streamable-http

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 0 min ago.

run in your terminal
claude mcp add lead-enrichment --transport http https://leads.compuute.se/mcp/
~/Library/Application Support/Claude/claude_desktop_config.json
{
  "mcpServers": {
    "lead-enrichment": {
      "url": "https://leads.compuute.se/mcp/"
    }
  }
}
~/.codex/config.toml
[mcp_servers.lead-enrichment]
url = "https://leads.compuute.se/mcp/"
.cursor/mcp.json
{
  "mcpServers": {
    "lead-enrichment": {
      "url": "https://leads.compuute.se/mcp/"
    }
  }
}
.vscode/mcp.json
{
  "mcpServers": {
    "lead-enrichment": {
      "url": "https://leads.compuute.se/mcp/"
    }
  }
}

Available tools 3

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

leads
search_leads
Search enriched B2B leads by ICP criteria. Returns scored companies with firmographics, tech stack signals, and buying signals. Each lead returned counts against the monthly quota. Args: industries: Filter by industry — AI, Blockchain, Fintech, Security, Healthcare, DevTools, Other stages: Funding stage — Pre-seed, Seed, Series A, Series B, Series C+, Public, Unknown regions: EU, US, APAC, MENA, Other min_icp_score: 0-100, minimum ICP fit score min_buying_intent: 0-100, minimum buying intent score tech_stack_contains: must match at least one signal max_age_days: only leads enriched within N days (1-365) limit: leads per response (1-100) sort_by: icp_score, buying_intent, employees, or enriched_at
usage
get_usage
Return current month quota status and recent usage for the calling API key.
validate
validate_lead
Check the freshness and website reachability of a specific lead. Args: lead_id: UUID of the lead to validate

Endpoints

URLTransportStateLatencyChecked
https://leads.compuute.se/mcp/ streamable-http answering 635 ms 0 min ago

Lead Enrichment API — questions

Answers built from our own checks of this server.

What can Lead Enrichment API do?
It exposes 3 tools, read directly from the server on our last check. Among them: get_usage, search_leads, validate_lead. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →
Is Lead Enrichment API working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 92 of 92 checks got a reply (100.0%), average response time 544 ms. The bar chart above shows every period we have measured.
Is Lead Enrichment API still maintained?
The linked repository no longer exists on GitHub — it was deleted or made private. We show this because it changes what you can expect: an unmaintained server may keep answering for months and then stop without warning.
How do I connect Lead Enrichment API?
Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.
Does Lead Enrichment API need an API key?
No. Lead Enrichment API completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 3 of them are readable on this page. This is what we observed, not what the docs claim.
How fast is Lead Enrichment API?
It answers our handshake in 544 ms on average, which is faster than 19% of all working MCP servers we measure. That is on the slow side — worth knowing if the tool sits inside an interactive loop. The comparison comes from our own checks across the whole registry, every 15 minutes.