Lead Enrichment API
REMOTE · LEADS.COMPUUTE.SE · SCANNED SEP 20
Curated EU AI/Sec/DevTools/Fintech B2B leads, Claude-scored. MCP+x402. Free 250/mo.
Available components
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 Security66
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- 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. See how to fix → View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC is configured correctly; the domain's records validate against the full chain to the root. View diagnostics → Pass
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability77
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 419 tokens (~139/item across 3 items; 3 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 Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage67
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 0% of tool parameters carry a description.Fail
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
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/'
{
"mcpServers": {
"compuute-lead-enrichment": {
"url": "https://leads.compuute.se/mcp/"
}
}
} {
"servers": {
"compuute-lead-enrichment": {
"type": "http",
"url": "https://leads.compuute.se/mcp/"
}
}
} [mcp_servers.compuute-lead-enrichment] url = "https://leads.compuute.se/mcp/"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"compuute-lead-enrichment": {
"type": "remote",
"url": "https://leads.compuute.se/mcp/",
"enabled": true
}
}
} openclaw mcp add compuute-lead-enrichment --url 'https://leads.compuute.se/mcp/' --transport streamable-http
mcp_servers:
compuute-lead-enrichment:
url: "https://leads.compuute.se/mcp/" {
"McpServers": {
"compuute-lead-enrichment": {
"Transport": "http",
"Url": "https://leads.compuute.se/mcp/"
}
}
} assistant mcp add compuute-lead-enrichment -t streamable-http -u 'https://leads.compuute.se/mcp/'
{
"mcpServers": {
"compuute-lead-enrichment": {
"type": "http",
"url": "https://leads.compuute.se/mcp/"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
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.
- 26 Aug 26 +1
- 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 +1
- Stability: 0.97 → pass security
- 24 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 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
- 31 Jul 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
- 30 Jul 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
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 20 Sept 2026 · Probed https://leads.compuute.se/mcp/
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=leads.compuute.se | CN=YR1,O=Let's Encrypt,C=US | 18 Sept 2026 | 17 Dec 2026 | RSA 2048 | SHA256-RSA | 615804d60eb0aae37cacab2bd2b1a7f954e |
| SANs: leads.compuute.se | ||||||
| CN=YR1,O=Let's Encrypt,C=US (CA) | CN=Root YR,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | RSA 2048 | SHA256-RSA | a20253f15f2691c05dc1ce13b9bcca4e |
| 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 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 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; includeSubDomains |
| x-content-type-options | nosniff |
| x-frame-options | DENY |
| referrer-policy | strict-origin-when-cross-origin |
| permissions-policy | geolocation=(), microphone=(), camera=() |
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/ | Verified | 200 | |
| http (plaintext) | http://leads.compuute.se/mcp/ | HTTPS enforced | 301 | https://leads.compuute.se/mcp/ |
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.
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?
No. We connected to Lead Enrichment API without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Lead Enrichment API MCP server still maintained?
Lead Enrichment API is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.