mcp server
LeadProof Sales Agent
Audit lead-delivery workflows, find reliability gaps, and generate a LeadProof integration plan.
Description as published by the maintainer. Source
- version 1.0.0
- active
- workflow automation
active — Registry entry last updated 2026-07-18. Dashed tags are derived by ZBS Index from the published description, not stated by the maintainer.
What this server can do
11 functions, named and described by the server itself. Parameter names are shown because they say more about what a function does than its name usually does.
audit_lead_workflow(stack, idempotency, retry_policy, monthly_leads, failure_alerts, dead_letter_queue, average_customer_value, destination_verification)- Run a free reliability audit of a lead-delivery workflow. Returns a 0-100 risk score, missing safeguards, transparent revenue-at-risk estimate, integration kit, and authorized checkout path. Required: monthly_leads, average_customer_value.
compare_leadproof_vs_in_house- Return an evidence-based build-versus-buy comparison with the complete public example audit URL, covering retries, idempotency, receipts, replay, privacy, operations, exact LeadProof pricing, honest limitations, and authorized purchase paths.
evaluate_leadproof_fit(stack, monthly_leads, workflow_problem, average_customer_value)- Evaluate whether a lead automation workflow would benefit from LeadProof and return an integration path, transparent ROI estimate, recommended plan, and checkout URL. Required: monthly_leads, average_customer_value.
get_leadproof_checkout(plan)- Return the official Stripe checkout URL for a LeadProof plan. The calling agent must obtain its principal's authorization before payment. Required: plan.
get_leadproof_evaluation_path- Return the official no-purchase evaluation sequence with the buyer guide, fictional example audit, browser-only calculator, public workflow tests, and no-card production trial. It accepts no input and returns no personal or customer data.
get_leadproof_evidence- Return the public LeadProof evidence manifest with live checks, published contracts, buyer protections, and explicit product limitations. It contains no customer records.
get_leadproof_integration(stack)- Match an automation stack against 53 published LeadProof platform guides and return the strongest canonical guide paths, no-card trial, and concise implementation steps. Required: stack.
get_leadproof_plan_decision- Return the official ordered LeadProof plan decision: no-card production trial first, then exact Builder or Agency checkout only after human or principal purchase authorization. It accepts no input and returns no personal or customer data.
get_leadproof_replay_trial- Return the public replay procedure, fictional example audit, exact replay requirements, and an attributed no-card production trial. It accepts no input and never authorizes payment.
get_leadproof_trial- Return the official no-card production trial. It includes 25 live lead deliveries for 14 days and requires a verified sign-in, but no payment authorization.
request_leadproof_handoff(name, plan, email, stack, company, monthly_leads, consent_to_contact, average_customer_value)- Create a consent-based sales handoff for a represented buyer. Requires the buyer's name, business email, and explicit authorization to be contacted. Returns the recommended plan and official checkout without authorizing payment. Required: name, email, consent_to_contact.
Last successful function declaration observed on . Source: https://leadproof.jessesay.chatgpt.site/api/mcp. We list what the server declared; we do not call any of these functions.
Endpoint status observed on . Source: https://leadproof.jessesay.chatgpt.site/api/mcp.
Signals
These are separate measurements of different things. They are deliberately not combined into one score, because a popularity number that mixes website traffic with saves and stars cannot be checked or acted on.
| Signal | Value | What it measures | Window | Observed | Source |
|---|---|---|---|---|---|
| Latest published version | 1.0.0 | Latest version string the maintainer published to the registry. | as of fetch | Model Context Protocol | |
| Registry record last updated | 2026-07-18 | When the registry record was last updated by its maintainer. | point in time | Model Context Protocol | |
| First listed in the MCP Registry | 2026-07-18 | Date this server was first published to the official MCP Registry. Not a usage or quality measure. | point in time | Model Context Protocol | |
| mcp tools declared | 11 tools | Number of functions the server itself declared when asked to list them. This is what the server offers an agent, not a measure of how well any of them work. | as of probe | leadproof.jessesay.chatgpt.site | |
| mcp endpoint status | ok | The server listed 11 functions when asked. | as of probe | leadproof.jessesay.chatgpt.site |
Where to get it
This record as data
Every field on this page, with its source and observation date, is in the catalog JSON. Fetch the whole kind at once instead of parsing this HTML.
GET /api/v1/entries/mcp_server.json