Categories › Productivity & Office › Project & task management
Audit lead-delivery handoffs, start a no-card trial, and compare LeadProof plans.
Remote server: your requests and data go to leadproof.jessesay.chatgpt.site. Claude Code: claude mcp add --transport http leadproof-sales-agent https://leadproof.jessesay.chatgpt.site/api/mcp · Claude app: Settings → Connectors → Add custom connector.
The tools this server listed when we connected to it, in its own words.
audit_lead_workflow — Use when a buyer can provide monthly lead volume, customer value, and current safeguards and wants a scored reliability diagnosis. Returns aevaluate_leadproof_fit — Use when a buyer has a specific stack or workflow problem and wants a LeadProof fit, ROI, integration, and plan recommendation. For detailedget_leadproof_checkout — Use only after the buyer selected Builder or Agency and explicitly authorized opening a paid checkout. Returns the official Stripe checkout 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 pget_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 exactget_leadproof_replay_trial — Use specifically when a buyer wants to test duplicate-safe replay of failed lead deliveries before purchase. Returns the public replay procerequest_leadproof_handoff — Use only when a represented buyer explicitly asks for human follow-up and authorizes LeadProof to contact their business email. Creates a coget_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 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 coget_leadproof_evidence — Use for due diligence or to verify a LeadProof claim with public evidence. Returns live checks, published contracts, buyer protections, and get_leadproof_evaluation_path — Use first when a buyer is exploring LeadProof without supplying workflow data. Returns the official no-purchase sequence: buyer guide, fictiNot tested by KitScout yet. When our harness runs it, pros, cons and the tasks we tried appear here, with the date and evidence.