LeadProof Sales Agent is answering right now. Last checked moments ago. It exposes 11 tools.
Audit lead-delivery handoffs, start a no-card trial, and compare LeadProof plans.
Uptime history
91 days of history · worst day 88%
91 days agonow
100.0%
Uptime 24h
92 of 92 checks
11
Tools
read from the server
714 ms
Response time
average over 24h
open, no key
Access
streamable-http
What changed 16
Every tool that appeared, vanished or quietly changed what it asks for. Recorded since 11 August 2026. No other catalogue keeps this.
30 Sep
a tool changed version
23 Sep
11 tool descriptions were rewritten
audit_lead_workflow, compare_leadproof_vs_in_house, evaluate_leadproof_fit and 8 more
12 Aug
a tool description was rewritten
get_leadproof_integration
11 Aug
a tool appeared
get_leadproof_plan_decision
11 Aug
a tool description was rewritten
get_leadproof_integration
11 Aug
a tool changed version
LeadProof Sales Agent missed one check this week
Everything else answered, so this is steady rather than shaky. We check every 15 minutes, which is how a one-off gets told apart from the start of a pattern, and how you hear about the next one within the hour instead of from your users.
Connect this server
Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 0 min ago.
run in your terminal
claude mcp add sales-agent --transport http https://leadproof.jessesay.chatgpt.site/api/mcpSettings → Connectors → Add custom connector, then paste this address
https://leadproof.jessesay.chatgpt.site/api/mcp~/.codex/config.toml
[mcp_servers.sales-agent]
url = "https://leadproof.jessesay.chatgpt.site/api/mcp".cursor/mcp.json
{
"mcpServers": {
"sales-agent": {
"url": "https://leadproof.jessesay.chatgpt.site/api/mcp"
}
}
}.vscode/mcp.json
{
"servers": {
"sales-agent": {
"type": "http",
"url": "https://leadproof.jessesay.chatgpt.site/api/mcp"
}
}
}Available tools 11
Read directly from the server with tools/list, grouped by what they act on.
If a tool disappears, we record the date.
leadproof
get_leadproof_checkout
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.
get_leadproof_evaluation_path
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.
get_leadproof_evidence
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.
get_leadproof_integration
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.
get_leadproof_plan_decision
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.
get_leadproof_replay_trial
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.
get_leadproof_trial
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.
audit
audit_lead_workflow
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.
compare
compare_leadproof_vs_in_house
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.
evaluate
evaluate_leadproof_fit
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.
request
request_leadproof_handoff
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.
Endpoints
| URL | Transport | State | Latency | Checked |
|---|---|---|---|---|
| https://leadproof.jessesay.chatgpt.site/api/mcp | streamable-http | answering | 1053 ms | 0 min ago |
Alternatives to LeadProof Sales Agent
same job, measured the same wayFlurryPORT
by flurryport
Webhook capture and replay, delivery pipes, and signed multi-agent rooms. No signup to start.
Agent Placement Trial
by sadri-dridi
Start a 7-day placement trial: card on file, cancel anytime, measured agent hops.
SolarDialer
by solardialer
AI dialer: add and find leads, list campaigns, and have the AI agent call a lead now.
botx402
by botx402
Inventory reorder plans from SKU sales, stock and lead times. $19 a run, paid by card.
Hamster
by gethamster
Search and manage Hamster briefs, tasks, plans, and knowledge; trigger delivery from your agent.
X402 Receipt Verifier
by nexus-mcp-infra
Audits NEXUS's own x402 payment logs against its own delivery logs and issues a signed proof-of-deli
Cascade Scout
by runscout
Shared team record of decisions, changes and handoffs that every coding agent reads and writes.
Simscout
by cloudcorprecords
Compare travel eSIM plans by country, trip length and data, with live catalog prices.
LeadProof Sales Agent — questions
Answers built from our own checks of this server.
What can LeadProof Sales Agent do?
It exposes 11 tools, read directly from the server on our last check. Among them: audit_lead_workflow, compare_leadproof_vs_in_house, evaluate_leadproof_fit, get_leadproof_checkout, get_leadproof_evaluation_path, get_leadproof_evidence and 5 more. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README.
How MCP servers expose tools in the first place →
Is LeadProof Sales Agent working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 92 of 92 checks got a reply (100.0%), average response time 714 ms. The bar chart above shows every period we have measured.
How do I connect LeadProof Sales Agent?
Copy the ready config from this page. We generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each in the form that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.
Does LeadProof Sales Agent need an API key?
No. LeadProof Sales Agent completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 11 of them are readable on this page. This is what we observed, not what the docs claim.
How fast is LeadProof Sales Agent?
It answers our handshake in 714 ms on average, which is faster than 12% of all working MCP servers we measure. That is on the slow side — worth knowing if the tool sits inside an interactive loop. The comparison comes from our own checks across the whole registry, every 15 minutes.