# LeadProof Sales Agent (remote · leadproof.jessesay.chatgpt.site)

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

- Trust score: 62/100 (medium)
- Change this week: +6
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-08-03

## Components

- remote · `leadproof.jessesay.chatgpt.site`: 62/100 (this document), [markdown](https://verifymcp.io/servers/site-chatgpt-jessesay-leadproof-sales-agent/api-mcp.md), [page](https://verifymcp.io/servers/site-chatgpt-jessesay-leadproof-sales-agent/api-mcp)

## Channel facts

- Endpoint: `https://leadproof.jessesay.chatgpt.site/api/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.0`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-08-03.

- **Endpoint Security**: 57/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation not fully verified: no authorisation is required to call this server, and 10 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.
  - HTTPS is enforced; there's no plaintext access path.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 66/100
  - AI-judged instruction clarity (good).
  - Tool/resource definitions use about 742 tokens (~74/item across 10 items; 10 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 27/100
  - Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 74/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 23% of tool parameters carry a description.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### Claude

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

### Codex

```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
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add site-chatgpt-jessesay-leadproof-sales-agent --url https://leadproof.jessesay.chatgpt.site/api/mcp --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  site-chatgpt-jessesay-leadproof-sales-agent:
    url: "https://leadproof.jessesay.chatgpt.site/api/mcp"
```

### Other

```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 recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-08-03 (score 62, +1)

- [functional] Schema quality: fair → good
- [functional] New tool “get_leadproof_replay_trial”

### 2026-08-02 (score 61, +1)

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

### 2026-07-31 (score 60, +2)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-30 (score 58, +1)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-29 (score 57, 0)

- [security] Tool “compare_leadproof_vs_in_house” 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
- [functional regression] Schema quality: 633 → 697
- [functional] New tool “get_leadproof_evaluation_path”

### 2026-07-28 (score 57, +1)

- [security] Tool “get_leadproof_integration” rewrote its description, which is the text the model reads

### 2026-07-27 (score 56, +1)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-26 (score 55)

First indexed and scored.

## MCP tools (10)

### `audit_lead_workflow` (~118 tokens)

Audit Lead Workflow

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.

Input parameters:

- `average_customer_value` (number, required)
- `dead_letter_queue` (boolean)
- `destination_verification` (boolean)
- `failure_alerts` (boolean)
- `idempotency` (boolean)
- `monthly_leads` (number, required)
- `retry_policy` (boolean)
- `stack` (string)

### `evaluate_leadproof_fit` (~97 tokens)

Evaluate LeadProof Fit

Evaluate whether a lead automation workflow would benefit from LeadProof and return an integration path, transparent ROI estimate, recommended plan, and checkout URL.

Input parameters:

- `average_customer_value` (number, required)
- `monthly_leads` (number, required)
- `stack` (string): Current automation or CRM stack, such as GoHighLevel, Make, Zapier, n8n, or a custom API.
- `workflow_problem` (string)

### `get_leadproof_checkout` (~42 tokens)

Get LeadProof Checkout

Return the official Stripe checkout URL for a LeadProof plan. The calling agent must obtain its principal's authorization before payment.

Input parameters:

- `plan` (string, required)

### `get_leadproof_trial` (~42 tokens)

Get LeadProof Free 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.

### `get_leadproof_replay_trial` (~45 tokens)

Test Failed-Lead Replay Before Purchase

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.

### `request_leadproof_handoff` (~138 tokens)

Request LeadProof Handoff

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.

Input parameters:

- `average_customer_value` (number)
- `company` (string)
- `consent_to_contact` (boolean, required): Must be true only after the represented buyer authorizes contact.
- `email` (string, required): Business email authorized for LeadProof follow-up.
- `monthly_leads` (number)
- `name` (string, required): Name of the represented buyer.
- `plan` (string)
- `stack` (string)

### `get_leadproof_integration` (~67 tokens)

Get Integration Instructions

Match an automation stack against 51 published LeadProof platform guides and return the strongest canonical guide paths, no-card trial, and concise implementation steps.

Input parameters:

- `stack` (string, required): Automation, form, AI voice, ad, or CRM stack to match against public LeadProof guides.

### `compare_leadproof_vs_in_house` (~58 tokens)

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.

### `get_leadproof_evidence` (~40 tokens)

Get LeadProof Product 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_evaluation_path` (~56 tokens)

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.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/site-chatgpt-jessesay-leadproof-sales-agent/api-mcp#diagnostics

## Score history

- 2026-08-03: 62
- 2026-08-02: 61
- 2026-08-01: 60
- 2026-07-31: 60
- 2026-07-30: 58
- 2026-07-29: 57
- 2026-07-28: 57
- 2026-07-27: 56
- 2026-07-26: 55

## Links

- Remote endpoint: https://leadproof.jessesay.chatgpt.site/api/mcp
- Website: https://leadproof.jessesay.chatgpt.site/agent
- Changelog RSS feed: https://verifymcp.io/servers/site-chatgpt-jessesay-leadproof-sales-agent/api-mcp/changelog.xml
- Changelog JSON feed: https://verifymcp.io/servers/site-chatgpt-jessesay-leadproof-sales-agent/api-mcp/changelog.json
- HTML version of this page: https://verifymcp.io/servers/site-chatgpt-jessesay-leadproof-sales-agent/api-mcp