LeadProof
REMOTE · LEADPROOF.CO · SCANNED SEP 20
Verified local-business lead lists: quote, sample and order. The person approves every payment.
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 Security80
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability80
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 860 tokens (~143/item across 6 items; 6 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 Management27
- Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 6 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 7 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
How do I install the LeadProof MCP server?
LeadProof is a hosted endpoint at https://leadproof.co/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 · leadproof.co
claude mcp add --transport http co-leadproof-leadproof 'https://leadproof.co/mcp'
{
"mcpServers": {
"co-leadproof-leadproof": {
"url": "https://leadproof.co/mcp"
}
}
} {
"servers": {
"co-leadproof-leadproof": {
"type": "http",
"url": "https://leadproof.co/mcp"
}
}
} [mcp_servers.co-leadproof-leadproof] url = "https://leadproof.co/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"co-leadproof-leadproof": {
"type": "remote",
"url": "https://leadproof.co/mcp",
"enabled": true
}
}
} openclaw mcp add co-leadproof-leadproof --url 'https://leadproof.co/mcp' --transport streamable-http
mcp_servers:
co-leadproof-leadproof:
url: "https://leadproof.co/mcp" {
"McpServers": {
"co-leadproof-leadproof": {
"Transport": "http",
"Url": "https://leadproof.co/mcp"
}
}
} assistant mcp add co-leadproof-leadproof -t streamable-http -u 'https://leadproof.co/mcp'
{
"mcpServers": {
"co-leadproof-leadproof": {
"type": "http",
"url": "https://leadproof.co/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.
- 19 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.
- 17 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.
- 15 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.
- 13 Sept 26 +1
- Stability: unverified → 0.03 ▲ functional
- 12 Sept 26 74
First indexed and scored.
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://leadproof.co/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=leadproof.co | CN=WE1,O=Google Trust Services,C=US | 24 Jul 2026 | 22 Oct 2026 | ECDSA 256 | ECDSA-SHA256 | 1359dcc48737c2ab138dc03bcfc4b453 |
| SANs: leadproof.co, www.leadproof.co, *.www.leadproof.co | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of leadproof.co. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| co. | present | 7786 | 8 | Verified |
| leadproof.co. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
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=31536000 |
| x-content-type-options | nosniff |
| x-frame-options | DENY |
| referrer-policy | strict-origin-when-cross-origin |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://leadproof.co/mcp | Verified | 200 | |
| http (plaintext) | http://leadproof.co/mcp | HTTPS enforced | 301 | https://leadproof.co/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 →
create_order Create an order (PayPal approval link) ~209
Creates the order and returns a PayPal approval link. The PERSON must open the link and approve the payment; nothing is charged until they do. Ask for the delivery email first: the CSV and the order page go there. Returns the order id, the approval link, an order-status link and a status token for get_order_status.
| Name | Type | Req | Description |
|---|---|---|---|
| business_types | array | yes | Business categories to find, e.g. ["HVAC contractor"]. Each one becomes a Google Maps search term. |
| string | yes | Delivery email. The CSV download and order updates go here. | |
| locations | array | yes | Cities, regions or countries, e.g. ["Austin, TX", "Dallas, TX"]. Anything Google Maps can resolve. |
| min_reviews | integer | – | Only businesses with at least this many Google reviews. 0 means no filter. A higher bar costs more per lead and screens out more businesses. |
| qty | integer | yes | How many verified leads to deliver, 100 to 1000. |
No output schema declared.
No examples provided.
get_checkout_link Get a prefilled checkout link ~168
A leadproof.co link with the list already configured. The person opens it, reviews the price and pays on the site. Use this when they prefer to finish in a browser. Nothing is created until they order.
| Name | Type | Req | Description |
|---|---|---|---|
| business_types | array | yes | Business categories to find, e.g. ["HVAC contractor"]. Each one becomes a Google Maps search term. |
| locations | array | yes | Cities, regions or countries, e.g. ["Austin, TX", "Dallas, TX"]. Anything Google Maps can resolve. |
| min_reviews | integer | – | Only businesses with at least this many Google reviews. 0 means no filter. A higher bar costs more per lead and screens out more businesses. |
| qty | integer | yes | How many verified leads to deliver, 100 to 1000. |
No output schema declared.
No examples provided.
get_order_status Get order status ~76
Status of an order created with create_order: awaiting approval, in review, building, delivered (with a download link) or refunded. Needs the order_id and status_token that create_order returned.
| Name | Type | Req | Description |
|---|---|---|---|
| order_id | string | yes | The order id from create_order. |
| status_token | string | yes | The status_token from create_order. |
No output schema declared.
No examples provided.
get_pricing Get LeadProof pricing ~38
Price tiers, review-filter multipliers, quantity limits and what a delivered list contains. Call this before quoting if the person wants to compare options.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_sample_leads Get sample leads ~53
A few illustrative rows in the exact delivered format (placeholder businesses on reserved example domains, not real leads), plus the column reference.
| Name | Type | Req | Description |
|---|---|---|---|
| count | integer | – | How many sample rows, 1 to 10. |
No output schema declared.
No examples provided.
quote_lead_list Quote a lead list ~163
Exact price for a lead list: business types, locations, quantity and optional minimum-review bar. Returns the amount the site charges, what is included and delivery terms. Nothing is created.
| Name | Type | Req | Description |
|---|---|---|---|
| business_types | array | yes | Business categories to find, e.g. ["HVAC contractor"]. Each one becomes a Google Maps search term. |
| locations | array | yes | Cities, regions or countries, e.g. ["Austin, TX", "Dallas, TX"]. Anything Google Maps can resolve. |
| min_reviews | integer | – | Only businesses with at least this many Google reviews. 0 means no filter. A higher bar costs more per lead and screens out more businesses. |
| qty | integer | yes | How many verified leads to deliver, 100 to 1000. |
No output schema declared.
No examples provided.
What is the LeadProof MCP server?
LeadProof is an MCP server listed in the public MCP registry as co.leadproof/leadproof. Verified local-business lead lists: quote, sample and order. The person approves every payment. This page covers its hosted endpoint (https://leadproof.co/mcp).
Is the LeadProof MCP server safe to use?
LeadProof 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 LeadProof MCP server expose?
LeadProof exposes 6 tools: get_pricing, quote_lead_list, get_sample_leads, get_checkout_link, create_order, get_order_status. Their descriptions and schemas cost roughly 707 tokens of context every time the server is loaded.
Does the LeadProof MCP server require authentication?
No. We connected to LeadProof without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the LeadProof MCP server still maintained?
LeadProof 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.