# 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.

- Trust score: 80/100 (high trust)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-21

## Components

- remote · `ringback.0xpi.com`: 80/100 (this document), [markdown](https://verifymcp.io/servers/com-0xpi-ringback-missed-call-text-back/ringback.md), [page](https://verifymcp.io/servers/com-0xpi-ringback-missed-call-text-back/ringback)

## Channel facts

- Endpoint: `https://ringback.0xpi.com/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.0`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-21.

- **Endpoint Security**: 80/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - 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.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 67/100
  - AI-judged instruction clarity (good).
  - 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.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 57/100
  - Stability observed for 17 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## 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.

### Claude

```bash
claude mcp add --transport http com-0xpi-ringback-missed-call-text-back 'https://ringback.0xpi.com/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "com-0xpi-ringback-missed-call-text-back": {
      "url": "https://ringback.0xpi.com/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "com-0xpi-ringback-missed-call-text-back": {
      "type": "http",
      "url": "https://ringback.0xpi.com/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.com-0xpi-ringback-missed-call-text-back]
url = "https://ringback.0xpi.com/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-0xpi-ringback-missed-call-text-back": {
      "type": "remote",
      "url": "https://ringback.0xpi.com/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add com-0xpi-ringback-missed-call-text-back --url 'https://ringback.0xpi.com/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  com-0xpi-ringback-missed-call-text-back:
    url: "https://ringback.0xpi.com/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "com-0xpi-ringback-missed-call-text-back": {
      "Transport": "http",
      "Url": "https://ringback.0xpi.com/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add com-0xpi-ringback-missed-call-text-back -t streamable-http -u 'https://ringback.0xpi.com/mcp'
```

### Other

```json
{
  "mcpServers": {
    "com-0xpi-ringback-missed-call-text-back": {
      "type": "http",
      "url": "https://ringback.0xpi.com/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-21 (score 80, +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.

### 2026-11-18 (score 79, +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.

### 2026-11-16 (score 78, +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.

### 2026-11-14 (score 77, +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.

### 2026-11-12 (score 76, +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.

### 2026-11-10 (score 75, +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.

### 2026-11-08 (score 74, +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.

### 2026-11-06 (score 73, +1)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

## MCP tools (4)

### `estimate_missed_call_cost` (~172 tokens)

Estimate what missed calls cost a service business

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.

Input parameters:

- `average_job_value` (number, required): Average revenue per job, in US dollars.
- `calls_per_week` (number, required): Inbound calls the business gets in a typical week.
- `close_rate_percent` (number, required): Share of answered callers who normally book a job, in percent (e.g. 30).
- `missed_percent` (number, required): Share of those calls that go unanswered, in percent (e.g. 25).

### `how_ringback_works` (~77 tokens)

How Ringback works, what it costs, what it does not do

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.

### `my_missed_calls` (~177 tokens)

My missed calls (from my Ringback call log)

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.

Input parameters:

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

### `my_texts_sent` (~163 tokens)

Texts my Ringback line sent

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.

Input parameters:

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

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/com-0xpi-ringback-missed-call-text-back/ringback#diagnostics

## Score history

- 2026-11-21: 80
- 2026-11-20: 79
- 2026-11-19: 79
- 2026-11-18: 79
- 2026-11-17: 78
- 2026-11-16: 78
- 2026-11-15: 77
- 2026-11-14: 77
- 2026-11-13: 76
- 2026-11-12: 76
- 2026-11-11: 75
- 2026-11-10: 75
- 2026-11-09: 74
- 2026-11-08: 74
- 2026-11-07: 73
- 2026-11-06: 73
- 2026-11-05: 72
- 2026-11-04: 72

## 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.

## Links

- Remote endpoint: https://ringback.0xpi.com/mcp
- Website: https://ringback.0xpi.com/
- Changelog RSS feed: https://verifymcp.io/servers/com-0xpi-ringback-missed-call-text-back/ringback.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-0xpi-ringback-missed-call-text-back/ringback/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/com-0xpi-ringback-missed-call-text-back/ringback.json
- HTML version of this page: https://verifymcp.io/servers/com-0xpi-ringback-missed-call-text-back/ringback
