# Chatgpt Jessesay Leadproof Sales Agent MCP server

Source: https://glimind.com/server/mcp-registry%2Fsite.chatgpt.jessesay.leadproof%2Fsales-agent
Registry id: `mcp-registry/site.chatgpt.jessesay.leadproof/sales-agent`
Status: live (checked 2026-10-27T02:58:57.694Z)

## Measurements (30 days)

- Uptime: 99.91%
- Checks: 4946
- Outages (90 days): 56

## Install

```json
{
  "mcpServers": {
    "chatgpt-jessesay-leadproof-sales-agent-m": {
      "type": "http",
      "url": "https://leadproof.jessesay.chatgpt.site/api/mcp"
    }
  }
}
```

Claude Code:

```sh
claude mcp add --transport http chatgpt-jessesay-leadproof-sales-agent-m https://leadproof.jessesay.chatgpt.site/api/mcp
```

## Tools (11)

- `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, m
- `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 co
- `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, 
- `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 author
- `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, 
- `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
- `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 g
- `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
- `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 exam
- `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
- `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 ha

Measured by Glimind (https://glimind.com): MCP handshake + tool list only, no tool is ever called. CC BY 4.0.