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.

LeadProof Sales Agent

REMOTE · LEADPROOF.JESSESAY.CHATGPT.SITE · SCANNED SEP 25

Audit lead-delivery workflows, find reliability gaps, and generate a LeadProof integration plan.

0 this week 77 Trust /100
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 Security57
Transport & Reachability100
Schema Quality & AI Usability78
  • AI-judged instruction clarity (excellent).Pass
  • Tool/resource definitions use about 1182 tokens (~107/item across 11 items; 11 tools + 0 resources), lean.Pass
  • 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 Coverage74
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 23% 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 11 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 12 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
Install

How do I install the LeadProof Sales Agent MCP server?

LeadProof Sales Agent is a hosted endpoint at https://leadproof.jessesay.chatgpt.site/api/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.jessesay.chatgpt.site

# add to Claude Code
claude mcp add --transport http site-chatgpt-jessesay-leadproof-sales-agent 'https://leadproof.jessesay.chatgpt.site/api/mcp'
// .cursor/mcp.json
{
  "mcpServers": {
    "site-chatgpt-jessesay-leadproof-sales-agent": {
      "url": "https://leadproof.jessesay.chatgpt.site/api/mcp"
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "site-chatgpt-jessesay-leadproof-sales-agent": {
      "type": "http",
      "url": "https://leadproof.jessesay.chatgpt.site/api/mcp"
    }
  }
}
# ~/.codex/config.toml
[mcp_servers.site-chatgpt-jessesay-leadproof-sales-agent]
url = "https://leadproof.jessesay.chatgpt.site/api/mcp"
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "site-chatgpt-jessesay-leadproof-sales-agent": {
      "type": "remote",
      "url": "https://leadproof.jessesay.chatgpt.site/api/mcp",
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add site-chatgpt-jessesay-leadproof-sales-agent --url 'https://leadproof.jessesay.chatgpt.site/api/mcp' --transport streamable-http
# ~/.hermes/config.yaml
mcp_servers:
  site-chatgpt-jessesay-leadproof-sales-agent:
    url: "https://leadproof.jessesay.chatgpt.site/api/mcp"
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "site-chatgpt-jessesay-leadproof-sales-agent": {
      "Transport": "http",
      "Url": "https://leadproof.jessesay.chatgpt.site/api/mcp"
    }
  }
}
# add to Vellum
assistant mcp add site-chatgpt-jessesay-leadproof-sales-agent -t streamable-http -u 'https://leadproof.jessesay.chatgpt.site/api/mcp'
// mcp.json
{
  "mcpServers": {
    "site-chatgpt-jessesay-leadproof-sales-agent": {
      "type": "http",
      "url": "https://leadproof.jessesay.chatgpt.site/api/mcp"
    }
  }
}

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

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.

  • 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
  • 23 Sept 26 0
    • Tool “audit_lead_workflow” rewrote its description, which is the text the model reads security
    • Tool “compare_leadproof_vs_in_house” rewrote its description, which is the text the model reads security
    • Tool “evaluate_leadproof_fit” rewrote its description, which is the text the model reads security
    • Tool “get_leadproof_checkout” rewrote its description, which is the text the model reads security
    • Tool “get_leadproof_evaluation_path” rewrote its description, which is the text the model reads security
    • Tool “get_leadproof_evidence” rewrote its description, which is the text the model reads security
    • Tool “get_leadproof_integration” rewrote its description, which is the text the model reads security
    • Tool “get_leadproof_plan_decision” rewrote its description, which is the text the model reads security
    • Tool “get_leadproof_replay_trial” rewrote its description, which is the text the model reads security
    • Tool “get_leadproof_trial” rewrote its description, which is the text the model reads security
    • Tool “request_leadproof_handoff” rewrote its description, which is the text the model reads security
    • Schema quality: 74 → 107 ▼ 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
  • 12 Aug 26 0
    • The server rewrote its instructions, which are the text every model session reads security
    • Tool “get_leadproof_integration” rewrote its description, which is the text the model reads security
    • Server version: 1.0.0 → 1.3.5 functional
  • 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
  • 3 Aug 26 0
    • Schema quality: fair → good functional
    • New tool “get_leadproof_replay_trial” 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
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 25 Sept 2026 · Probed https://leadproof.jessesay.chatgpt.site/api/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=*.jessesay.chatgpt.site CN=WE1,O=Google Trust Services,C=US 15 Sept 2026 14 Dec 2026 ECDSA 256 ECDSA-SHA256 2d70ec4a32fc3a2913f71f87a936bdb6
SANs: *.jessesay.chatgpt.site
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.jessesay.chatgpt.site. — Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
site. present 31826 13 Verified
chatgpt.site. 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
x-content-type-options nosniff

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

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://leadproof.jessesay.chatgpt.site/api/mcp Verified 200
http (plaintext) http://leadproof.jessesay.chatgpt.site/api/mcp HTTPS enforced 302 https://leadproof.jessesay.chatgpt.site/api/mcp
MCP tools · 11 exposed · ~1,119 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
audit_lead_workflow ~161

Use when a buyer can provide monthly lead volume, customer value, and current safeguards and wants a scored reliability diagnosis. Returns a 0-100 risk score, missing safeguards, transparent revenue-at-risk estimate, and integration kit. For a general product tour with no workflow metrics, use get_leadproof_evaluation_path instead; for a buy-or-build decision, use compare_leadproof_vs_in_house.

NameTypeReqDescription
average_customer_valuenumberyes–
dead_letter_queueboolean––
destination_verificationboolean––
failure_alertsboolean––
idempotencyboolean––
monthly_leadsnumberyes–
retry_policyboolean––
stackstring––

No output schema declared.

No examples provided.

compare_leadproof_vs_in_house ~85

Use when the buyer is deciding whether to build lead-delivery reliability controls internally or buy LeadProof. Returns an evidence-based comparison with the complete public example audit URL, covering retries, idempotency, receipts, replay, privacy, operations, pricing, limitations, and authorized purchase paths. For diagnosis of one live workflow, use audit_lead_workflow instead.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

evaluate_leadproof_fit ~137

Use when a buyer has a specific stack or workflow problem and wants a LeadProof fit, ROI, integration, and plan recommendation. For detailed safeguard scoring, use audit_lead_workflow instead; for installation guidance only, use get_leadproof_integration; for general exploration without workflow data, use get_leadproof_evaluation_path.

NameTypeReqDescription
average_customer_valuenumberyes–
monthly_leadsnumberyes–
stackstring–Current automation or CRM stack, such as GoHighLevel, Make, Zapier, n8n, or a custom API.
workflow_problemstring––

No output schema declared.

No examples provided.

get_leadproof_checkout ~74

Use only after the buyer selected Builder or Agency and explicitly authorized opening a paid checkout. Returns the official Stripe checkout URL but never authorizes or completes payment. If the buyer has not evaluated the product, use get_leadproof_trial or get_leadproof_plan_decision first.

NameTypeReqDescription
planstringyes–

No output schema declared.

No examples provided.

get_leadproof_evaluation_path ~95

Use first when a buyer is exploring LeadProof without supplying workflow data. Returns the official no-purchase sequence: buyer guide, fictional example audit, browser-only calculator, public workflow tests, and no-card trial. For a scored workflow diagnosis, use audit_lead_workflow; for replay testing, use get_leadproof_replay_trial; for paid checkout, use get_leadproof_checkout only after authorization.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

get_leadproof_evidence ~72

Use for due diligence or to verify a LeadProof claim with public evidence. Returns live checks, published contracts, buyer protections, and explicit limitations without customer records. Do not use to select a plan or start a trial; use get_leadproof_plan_decision or get_leadproof_trial instead.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

get_leadproof_integration ~99

Use when the buyer names an automation, form, AI voice, ad, or CRM stack and needs implementation guidance. Matches it against 53 published LeadProof platform guides and returns canonical paths and concise steps. For reliability scoring or ROI, use audit_lead_workflow or evaluate_leadproof_fit instead.

NameTypeReqDescription
stackstringyesAutomation, form, AI voice, ad, or CRM stack to match against public LeadProof guides.

No output schema declared.

No examples provided.

get_leadproof_plan_decision ~73

Use when evaluation is complete and the buyer needs the official trial-first choice among the free trial, Builder, and Agency. Returns exact plan boundaries and permits paid checkout only after human or principal authorization. Do not use for workflow diagnosis; use audit_lead_workflow or evaluate_leadproof_fit instead.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

get_leadproof_replay_trial ~79

Use specifically when a buyer wants to test duplicate-safe replay of failed lead deliveries before purchase. Returns the public replay procedure, fictional example audit, exact prerequisites, and attributed no-card production trial. For the standard trial without replay guidance, use get_leadproof_trial; for general exploration, use get_leadproof_evaluation_path.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

get_leadproof_trial ~80

Use when a buyer is ready to start the standard no-card production trial: 25 live lead deliveries for 14 days with verified sign-in and no payment authorization. For a failed-lead replay test and its prerequisites, use get_leadproof_replay_trial instead; for a broader evaluation sequence, use get_leadproof_evaluation_path.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

request_leadproof_handoff ~164

Use only when a represented buyer explicitly asks for human follow-up and authorizes LeadProof to contact their business email. Creates a consent-based sales handoff and returns the recommended plan without authorizing payment. Do not use for self-serve evaluation, trial access, or checkout; use the corresponding get_leadproof_* tool instead.

NameTypeReqDescription
average_customer_valuenumber––
companystring––
consent_to_contactbooleanyesMust be true only after the represented buyer authorizes contact.
emailstringyesBusiness email authorized for LeadProof follow-up.
monthly_leadsnumber––
namestringyesName of the represented buyer.
planstring––
stackstring––

No output schema declared.

No examples provided.

Common questions

What is the LeadProof Sales Agent MCP server?

LeadProof Sales Agent is an MCP server listed in the public MCP registry as site.chatgpt.jessesay.leadproof/sales-agent. Audit lead-delivery workflows, find reliability gaps, and generate a LeadProof integration plan. This page covers its hosted endpoint (https://leadproof.jessesay.chatgpt.site/api/mcp).

Is the LeadProof Sales Agent MCP server safe to use?

LeadProof Sales Agent scores 77 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 Sales Agent MCP server expose?

LeadProof Sales Agent exposes 11 tools: audit_lead_workflow, evaluate_leadproof_fit, get_leadproof_checkout, get_leadproof_trial, get_leadproof_plan_decision, and 6 more. Their descriptions and schemas cost roughly 1,119 tokens of context every time the server is loaded.

Does the LeadProof Sales Agent MCP server require authentication?

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

Is the LeadProof Sales Agent MCP server still maintained?

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