LeadProof Sales Agent

site.chatgpt.jessesay.leadproofPublished by leadproof.jessesay.chatgpt.siteOfficial publisherv1.3.6Updated Oct 25, 2026

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

VerifiedStreamable HTTPWeb executableData & AnalyticsBusiness & Commerce

Overview

AI-generated overview

A remote sales-assistant server that audits lead-delivery workflows, recommends LeadProof plans, and guides buyers to trials, checkout, or human handoff.

What you can do
Audit a lead workflow and get a 0-100 risk score, missing safeguards, and revenue-at-risk estimate, or evaluate LeadProof fit and ROI for a specific stack or problem line by line. Compare buying LeadProof against building controls in-house, and pull public evidence, contracts, and limitations for due diligence. Get the official evaluation path, standard no-card trial, or duplicate-safe replay trial details. Retrieve integration guidance matched against published platform guides. Get plan boundaries and a Stripe checkout link, or create a consent-based sales handoff when the buyer explicitly asks for human follow-up.
When to use it
Useful when a buyer is evaluating LeadProof or lead-delivery reliability tooling and wants a scored diagnosis, plan comparison, integration guidance, trial details, or public evidence before deciding. Also suited to sales conversations where the assistant should walk a prospect through options without completing payment.
Requirements
Remote streamable HTTP endpoint; no packages, environment variables, or headers declared. No authentication is declared, though the tools describe buyer authorization and consent steps before checkout or handoff.
Before you install
Tools can return a Stripe checkout link and create a sales handoff that contacts the buyer's business email, so only proceed after explicit buyer authorization. Workflow metrics such as lead volume and customer value are sent to the remote service. The server never completes payment itself, but checkout leads to a paid plan.

Installation

In SourceWeft

  1. Open LeadProof Sales Agent in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/site.chatgpt.jessesay.leadproof%2Fsales-agent/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

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

Tools

11

audit_lead_workflow

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, 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.

Parametersstackidempotencyretry_policymonthly_leadsrequiredfailure_alertsdead_letter_queueaverage_customer_valuerequireddestination_verification

evaluate_leadproof_fit

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, use audit_lead_workflow instead; for installation guidance only, use get_leadproof_integration; for general exploration without workflow data, use get_leadproof_evaluation_path.

Parametersstackmonthly_leadsrequiredworkflow_problemaverage_customer_valuerequired

get_leadproof_checkout

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 authorizes or completes payment. If the buyer has not evaluated the product, use get_leadproof_trial or get_leadproof_plan_decision first.

Parametersplanrequired

get_leadproof_trial

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

Takes no parameters.

get_leadproof_plan_decision

Get Trial-First 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 permits paid checkout only after human or principal authorization. Do not use for workflow diagnosis; use audit_lead_workflow or evaluate_leadproof_fit instead.

Takes no parameters.

get_leadproof_replay_trial

Test Failed-Lead Replay Before Purchase

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.

Takes no parameters.

request_leadproof_handoff

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 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.

Parametersnamerequiredplanemailrequiredstackcompanymonthly_leadsconsent_to_contactrequiredaverage_customer_value

get_leadproof_integration

Get Integration Instructions

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.

Parametersstackrequired

compare_leadproof_vs_in_house

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 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.

Takes no parameters.

get_leadproof_evidence

Get LeadProof Product Evidence

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.

Takes no parameters.

get_leadproof_evaluation_path

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, 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.

Takes no parameters.

Version history

2
  1. v1.3.6LatestOct 1, 2026
  2. v1.0.0Sep 16, 2026

Score

72% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listedRequired15 pts
  • DescriptionRequired15 pts
  • Logo10 pts

    Publish an icon in the registry entry.

  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.