RingGuard — AI Receptionist for Trade Businesses
REMOTE · RINGGUARD.ONLINE
Missed-call cost, AI receptionist pricing and free trial signup; CRM tools for RingGuard sales reps
Available components
Last scanned (10 hours ago)
Scores higher than 98% of remote servers
Reachable. Last reached 5 Nov 2026.
Category CRM and Sales
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 → Why this is hard to score →
Endpoint Security94
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation is enforced on tool calls, advertised via RFC 9728 protected-resource metadata. Discovery is public, which costs nothing: no tool can be invoked without a token. View diagnostics → Pass
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
- The authorisation server offers only Dynamic Client Registration (RFC 7591), which MCP 2026-07-28 deprecated in favour of Client ID Metadata Documents. View diagnostics → Partial
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability75
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 1766 tokens (~84/item across 21 items; 21 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management97
- Stability observed for 29 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage77
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 32% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 21 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 22 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
Checks we ran (13)
- TLS certificate
- Authorization
- HTTPS
- HSTS header
- DNSSEC
- Transport
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Does not apply to this hosted endpoint (2)
- Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
- Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
The score does not measure everything. What the score does not measure →
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.
- 5 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 3 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.
- 1 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.
- 30 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 73 to 77. That category is still filling its 30-day observation window: 22 days of observed history at the previous scan, 23 at this one. The score rises as the window fills, whether or not the server changes.
- 27 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 63 to 67. That category is still filling its 30-day observation window: 19 days of observed history at the previous scan, 20 at this one. The score rises as the window fills, whether or not the server changes.
- 25 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 57 to 60. That category is still filling its 30-day observation window: 17 days of observed history at the previous scan, 18 at this one. The score rises as the window fills, whether or not the server changes.
- 23 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 50 to 53. That category is still filling its 30-day observation window: 15 days of observed history at the previous scan, 16 at this one. The score rises as the window fills, whether or not the server changes.
- 21 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 43 to 47. That category is still filling its 30-day observation window: 13 days of observed history at the previous scan, 14 at this one. The score rises as the window fills, whether or not the server changes.
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 5 Nov 2026 · Probed https://ringguard.online/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=ringguard.online | CN=YR1,O=Let's Encrypt,C=US | 22 Oct 2026 | 20 Jan 2027 | RSA 2048 | SHA256-RSA | 630816b73884004a69617a11e491b78fa7e |
| SANs: ringguard.online | ||||||
| CN=YR1,O=Let's Encrypt,C=US (CA) | CN=Root YR,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | RSA 2048 | SHA256-RSA | a20253f15f2691c05dc1ce13b9bcca4e |
| CN=Root YR,O=ISRG,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | RSA 4096 | SHA256-RSA | f24b6d17f9d9ad7cb1c9fea78782699f |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of ringguard.online. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| online. | DS published | 30961 | 13 | Verified |
| ringguard.online. | No DS | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Enforced and verified
The endpoint asked for a token and published valid RFC 9728 metadata describing how to get one.
| Result | Enforced and verified |
|---|---|
| Enforced | On tool calls |
| HTTP status | 200 |
WWW-Authenticate challenge Bearer error="invalid_token", error_description="No authorization provided", resource_metadata="https://ringguard.online/.well-known/oauth-protected-resource/mcp"
Bearer error="invalid_token", error_description="No authorization provided", resource_metadata="https://ringguard.online/.well-known/oauth-protected-resource/mcp"| Header | Value |
|---|---|
| strict-transport-security | max-age=63072000 |
Protected resource metadata
| Document | https://ringguard.online/.well-known/oauth-protected-resource/mcp |
|---|---|
| Retrieved | Yes |
| Resource | https://ringguard.online/mcp |
| Authorisation server | https://wwqptyjwvpxsssuhnizr.supabase.co/auth/v1 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://ringguard.online/mcp | Verified | 200 | |
| http (plaintext) | http://ringguard.online/mcp | HTTPS enforced | 308 | https://ringguard.online/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. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
add_lead Add a lead ~126
Add a new lead to your pipeline. Warns if another visible lead already has the same phone number. Two-step: draft, then confirm.
| Name | Type | Req | Description |
|---|---|---|---|
| business_name | string | yes | – |
| city | string | – | – |
| confirm | boolean | – | Leave false to get a draft of the change. Only set true after the user has seen the draft and approved it. |
| contact_name | string | – | – |
| string | – | – | |
| industry | string | – | – |
| notes | string | – | – |
| phone | string | yes | – |
| state | string | – | – |
No output schema declared.
No examples provided.
call_history Call history ~53
Calls logged on one lead, or if no lead is given, the calls you logged in the last N days.
| Name | Type | Req | Description |
|---|---|---|---|
| days | integer | – | – |
| lead_id | string | – | – |
| limit | integer | – | – |
No output schema declared.
No examples provided.
claim_lead Claim a lead ~69
Take an unclaimed lead from the shared pool into your own pipeline. Two-step: draft, then confirm.
| Name | Type | Req | Description |
|---|---|---|---|
| confirm | boolean | – | Leave false to get a draft of the change. Only set true after the user has seen the draft and approved it. |
| lead_id | string | yes | – |
No output schema declared.
No examples provided.
convert_trial_to_lead Convert trial signup to lead ~74
Turn a Shadow Trial signup into a lead in your pipeline at the shadow_trial stage. Two-step: draft, then confirm.
| Name | Type | Req | Description |
|---|---|---|---|
| confirm | boolean | – | Leave false to get a draft of the change. Only set true after the user has seen the draft and approved it. |
| trial_id | string | yes | – |
No output schema declared.
No examples provided.
find_leads Find leads ~123
Search leads you can see: your own plus the unclaimed pool. Filter by name/phone text, status, industry, city or minimum lead score.
| Name | Type | Req | Description |
|---|---|---|---|
| city | string | – | – |
| industry | string | – | Partial match, e.g. "hvac" or "dental". |
| limit | integer | – | – |
| min_score | integer | – | Pipeline lead score, 1-5. |
| scope | string | – | – |
| search | string | – | Text to match in business name, contact name or phone. |
| status | string | – | – |
No output schema declared.
No examples provided.
lead_details Lead details ~45
Everything about one lead: contact info, pitch (cold-call angle, Shadow Trial pitch, pain points), deal details, call history and notes.
| Name | Type | Req | Description |
|---|---|---|---|
| lead_id | string | yes | – |
No output schema declared.
No examples provided.
lead_gen_status Lead-gen status ~42
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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
log_call Log a call ~161
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.
| Name | Type | Req | Description |
|---|---|---|---|
| confirm | boolean | – | Leave false to get a draft of the change. Only set true after the user has seen the draft and approved it. |
| direction | string | – | – |
| follow_up_at | string | – | When to follow up, as an ISO 8601 date-time with timezone, e.g. 2026-10-09T10:00:00-05:00. |
| lead_id | string | yes | – |
| notes | string | – | – |
| outcome | string | yes | – |
No output schema declared.
No examples provided.
missed_call_cost Missed-call cost calculator ~137
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.
| Name | Type | Req | Description |
|---|---|---|---|
| avg_job_value | number | yes | Average revenue from one booked job, in dollars. |
| booking_percent | number | – | Share of answered calls that become a booked job. Default 50 is an assumption. |
| calls_per_week | number | yes | Inbound calls the business gets in a typical week. |
| missed_percent | number | – | Share of calls that go unanswered. Default 30 is an assumption; use the business's own figure if known. |
No output schema declared.
No examples provided.
my_account My RingGuard account ~24
Who is signed in to RingGuard, and a quick count of their pipeline.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
my_follow_ups My follow-ups ~35
Your leads with a follow-up due, including overdue ones, soonest first.
| Name | Type | Req | Description |
|---|---|---|---|
| days_ahead | integer | – | – |
No output schema declared.
No examples provided.
my_stats My call stats ~35
Your call activity over the last N days: totals by outcome, conversations, trials started and wins.
| Name | Type | Req | Description |
|---|---|---|---|
| days | integer | – | – |
No output schema declared.
No examples provided.
new_trial_signups New Shadow Trial signups ~48
Businesses that signed up for the free Shadow Trial on ringguard.online and haven't been converted to a lead yet.
| Name | Type | Req | Description |
|---|---|---|---|
| days | integer | – | – |
| include_converted | boolean | – | – |
No output schema declared.
No examples provided.
pipeline_report Pipeline report ~38
Snapshot of your pipeline: leads by stage, won deals and monthly recurring revenue, follow-ups due, the unclaimed pool and open trial signups.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
ringguard_cost_estimate RingGuard cost estimate ~85
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.
| Name | Type | Req | Description |
|---|---|---|---|
| avg_call_minutes | number | – | Average call length in minutes. Default 3 is an assumption. |
| calls_per_month | integer | yes | Calls RingGuard would answer per month (overflow + after-hours). |
No output schema declared.
No examples provided.
start_shadow_trial Start a free Shadow Trial ~166
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 privacy policy (https://ringguard.online/privacy). No sign-in needed.
| Name | Type | Req | Description |
|---|---|---|---|
| agreed_to_be_contacted | boolean | yes | Must be true: the person explicitly agreed to be contacted and to the privacy policy. |
| business_name | string | yes | – |
| city | string | – | – |
| contact_name | string | yes | – |
| string | yes | – | |
| industry | string | – | – |
| message | string | – | Anything the business wants RingGuard to know. |
| phone | string | yes | – |
| state | string | – | – |
No output schema declared.
No examples provided.
team_leaderboard Team leaderboard ~34
Owner only. Call activity per rep over the last N days, ranked by conversations.
| Name | Type | Req | Description |
|---|---|---|---|
| days | integer | – | – |
No output schema declared.
No examples provided.
top_leads_to_call Top leads to call ~66
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.
| Name | Type | Req | Description |
|---|---|---|---|
| industry | string | – | – |
| limit | integer | – | – |
No output schema declared.
No examples provided.
undo_last_change Undo last change ~71
Reverse the most recent change you made through Claude (claim, new lead, status change, logged call or trial conversion). Two-step: draft, then confirm.
| Name | Type | Req | Description |
|---|---|---|---|
| confirm | boolean | – | Leave false to get a draft of the change. Only set true after the user has seen the draft and approved it. |
No output schema declared.
No examples provided.
update_lead_status Update lead status ~74
Move one of your leads to a new pipeline stage. Two-step: draft, then confirm.
| Name | Type | Req | Description |
|---|---|---|---|
| confirm | boolean | – | Leave false to get a draft of the change. Only set true after the user has seen the draft and approved it. |
| lead_id | string | yes | – |
| status | string | yes | – |
No output schema declared.
No examples provided.
what_ringguard_does What RingGuard does ~60
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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
How do I install the RingGuard — AI Receptionist for Trade Businesses MCP server?
RingGuard — AI Receptionist for Trade Businesses is a hosted endpoint at https://ringguard.online/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · ringguard.online
claude mcp add --transport http online-ringguard-ringguard 'https://ringguard.online/mcp'
What is the RingGuard — AI Receptionist for Trade Businesses MCP server?
RingGuard — AI Receptionist for Trade Businesses is an MCP server listed in the public MCP registry as online.ringguard/ringguard. Missed-call cost, AI receptionist pricing and free trial signup; CRM tools for RingGuard sales reps. This page covers its hosted endpoint (https://ringguard.online/mcp).
Is the RingGuard — AI Receptionist for Trade Businesses MCP server safe to use?
RingGuard — AI Receptionist for Trade Businesses scores 91 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the RingGuard — AI Receptionist for Trade Businesses MCP server expose?
RingGuard — AI Receptionist for Trade Businesses exposes 21 tools: what_ringguard_does, missed_call_cost, ringguard_cost_estimate, start_shadow_trial, my_account, and 16 more. Their descriptions and schemas cost roughly 1,566 tokens of context every time the server is loaded.
Does the RingGuard — AI Receptionist for Trade Businesses MCP server require authentication?
Yes. RingGuard — AI Receptionist for Trade Businesses asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.
Is the RingGuard — AI Receptionist for Trade Businesses MCP server still maintained?
RingGuard — AI Receptionist for Trade Businesses is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What did VerifyMCP test on the RingGuard — AI Receptionist for Trade Businesses MCP server?
VerifyMCP ran 13 checks on RingGuard — AI Receptionist for Trade Businesses, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.