LeadProof MCP MCP server

An automated agent that audits lead-delivery handoffs, evaluates risk, compares integration stacks, and facilitates no-card trials for the LeadProof product.

Endpoint and access

No sign-in: your client connects and lists tools immediately, with no account or key.

No sign-inEndpoint checked 2026-10-05Operated by LeadProof

MCP endpoint (Streamable HTTP)

https://leadproof.jessesay.chatgpt.site/api/mcp

Vendor documentation

What you can do with it

Audit lead workflow reliability and risk scores
Compare build versus buy integration options
Request no-card production trials
Verify product evidence and plans

Tools advertised by the last live check:

audit_lead_workflow
evaluate_leadproof_fit
get_leadproof_checkout
get_leadproof_trial
get_leadproof_plan_decision
get_leadproof_replay_trial
request_leadproof_handoff
get_leadproof_integration
compare_leadproof_vs_in_house
get_leadproof_evidence
get_leadproof_evaluation_path

Connect from your client

Each snippet registers the same endpoint; pick the client you use.

This server is operated by the named third party. Listing and endpoint checks are not an endorsement or a security audit. Review the operator's permissions, terms, and data handling before connecting. How listings are checked and corrected.

Claude Code

Run this once in a terminal. It registers a Streamable HTTP server. Use --scope project to write .mcp.json for the repo.

Claude Code configuration

claude mcp add --transport http leadproof-mcp-chatgpt https://leadproof.jessesay.chatgpt.site/api/mcp

Codex

Run this once. Codex stores MCP servers in ~/.codex/config.toml (or .codex/config.toml in a trusted project).

Codex configuration

codex mcp add leadproof-mcp-chatgpt --url https://leadproof.jessesay.chatgpt.site/api/mcp

Cursor

Merge this server into .cursor/mcp.json in your project, then enable leadproof-mcp-chatgpt in your MCP settings.

Cursor configuration

{
  "mcpServers": {
    "leadproof-mcp-chatgpt": {
      "url": "https://leadproof.jessesay.chatgpt.site/api/mcp"
    }
  }
}

Cline

Merge this into cline_mcp_settings.json (Cline → MCP Servers → Configure). The type must be streamableHttp for a remote HTTP server.

Cline configuration

{
  "mcpServers": {
    "leadproof-mcp-chatgpt": {
      "type": "streamableHttp",
      "url": "https://leadproof.jessesay.chatgpt.site/api/mcp",
      "disabled": false
    }
  }
}

VS Code

Merge this server into .vscode/mcp.json. Use MCP: List Servers to start leadproof-mcp-chatgpt and inspect its tools.

VS Code configuration

{
  "servers": {
    "leadproof-mcp-chatgpt": {
      "type": "http",
      "url": "https://leadproof.jessesay.chatgpt.site/api/mcp"
    }
  }
}

Gemini CLI

Run this once. It writes .gemini/settings.json in the current project; pass --scope user for ~/.gemini/settings.json.

Gemini CLI configuration

gemini mcp add --transport http leadproof-mcp-chatgpt https://leadproof.jessesay.chatgpt.site/api/mcp

Claude Desktop

Merge this into claude_desktop_config.json (macOS: ~/Library/Application Support/Claude/, Windows: %APPDATA%\Claude\), then restart Claude Desktop.

Claude Desktop configuration

{
  "mcpServers": {
    "leadproof-mcp-chatgpt": {
      "url": "https://leadproof.jessesay.chatgpt.site/api/mcp"
    }
  }
}

Windsurf

Merge this into ~/.codeium/windsurf/mcp_config.json, then refresh MCP in Cascade. Windsurf remote servers use serverUrl, not url.

Windsurf configuration

{
  "mcpServers": {
    "leadproof-mcp-chatgpt": {
      "serverUrl": "https://leadproof.jessesay.chatgpt.site/api/mcp"
    }
  }
}

See all 347

Do you run LeadProof MCP?

Prove ownership with a DNS record, a well-known file, or your Official MCP Registry entry, and your edits publish immediately. Proofs are re-checked weekly; admins can still hide or remove a listing.

Claim this listing