Servidor MCP de RingGuard

• Nombre en el registroonline.ringguard/ringguardverificado en el registro MCP

El nombre en el registro está bajo ringguard.online. El registro solo permite usar ese espacio de nombres a quien demuestra control del dominio por DNS o HTTP.

• Estadorespondecomprobado el 2026-10-26
• Herramientas21
• El servidor se llamaringguard
• Versión del servidor1.1.0
• Versión del protocolo2025-06-18

El 2026-10-26 el servidor respondió a initialize y tools/list sin iniciar sesión. Primera respuesta en 107 ms.

• Aún no se ha juzgado si sus herramientas hacen el trabajo del producto.
• Comprobado 2 de los 7 días necesarios para juzgar su fiabilidad.

Lo dicen reglas a partir de las mediciones de arriba. La primera llamada probable la elige un modelo de la lista de herramientas; lee su descripción antes de fiarte.

• Nota INITE MCPtras una semanala nota necesita 7 comprobaciones diarias: 2 hasta ahora
• Respondiómidiendo2 de las 7 comprobaciones diarias necesarias para mostrar el porcentaje
• Mediana de la primera respuesta209 ms
• Espacio en el contexto del agente≈ 3065 tokenslas definiciones de todas sus herramientas (21), que el agente lleva en cada turno
• Definiciones de herramientasB · 89 de 100
• Resultados tipados0 de 21 herramientasdeclaran outputSchema: el resultado llega tipado y se lee de una vez

• Parámetros sin descripción: en 14 de 21

Un programa comprueba el servidor una vez al día: initialize y tools/list, sin modelo. Los tokens son la longitud de las definiciones, a unos cuatro caracteres por token. La nota promedia seis comprobaciones del nombre, la descripción, el esquema y las anotaciones de cada herramienta; dice lo bien descritas que están, no si funcionan. La nota pondera solo lo medido: si responde (25%), si hace el trabajo del producto (25%), definiciones (20%), contexto (10%), uso (10%) y lo fácil que es conectarse (10%). Lo que no se midió queda fuera, y una instrucción oculta limita la nota a 40. El estado de los servidores MCP de los proveedores: método y números →

• what_ringguard_does

  Explains RingGuard, the AI voice receptionist for trade businesses (HVAC, plumbing, roofing, towing): what it does, pricing, how it compares to a receptionist or answering service, and the free Shadow Trial. No sign-in needed.

• missed_call_cost

  Estimate how much revenue a business loses to unanswered calls, from its own call volume and average job value. No sign-in needed. Ask the user for their numbers rather than guessing them.

• ringguard_cost_estimate

  Estimate what RingGuard would cost a business per month from how many calls it would handle, compared with a receptionist and an answering service. No sign-in needed.

• start_shadow_trial

  Sign a business up for RingGuard's free 48-hour Shadow Trial. The RingGuard team follows up by text or call within one business day. Only call this after the person has given their details and explicitly agreed to be contacted and to the…

• my_account

  Who is signed in to RingGuard, and a quick count of their pipeline.

• find_leads

  Search leads you can see: your own plus the unclaimed pool. Filter by name/phone text, status, industry, city or minimum lead score.

• top_leads_to_call

  The best leads to call right now: not yet won or lost, with a phone number, ranked by lead score and how much the open receptionist job is costing them. Includes the suggested cold-call angle.

• lead_details

  Everything about one lead: contact info, pitch (cold-call angle, Shadow Trial pitch, pain points), deal details, call history and notes.

• claim_lead

  Take an unclaimed lead from the shared pool into your own pipeline. Two-step: draft, then confirm.

• add_lead

  Add a new lead to your pipeline. Warns if another visible lead already has the same phone number. Two-step: draft, then confirm.

• update_lead_status

  Move one of your leads to a new pipeline stage. Two-step: draft, then confirm.

• log_call

  Record a call with one of your leads, optionally setting a follow-up. Some outcomes also move the lead's stage (won, trial_started, appointment_booked, not_interested, do_not_call). Two-step: draft, then confirm.

• my_follow_ups

  Your leads with a follow-up due, including overdue ones, soonest first.

• call_history

  Calls logged on one lead, or if no lead is given, the calls you logged in the last N days.

• new_trial_signups

  Businesses that signed up for the free Shadow Trial on ringguard.online and haven't been converted to a lead yet.

• convert_trial_to_lead

  Turn a Shadow Trial signup into a lead in your pipeline at the shadow_trial stage. Two-step: draft, then confirm.

• pipeline_report

  Snapshot of your pipeline: leads by stage, won deals and monthly recurring revenue, follow-ups due, the unclaimed pool and open trial signups.

• my_stats

  Your call activity over the last N days: totals by outcome, conversations, trials started and wins.

• team_leaderboard

  Owner only. Call activity per rep over the last N days, ranked by conversations.

• lead_gen_status

  Health of the automated lead-gen pipeline (job postings → AI enrichment → unclaimed pool, runs every 4 hours): when it last delivered leads and how many.

• undo_last_change

  Reverse the most recent change you made through Claude (claim, new lead, status change, logged call or trial conversion). Two-step: draft, then confirm.