Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

LeadFuzion Agent Store

REMOTE · MCP.LEADFUZION.AI

US probate and pre-probate lead packages by county. No account; pay per package by card or USDC.

+3 this week 74 Trust /100

Last scanned (20 hours ago)

Scores higher than 60% of remote servers

Reachable. Last reached 21 Nov 2026.

Category CRM and Sales

Trust breakdown (7 categories)

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. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation. 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
Schema Quality & AI Usability62
  • AI-judged instruction clarity (good).Pass
  • Context-footprint check failed: tool/resource definitions use about 461 tokens (~153/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 Management30
  • Stability observed for 9 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage88
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 64% of tool parameters carry a description.Partial
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
Capabilities100
  • Implements a current MCP spec version (2026-07-28).Pass
What we tested

Checks we ran (13)

  • TLS certificate
  • Authorization
  • HTTPS
  • HSTS header
  • DNSSEC
  • Transport
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Does not apply to this hosted endpoint (2)

  • Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
  • Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.

The score does not measure everything. What the score does not measure →

Changelog

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.

  • 20 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.

  • 17 Nov 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 Nov 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 Nov 26 +1
    • Stability: unverified → 0.03 ▲ functional
  • 12 Nov 26 70

    First indexed and scored.

Diagnostics

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 21 Nov 2026 · Probed https://mcp.leadfuzion.ai/api/v1/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=mcp.leadfuzion.ai CN=YR2,O=Let's Encrypt,C=US 3 Oct 2026 1 Jan 2027 RSA 2048 SHA256-RSA 585767e64ec9f37540842578ca31b360416
SANs: mcp.leadfuzion.ai
CN=YR2,O=Let's Encrypt,C=US (CA) CN=Root YR,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 RSA 2048 SHA256-RSA 4ebd24947e24d394802d84a52fd5b319
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 insecure

Validation of mcp.leadfuzion.ai. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
ai. DS published 1814 8 Verified
leadfuzion.ai. No DS 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

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://mcp.leadfuzion.ai/api/v1/mcp Verified 200
http (plaintext) http://mcp.leadfuzion.ai/api/v1/mcp HTTPS enforced 301 https://mcp.leadfuzion.ai/api/v1/mcp
MCP tools · 3 exposed · ~413 tokens

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 →

Tool Tokens
buy_package ~219

Buy one LeadFuzion lead package (one item_id) at its listed price. Call get_package_quote first: it is free and shows the price. Without payment this returns the price and how to pay (x402 USDC on Base, MPP card, or MPP Tempo), and nothing is charged. If your client cannot pay inside MCP, pay at the HTTPS URL given and pass the order_token back here.

NameTypeReqDescription
accept_termsboolean–Must be true: you accept the terms at terms_url.
buyerstring–Who is buying: person or company name plus a contact. Recorded with the order.
item_idstringyes–
order_tokenstring–Proof of a purchase already paid at the HTTPS endpoint or in an earlier call. Redelivers that order; no charge, no attestation needed. Valid 7 days.
purposestring–What the leads will be used for. Recorded with the order.
terms_versionstring–terms_version from get_package_quote

No output schema declared.

No examples provided.

get_package_quote ~55

Get the price, lead count, record fields, buyer attestation rules and payment options for one package. Free: nothing is charged and no records are returned. Call this before buy_package.

NameTypeReqDescription
item_idstringyes–

No output schema declared.

No examples provided.

list_packages ~139

List LeadFuzion lead packages for sale: Historical Probate and FirstUp packages, one county and one month each. Pass state and county (e.g. AZ and Maricopa): the catalog is listed one county at a time. Free; nothing is charged. Each package shows its price and lead count; a lead set costs the same with or without skip tracing. Call get_package_quote for the terms and how to pay.

NameTypeReqDescription
countystring–County name without the word County
lead_typestring––
limitinteger––
statestring–Two-letter US state, e.g. AZ

No output schema declared.

No examples provided.

Install

How do I install the LeadFuzion Agent Store MCP server?

LeadFuzion Agent Store is a hosted endpoint at https://mcp.leadfuzion.ai/api/v1/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 · mcp.leadfuzion.ai

# add to Claude Code
claude mcp add --transport http ai-leadfuzion-mcp-agent-store 'https://mcp.leadfuzion.ai/api/v1/mcp'
Common questions

What is the LeadFuzion Agent Store MCP server?

LeadFuzion Agent Store is an MCP server listed in the public MCP registry as ai.leadfuzion.mcp/agent-store. US probate and pre-probate lead packages by county. No account; pay per package by card or USDC. This page covers its hosted endpoint (https://mcp.leadfuzion.ai/api/v1/mcp).

Is the LeadFuzion Agent Store MCP server safe to use?

LeadFuzion Agent Store scores 74 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 LeadFuzion Agent Store MCP server expose?

LeadFuzion Agent Store exposes 3 tools: list_packages, get_package_quote, buy_package. Their descriptions and schemas cost roughly 413 tokens of context every time the server is loaded.

Does the LeadFuzion Agent Store MCP server require authentication?

No. We connected to LeadFuzion Agent Store without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the LeadFuzion Agent Store MCP server still maintained?

LeadFuzion Agent Store is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What did VerifyMCP test on the LeadFuzion Agent Store MCP server?

VerifyMCP ran 13 checks on LeadFuzion Agent Store, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.