LeadProof Sales Agent
REMOTE · LEADPROOF.JESSESAY.CHATGPT.SITE · SCANNED AUG 3
Audit lead-delivery workflows, find reliability gaps, and generate a LeadProof integration plan.
Available components
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. How we score →
Endpoint Security57
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- 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. See how to fix → View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability66
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 742 tokens (~74/item across 10 items; 10 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management27
- Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage74
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 23% of tool parameters carry a description.Partial
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.
remote · leadproof.jessesay.chatgpt.site
claude mcp add --transport http site-chatgpt-jessesay-leadproof-sales-agent https://leadproof.jessesay.chatgpt.site/api/mcp
[mcp_servers.site-chatgpt-jessesay-leadproof-sales-agent] url = "https://leadproof.jessesay.chatgpt.site/api/mcp"
{
"$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 mcp add site-chatgpt-jessesay-leadproof-sales-agent --url https://leadproof.jessesay.chatgpt.site/api/mcp --transport streamable-http
mcp_servers:
site-chatgpt-jessesay-leadproof-sales-agent:
url: "https://leadproof.jessesay.chatgpt.site/api/mcp" {
"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.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 3 Aug 26 +1
- Schema quality: fair → good functional
- New tool “get_leadproof_replay_trial” functional
- 2 Aug 26 +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.
- 31 Jul 26 +2
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 30 Jul 26 +1
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 29 Jul 26 0
- 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 security
- Schema quality: 633 → 697 ▼ functional
- New tool “get_leadproof_evaluation_path” functional
- 28 Jul 26 +1
- Tool “get_leadproof_integration” rewrote its description, which is the text the model reads security
- 27 Jul 26 +1
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 26 Jul 26 55
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 3 Aug 2026 · Probed https://leadproof.jessesay.chatgpt.site/api/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=*.jessesay.chatgpt.site | CN=WE1,O=Google Trust Services,C=US | 18 Jul 2026 | 16 Oct 2026 | ECDSA 256 | ECDSA-SHA256 | c39216d6c3014e2613e22835c1445635 |
| SANs: *.jessesay.chatgpt.site | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
DNSSEC insecure
Validation of leadproof.jessesay.chatgpt.site. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| site. | present | 31826 | 13 | Verified |
| chatgpt.site. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| x-content-type-options | nosniff |
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://leadproof.jessesay.chatgpt.site/api/mcp | Verified | 200 | |
| http (plaintext) | http://leadproof.jessesay.chatgpt.site/api/mcp | HTTPS enforced | 302 | https://leadproof.jessesay.chatgpt.site/api/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability.
audit_lead_workflow Audit Lead Workflow ~118
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.
| Name | Type | Req | Description |
|---|---|---|---|
| average_customer_value | number | yes | — |
| dead_letter_queue | boolean | — | — |
| destination_verification | boolean | — | — |
| failure_alerts | boolean | — | — |
| idempotency | boolean | — | — |
| monthly_leads | number | yes | — |
| retry_policy | boolean | — | — |
| stack | string | — | — |
No output schema declared.
No examples provided.
compare_leadproof_vs_in_house Compare LeadProof vs In-House ~58
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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
evaluate_leadproof_fit Evaluate LeadProof Fit ~97
Evaluate whether a lead automation workflow would benefit from LeadProof and return an integration path, transparent ROI estimate, recommended plan, and checkout URL.
| Name | Type | Req | Description |
|---|---|---|---|
| average_customer_value | number | yes | — |
| monthly_leads | number | yes | — |
| stack | string | — | Current automation or CRM stack, such as GoHighLevel, Make, Zapier, n8n, or a custom API. |
| workflow_problem | string | — | — |
No output schema declared.
No examples provided.
get_leadproof_checkout Get LeadProof Checkout ~42
Return the official Stripe checkout URL for a LeadProof plan. The calling agent must obtain its principal's authorization before payment.
| Name | Type | Req | Description |
|---|---|---|---|
| plan | string | yes | — |
No output schema declared.
No examples provided.
get_leadproof_evaluation_path Get LeadProof Evaluation Path ~56
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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_leadproof_evidence Get LeadProof Product Evidence ~40
Return the public LeadProof evidence manifest with live checks, published contracts, buyer protections, and explicit product limitations. It contains no customer records.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_leadproof_integration Get Integration Instructions ~67
Match an automation stack against 51 published LeadProof platform guides and return the strongest canonical guide paths, no-card trial, and concise implementation steps.
| Name | Type | Req | Description |
|---|---|---|---|
| stack | string | yes | Automation, form, AI voice, ad, or CRM stack to match against public LeadProof guides. |
No output schema declared.
No examples provided.
get_leadproof_replay_trial Test Failed-Lead Replay Before Purchase ~45
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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_leadproof_trial Get LeadProof Free Trial ~42
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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
request_leadproof_handoff Request LeadProof Handoff ~138
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.
| Name | Type | Req | Description |
|---|---|---|---|
| average_customer_value | number | — | — |
| company | string | — | — |
| consent_to_contact | boolean | yes | Must be true only after the represented buyer authorizes contact. |
| string | yes | Business email authorized for LeadProof follow-up. | |
| monthly_leads | number | — | — |
| name | string | yes | Name of the represented buyer. |
| plan | string | — | — |
| stack | string | — | — |
No output schema declared.
No examples provided.