accueil / serveurs / IA & Mémoire / site.chatgpt.jessesay.leadproof/sales-agent
site.chatgpt.jessesay.leadproof/sales-agent
serveur MCP (Model Context Protocol) · leadproof-sales-agent 1.3.5
Référencé dans l'annuaire. Seul le pentest comportemental fait foi, et il n'a pas encore été exécuté sur ce serveur.
Est-ce que site.chatgpt.jessesay.leadproof/sales-agent est sûr ?
Au dernier audit MCP Hub, le serveur MCP « site.chatgpt.jessesay.leadproof/sales-agent » est classé « Non encore testé ». Référencé dans l'annuaire. Seul le pentest comportemental fait foi, et il n'a pas encore été exécuté sur ce serveur. Le verdict est réévalué en continu ; consultez la fiche pour l'état à jour.
Méthode : MCP Hub analyse la description de chaque outil (couche 1) et, pour le verdict fort, exécute le serveur dans une micro-VM isolée avec leurres et réseau bloqué (couche 2). On publie des noms et des compteurs, jamais le contenu brut renvoyé par un outil.
Les 11 outils
- audit_lead_workflow≈ 232 tokens
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.
Paramètres, retour & exemple (8)
Paramètresstack· string · optionnelidempotency· boolean · optionnelretry_policy· boolean · optionnelmonthly_leads· number · requisfailure_alerts· boolean · optionneldead_letter_queue· boolean · optionnelaverage_customer_value· number · requisdestination_verification· boolean · optionnel
Exemple d'appel{"name": "audit_lead_workflow", "arguments": {"monthly_leads": 1, "average_customer_value": 1}}Exemple de retour{"content": [{"type": "text", "text": "…"}]} - compare_leadproof_vs_in_house≈ 135 tokens
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.
Paramètres, retour & exemple (0)
Exemple d'appel{"name": "compare_leadproof_vs_in_house", "arguments": {}}Exemple de retour{"content": [{"type": "text", "text": "…"}]} - evaluate_leadproof_fit≈ 205 tokens
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.
Paramètres, retour & exemple (4)
Paramètresstack· string · optionnel
Current automation or CRM stack, such as GoHighLevel, Make, Zapier, n8n, or a custom API.monthly_leads· number · requisworkflow_problem· string · optionnelaverage_customer_value· number · requis
Exemple d'appel{"name": "evaluate_leadproof_fit", "arguments": {"monthly_leads": 1, "average_customer_value": 1}}Exemple de retour{"content": [{"type": "text", "text": "…"}]} - get_leadproof_checkout≈ 128 tokens
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.
Paramètres, retour & exemple (1)
Paramètresplan· string · requis · builder | agency
Exemple d'appel{"name": "get_leadproof_checkout", "arguments": {"plan": "builder"}}Exemple de retour{"content": [{"type": "text", "text": "…"}]} - get_leadproof_evaluation_path≈ 141 tokens
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.
Paramètres, retour & exemple (0)
Exemple d'appel{"name": "get_leadproof_evaluation_path", "arguments": {}}Exemple de retour{"content": [{"type": "text", "text": "…"}]} - get_leadproof_evidence≈ 111 tokens
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.
Paramètres, retour & exemple (0)
Exemple d'appel{"name": "get_leadproof_evidence", "arguments": {}}Exemple de retour{"content": [{"type": "text", "text": "…"}]} - get_leadproof_integration≈ 152 tokens
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.
Paramètres, retour & exemple (1)
Paramètresstack· string · requis
Automation, form, AI voice, ad, or CRM stack to match against public LeadProof guides.
Exemple d'appel{"name": "get_leadproof_integration", "arguments": {"stack": "texte"}}Exemple de retour{"content": [{"type": "text", "text": "…"}]} - get_leadproof_plan_decision≈ 118 tokens
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.
Paramètres, retour & exemple (0)
Exemple d'appel{"name": "get_leadproof_plan_decision", "arguments": {}}Exemple de retour{"content": [{"type": "text", "text": "…"}]} - get_leadproof_replay_trial≈ 132 tokens
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.
Paramètres, retour & exemple (0)
Exemple d'appel{"name": "get_leadproof_replay_trial", "arguments": {}}Exemple de retour{"content": [{"type": "text", "text": "…"}]} - get_leadproof_trial≈ 116 tokens
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.
Paramètres, retour & exemple (0)
Exemple d'appel{"name": "get_leadproof_trial", "arguments": {}}Exemple de retour{"content": [{"type": "text", "text": "…"}]} - request_leadproof_handoff≈ 268 tokens
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.
Paramètres, retour & exemple (8)
Paramètresname· string · requis
Name of the represented buyer.plan· string · optionnel · builder | agencyemail· string · requis
Business email authorized for LeadProof follow-up.stack· string · optionnelcompany· string · optionnelmonthly_leads· number · optionnelconsent_to_contact· boolean · requis
Must be true only after the represented buyer authorizes contact.average_customer_value· number · optionnel
Exemple d'appel{"name": "request_leadproof_handoff", "arguments": {"name": "texte", "email": "texte", "consent_to_contact": true}}Exemple de retour{"content": [{"type": "text", "text": "…"}]}
C'est votre serveur ?
Revendiquez-le sur l'espace créateur (preuve GitHub, domaine ou npm) pour afficher le badge « propriétaire vérifié » et lancer un pentest comportemental à la demande afin d'obtenir le badge « Vérifié ».