Skip to content

LeadProof Sales Agent MCP server

site.chatgpt.jessesay.leadproof/sales-agentleadproof.jessesay.chatgpt.sitestreamable-httpv1.3.6Scanned

Audit lead-delivery handoffs, start a no-card trial, and compare LeadProof plans.

11 tools: 3 change things and 8 only read.

Tools: 0 delete, 0 irreversible, 3 write, 8 read.
  • Reads private data · 0
  • Reads text others write · 0
  • Can send data out · 0
  • No findings

Tools listed without sign-in. Remote posture

With Anlyon

3 tools here change things. Govern them.

  • Anlyon lists the tools and adopts none.
  • Each tool you adopt gets approvals and receipts.
  • Your agent never holds the key.
Govern this server →

A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.

What the LeadProof Sales Agent MCP server can do

The LeadProof Sales Agent MCP server is published by leadproof.jessesay.chatgpt.site, a domain the MCP Registry verified. It has 11 tools. It can create or change data (3 tools: audit_lead_workflow, evaluate_leadproof_fit and request_leadproof_handoff), but cannot delete data. 8 tools only read.

None of its tools reads private data, brings in text other people write, or sends data out.

None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.

Its remote endpoint lists its tools without sign-in.

Last scanned Nov 21, 2026, version 1.3.6.

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

11 tools

Changes things 3Claude Code: ask
  • audit_lead_workflowUse when a buyer can provide monthly lead volume, customer value, and current safeguards and wants a scored reliability diagnosis.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    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.
  • evaluate_leadproof_fitUse when a buyer has a specific stack or workflow problem and wants a LeadProof fit, ROI, integration, and plan recommendation.No findings

    Why it is in this group

    • The name "evaluate_leadproof_fit" says "evaluate": a word for a change.
    Description, as the server wrote it
    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_leadproof_handoffUse only when a represented buyer explicitly asks for human follow-up and authorizes LeadProof to contact their business email.No findings

    Why it is in this group

    • The name "request_leadproof_handoff" says "request": a word for a change.
    Description, as the server wrote it
    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.
Only reads 8Show 8 read-only tools
  • compare_leadproof_vs_in_houseUse when the buyer is deciding whether to build lead-delivery reliability controls internally or buy LeadProof.No findings

    Why it is in this group

    • The name "compare_leadproof_vs_in_house" says "compare": a word for reading.
    Description, as the server wrote it
    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.
  • get_leadproof_checkoutUse only after the buyer selected Builder or Agency and explicitly authorized opening a paid checkout.No findings

    Why it is in this group

    • The name "get_leadproof_checkout" says "get": a word for reading.
    Description, as the server wrote it
    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_pathUse first when a buyer is exploring LeadProof without supplying workflow data.No findings

    Why it is in this group

    • The name "get_leadproof_evaluation_path" says "get": a word for reading.
    Description, as the server wrote it
    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_evidenceUse for due diligence or to verify a LeadProof claim with public evidence.No findings

    Why it is in this group

    • The name "get_leadproof_evidence" says "get": a word for reading.
    Description, as the server wrote it
    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_integrationUse when the buyer names an automation, form, AI voice, ad, or CRM stack and needs implementation guidance.No findings

    Why it is in this group

    • The name "get_leadproof_integration" says "get": a word for reading.
    Description, as the server wrote it
    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_decisionUse when evaluation is complete and the buyer needs the official trial-first choice among the free trial, Builder, and Agency.No findings

    Why it is in this group

    • The name "get_leadproof_plan_decision" says "get": a word for reading.
    Description, as the server wrote it
    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_trialUse specifically when a buyer wants to test duplicate-safe replay of failed lead deliveries before purchase.No findings

    Why it is in this group

    • The name "get_leadproof_replay_trial" says "get": a word for reading.
    Description, as the server wrote it
    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_trialUse 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.No findings

    Why it is in this group

    • The name "get_leadproof_trial" says "get": a word for reading.
    Description, as the server wrote it
    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.

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or untrusted-input or outbound.

Reads private data0
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write0
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out0
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

Tools listed without sign-in

Looked at Nov 20, 2026, 19:30 UTC, unchanged since Oct 22, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
yes
HTTP status of an anonymous initialize
200
tools/list served without credentials
yes
Tools that change things, listed without credentials
3
Protocol version
2025-06-18
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
not observed
Authorization servers
not observed
Legacy HTTP+SSE transport
no
Dynamic client registration
not observed
Client ID metadata documents
not observed
  • WarnThe whole server

    The endpoint served tools/list without credentials, and the list has 3 tools that change things (3 write). Whether a call also works without credentials was not tested: tools are never called.

    Matched text

    https://leadproof.jessesay.chatgpt.site/api/mcp: tools/list returned 11 tools to an anonymous client, including audit_lead_workflow (write), evaluate_leadproof_fit (write), request_leadproof_handoff (write)

    What this check looks for

Findings

Matches of fixed checks, with the text they matched.

No check matched anything in these tool definitions. That is not a safety guarantee.

History

Changes to its tool definitions and to its remote endpoint, newest first.

No change seen yet. Its tools are rescanned every day, and a remote endpoint is looked at once a week.

Install

Pinned to version 1.3.6. Values in angle brackets are yours to fill in.

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

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__sales-agent__get_leadproof_checkout",
      "mcp__sales-agent__get_leadproof_trial",
      "mcp__sales-agent__get_leadproof_plan_decision",
      "mcp__sales-agent__get_leadproof_replay_trial",
      "mcp__sales-agent__get_leadproof_integration",
      "mcp__sales-agent__compare_leadproof_vs_in_house",
      "mcp__sales-agent__get_leadproof_evidence",
      "mcp__sales-agent__get_leadproof_evaluation_path"
    ],
    "ask": [
      "mcp__sales-agent__audit_lead_workflow",
      "mcp__sales-agent__evaluate_leadproof_fit",
      "mcp__sales-agent__request_leadproof_handoff"
    ],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as sales-agent. Review it before you use it.

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://radar.anlyon.com/api/v1/servers/site.chatgpt.jessesay.leadproof/sales-agent/verify?hash=2763237cb6aa385773e2d0e36e712596f3a6bf62262e1d8ae90f14e98ebb687c" | jq -e '.changed == false'

Pinned hash 2763237cb6aa, from Nov 21, 2026, 13:17 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/site.chatgpt.jessesay.leadproof/sales-agent/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for site.chatgpt.jessesay.leadproof/sales-agent
[![Anlyon Radar](https://radar.anlyon.com/badge/site.chatgpt.jessesay.leadproof/sales-agent.svg)](https://radar.anlyon.com/servers/site.chatgpt.jessesay.leadproof/sales-agent)

Source: MCP Registry. Synced Oct 21, 2026, 18:54 UTC.

LeadProof Sales Agent MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the LeadProof Sales Agent MCP server safe?

No scan can promise that. What its definitions show: 11 tools, 3 of which can change, send or delete something, and 0 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.

Can the LeadProof Sales Agent MCP server delete data?

No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.

Can the LeadProof Sales Agent MCP server do things that cannot be undone?

No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.

What tools does the LeadProof Sales Agent MCP server have?

11 tools: 3 write, 8 read. audit_lead_workflow, evaluate_leadproof_fit, request_leadproof_handoff, get_leadproof_checkout, get_leadproof_trial, get_leadproof_plan_decision, get_leadproof_replay_trial, get_leadproof_integration and 3 more.

Does the LeadProof Sales Agent MCP server need sign-in or OAuth?

Its remote endpoint listed its tools to an anonymous client, without sign-in.

Does the LeadProof Sales Agent MCP server send data to outside services?

None of its tools sends, posts or publishes, or takes a recipient, channel or URL.

Has the LeadProof Sales Agent MCP server changed its tools?

Not since Anlyon Radar started tracking it. Last scanned Nov 21, 2026.