Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Ringback: Missed-Call Text-Back for Contractors

REMOTE · RINGBACK.0XPI.COM

Missed-call text-back for contractors: missed-call cost math, how it works, owners read their calls.

+3 this week 80 Trust /100

Last scanned (16 hours ago)

Scores higher than 77% of remote servers

Reachable. Last reached 21 Nov 2026.

Category CRM and Sales

Trust breakdown (7 categories)

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 Security80
  • The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
  • No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation. See how to fix → View diagnostics → Partial
  • 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
Transport & Reachability100
Schema Quality & AI Usability67
  • AI-judged instruction clarity (good).Pass
  • Context-footprint check failed: tool/resource definitions use about 720 tokens (~180/item across 4 items; 4 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management57
  • Stability observed for 17 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
What we tested

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 →

Changelog

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.

  • 21 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 53 to 57. That category is still filling its 30-day observation window: 16 days of observed history at the previous scan, 17 at this one. The score rises as the window fills, whether or not the server changes.

  • 18 Nov 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.

  • 16 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 37 to 40. That category is still filling its 30-day observation window: 11 days of observed history at the previous scan, 12 at this one. The score rises as the window fills, whether or not the server changes.

  • 14 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 30 to 33. That category is still filling its 30-day observation window: 9 days of observed history at the previous scan, 10 at this one. The score rises as the window fills, whether or not the server changes.

  • 12 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.

  • 10 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.

  • 8 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.

  • 6 Nov 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
Diagnostics

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 21 Nov 2026 · Probed https://ringback.0xpi.com/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_256_GCM_SHA384 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=ringback.0xpi.com CN=YE1,O=Let's Encrypt,C=US 3 Oct 2026 1 Jan 2027 ECDSA 256 ECDSA-SHA384 6ad7a2f0cf240da970619a896c419760953
SANs: ringback.0xpi.com
CN=YE1,O=Let's Encrypt,C=US (CA) CN=Root YE,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 ECDSA 384 ECDSA-SHA384 5ddd70dd31f801c85c186a7a04b80afe
CN=Root YE,O=ISRG,C=US (CA) CN=ISRG Root X2,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 ECDSA-SHA384 872165fc34b6e5fba8add5b3705fb53a
CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 SHA256-RSA 6c8f1dc727c7117f7baf853ac980f9cd

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of ringback.0xpi.com. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
com. DS published 19718 13 Verified
0xpi.com. No DS 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
strict-transport-security max-age=31536000
x-content-type-options nosniff
referrer-policy same-origin

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://ringback.0xpi.com/mcp Verified 200
http (plaintext) http://ringback.0xpi.com/mcp HTTPS enforced 301 https://ringback.0xpi.com/mcp
MCP tools · 4 exposed · ~589 tokens

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 →

Tool Tokens
estimate_missed_call_cost ~172

Arithmetic on your own numbers: calls per week x missed % x close rate x average job value, per week, month and year, with every step and assumption shown. It is an estimate of the value of jobs at stake from missed calls, not a prediction of what any tool will recover. Also shows how many saved jobs a month would cover Ringback's price.

NameTypeReqDescription
average_job_valuenumberyesAverage revenue per job, in US dollars.
calls_per_weeknumberyesInbound calls the business gets in a typical week.
close_rate_percentnumberyesShare of answered callers who normally book a job, in percent (e.g. 30).
missed_percentnumberyesShare of those calls that go unanswered, in percent (e.g. 25).

No output schema declared.

No examples provided.

how_ringback_works ~77

Facts about Ringback, missed-call text-back for contractors and home-service businesses: how the text is sent, phone requirements (Android, iPhone options), what the owner sees, price ($17/month or $170/year per business line), the 7-day free trial with no card, and what Ringback does not do.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

my_missed_calls ~177

List the missed calls in your own Ringback call log for a time range: when, the caller's number, whether a text-back went out (and its delivery status) or why not (e.g. already texted recently, opted out, do-not-text), and the lead's status. Counts first, then up to 50 most recent calls. Needs a personal Ringback access token, created by the business owner in Ringback (Settings, AI assistants) and sent as "Authorization: Bearer <token>". Read-only; reads only that business's own call and text log.

NameTypeReqDescription
rangestring–Time range: "today" (since midnight in the business's time zone), "7d", "30d" or "90d" (that many days back from now). Default "7d".

No output schema declared.

No examples provided.

my_texts_sent ~163

List the texts your Ringback line sent in a time range: missed-call text-backs, your replies from the dashboard and automatic replies, with delivery status as the phone reported it, the median time from call to text-back, and up to 50 most recent texts with their wording. Needs a personal Ringback access token, created by the business owner in Ringback (Settings, AI assistants) and sent as "Authorization: Bearer <token>". Read-only; reads only that business's own call and text log.

NameTypeReqDescription
rangestring–Time range: "today" (since midnight in the business's time zone), "7d", "30d" or "90d" (that many days back from now). Default "7d".

No output schema declared.

No examples provided.

Install

How do I install the Ringback: Missed-Call Text-Back for Contractors MCP server?

Ringback: Missed-Call Text-Back for Contractors is a hosted endpoint at https://ringback.0xpi.com/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 · ringback.0xpi.com

# add to Claude Code
claude mcp add --transport http com-0xpi-ringback-missed-call-text-back 'https://ringback.0xpi.com/mcp'
Common questions

What is the Ringback: Missed-Call Text-Back for Contractors MCP server?

Ringback: Missed-Call Text-Back for Contractors is an MCP server listed in the public MCP registry as com.0xpi.ringback/missed-call-text-back. Missed-call text-back for contractors: missed-call cost math, how it works, owners read their calls. This page covers its hosted endpoint (https://ringback.0xpi.com/mcp).

Is the Ringback: Missed-Call Text-Back for Contractors MCP server safe to use?

Ringback: Missed-Call Text-Back for Contractors scores 80 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 Ringback: Missed-Call Text-Back for Contractors MCP server expose?

Ringback: Missed-Call Text-Back for Contractors exposes 4 tools: estimate_missed_call_cost, how_ringback_works, my_missed_calls, my_texts_sent. Their descriptions and schemas cost roughly 589 tokens of context every time the server is loaded.

Does the Ringback: Missed-Call Text-Back for Contractors MCP server require authentication?

No. We connected to Ringback: Missed-Call Text-Back for Contractors without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the Ringback: Missed-Call Text-Back for Contractors MCP server still maintained?

Ringback: Missed-Call Text-Back for Contractors is still listed as active in the MCP registry. We last reached this channel on 21 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 Ringback: Missed-Call Text-Back for Contractors MCP server?

VerifyMCP ran 13 checks on Ringback: Missed-Call Text-Back for Contractors, 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.