Lead Enrichment API
REMOTE · LEADS.COMPUUTE.SE
Curated EU AI/Sec/DevTools/Fintech B2B leads, Claude-scored. MCP+x402. Free 250/mo.
Available components
Last scanned (6 hours ago)
Scores higher than 76% of remote servers
Unreachable for 1 day in a row. Last reached 4 Nov 2026.
Category CRM and Sales
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 Security14
- TLS not yet verified: we couldn't open a connection to check the certificate. View diagnostics → Unverified
- Authorisation not yet verified: we couldn't confirm whether this endpoint requires it. View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS not yet verified: we couldn't read the response headers to check for it. View diagnostics → Unverified
- DNSSEC is configured correctly; the domain's records validate against the full chain to the root. View diagnostics → Pass
Transport & Reachability0
- Transport check failed: declared streamable-http, but we couldn't connect to verify it. See how to fix → View diagnostics → Fail
Schema Quality & AI Usability0
- Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.Unverified
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
- Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Tool Safety0
- Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Capabilities0
- Capabilities not yet verified: we couldn't read the endpoint's capabilities.Unverified
Unverified: 5 categories
Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.
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 0
- Endpoint reachability: reachable → unreachable ▼ security
- Stability: pass → unverified ▼ security
- Tool safety: pass → 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
- 28 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 26 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Aug 26 0
- Stability: 0.97 → pass security
- 11 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 7 Aug 26 0
- The server no longer declares the “experimental” capability functional
- 6 Aug 26 0
- Authorization: Authorisation not fully verified: no authorisation is required to call this server, and 3 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
- Schema quality: unverified → fail ▼ functional
- Schema quality: pass → fail ▼ functional
- Tool coverage: unverified → 100 ▲ functional
- First check of Tool coverage: 0 functional
- Schema quality: poor → good functional
- New tool “get_usage” functional
- New tool “search_leads” functional
- New tool “validate_lead” functional
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://leads.compuute.se/mcp/
TLS unreached
Background: What to check on a remote MCP endpoint →
DNSSEC secure
Validation of leads.compuute.se. — Secure
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| se. | present | 59407 | 8 | Verified |
| compuute.se. | present | 51704 | 13 | Verified |
| leads.compuute.se. | Verified address RRset verified with the apex keys |
Authentication Inconclusive
We could not reach the endpoint well enough to judge its authorisation posture.
| Result | Inconclusive |
|---|
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://leads.compuute.se/mcp/ | Unreachable | ||
| http (plaintext) | http://leads.compuute.se/mcp/ | HTTPS enforced |
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 →
get_usage ~22
Return current month quota status and recent usage for the calling API key.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
search_leads ~269
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
| Name | Type | Req | Description |
|---|---|---|---|
| industries | – | – | – |
| limit | integer | – | – |
| max_age_days | integer | – | – |
| min_buying_intent | integer | – | – |
| min_icp_score | integer | – | – |
| regions | – | – | – |
| sort_by | string | – | – |
| stages | – | – | – |
| tech_stack_contains | – | – | – |
No output schema declared.
No examples provided.
validate_lead ~44
Check the freshness and website reachability of a specific lead. Args: lead_id: UUID of the lead to validate
| Name | Type | Req | Description |
|---|---|---|---|
| lead_id | string | yes | – |
No output schema declared.
No examples provided.
How do I install the Lead Enrichment API MCP server?
Lead Enrichment API is a hosted endpoint at https://leads.compuute.se/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 · leads.compuute.se
claude mcp add --transport http compuute-lead-enrichment 'https://leads.compuute.se/mcp/'
What is the Lead Enrichment API MCP server?
Lead Enrichment API is an MCP server listed in the public MCP registry as io.github.Compuute/lead-enrichment. Curated EU AI/Sec/DevTools/Fintech B2B leads, Claude-scored. MCP+x402. Free 250/mo. This page covers its hosted endpoint (https://leads.compuute.se/mcp/).
Is the Lead Enrichment API MCP server safe to use?
Lead Enrichment API scores 78 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 Lead Enrichment API MCP server expose?
Lead Enrichment API exposes 3 tools: search_leads, validate_lead, get_usage. Their descriptions and schemas cost roughly 335 tokens of context every time the server is loaded.
Does the Lead Enrichment API MCP server require authentication?
Its publisher declares no required credentials for Lead Enrichment API. We have not been able to confirm that against the live endpoint, and a server can require authorisation without declaring it here.
Is the Lead Enrichment API MCP server still maintained?
Lead Enrichment API is still listed in the MCP registry, though our most recent checks did not reach this channel. We last reached this channel on 4 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.