LeadProof Sales Agent

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

¿Debería usar esto?

Calidad y seguridad

A
Calidad de la descripción
100%
Integridad del esquema
56%
Calidad de los nombres
96%
Riesgo de envenenamiento
100%
Coincidencia de permisos
100%
Cumplimiento del protocolo
100%

Basado en el análisis automatizado de las definiciones de herramientas y el cumplimiento del protocolo.

Costo de contexto

~1,331Tokens (definiciones de herramientas)
~496 BTamaño de respuesta típico
Impacto moderado en la atención (1.04% del contexto de 128k)

Este es el número aproximado de tokens que se consumen cada vez que las herramientas del servidor se cargan en el contexto de un modelo. Los recuentos más altos reducen la atención disponible para otras tareas.

Instalar

Instalación con un clic

Agrega esto a tu archivo `claude_desktop_config.json`:

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

Puntos de conexión remotos

https://leadproof.jessesay.chatgpt.site/api/mcpstreamable-http

Qué puede hacer

Inventario de herramientas

Herramientas (11)

🟢 Solo lectura🟡 Escritura🔴 Eliminación⚪ Desconocido
🟢audit_lead_workflow(stack, monthly_leads, average_customer_value, retry_policy, idempotency, ...)

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.

Esquema de entrada

{
  "type": "object",
  "properties": {
    "stack": {
      "type": "string"
    },
    "monthly_leads": {
      "type": "number",
      "minimum": 0
    },
    "average_customer_value": {
      "type": "number",
      "minimum": 0
    },
    "retry_policy": {
      "type": "boolean"
    },
    "idempotency": {
      "type": "boolean"
    },
    "destination_verification": {
      "type": "boolean"
    },
    "failure_alerts": {
      "type": "boolean"
    },
    "dead_letter_queue": {
      "type": "boolean"
    }
  },
  "required": [
    "monthly_leads",
    "average_customer_value"
  ]
}
🟢evaluate_leadproof_fit(stack, monthly_leads, average_customer_value, workflow_problem)

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.

Esquema de entrada

{
  "type": "object",
  "properties": {
    "stack": {
      "type": "string",
      "description": "Current automation or CRM stack, such as GoHighLevel, Make, Zapier, n8n, or a custom API."
    },
    "monthly_leads": {
      "type": "number",
      "minimum": 0
    },
    "average_customer_value": {
      "type": "number",
      "minimum": 0
    },
    "workflow_problem": {
      "type": "string"
    }
  },
  "required": [
    "monthly_leads",
    "average_customer_value"
  ]
}
🟢get_leadproof_checkout(plan)

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.

Esquema de entrada

{
  "type": "object",
  "properties": {
    "plan": {
      "type": "string",
      "enum": [
        "builder",
        "agency"
      ]
    }
  },
  "required": [
    "plan"
  ]
}
🟢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 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.

Esquema de entrada

{
  "type": "object",
  "properties": {}
}
🟢get_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 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.

Esquema de entrada

{
  "type": "object",
  "properties": {}
}
🟢get_leadproof_replay_trial

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.

Esquema de entrada

{
  "type": "object",
  "properties": {}
}
🟢request_leadproof_handoff(name, email, company, stack, monthly_leads, ...)

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.

Esquema de entrada

{
  "type": "object",
  "properties": {
    "name": {
      "type": "string",
      "description": "Name of the represented buyer."
    },
    "email": {
      "type": "string",
      "description": "Business email authorized for LeadProof follow-up."
    },
    "company": {
      "type": "string"
    },
    "stack": {
      "type": "string"
    },
    "monthly_leads": {
      "type": "number",
      "minimum": 0
    },
    "average_customer_value": {
      "type": "number",
      "minimum": 0
    },
    "plan": {
      "type": "string",
      "enum": [
        "builder",
        "agency"
      ]
    },
    "consent_to_contact": {
      "type": "boolean",
      "description": "Must be true only after the represented buyer authorizes contact."
    }
  },
  "required": [
    "name",
    "email",
    "consent_to_contact"
  ]
}
🟢get_leadproof_integration(stack)

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.

Esquema de entrada

{
  "type": "object",
  "properties": {
    "stack": {
      "type": "string",
      "description": "Automation, form, AI voice, ad, or CRM stack to match against public LeadProof guides."
    }
  },
  "required": [
    "stack"
  ]
}
⚪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.

Esquema de entrada

{
  "type": "object",
  "properties": {}
}
🟢get_leadproof_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.

Esquema de entrada

{
  "type": "object",
  "properties": {}
}
🟢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.

Esquema de entrada

{
  "type": "object",
  "properties": {}
}

Prompts recomendados

retrieve_data
Get details about [item] from LeadProof Sales Agent
Herramientas esperadas: get_leadproof_checkout
fetch_info
Fetch [information type] using LeadProof Sales Agent
Herramientas esperadas: get_leadproof_checkout

Comunidad

Califica este servidor

Evidencia

Observaciones recientes

verificadoversión no registrada11 herramientas
verificadoversión no registrada11 herramientas