# CodaPhone (remote · mcp.codaphone.app)

Business texting for AI agents: send texts, read threads, manage contacts and run campaigns.

- Trust score: 71/100 (medium)
- Change this week: +1
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- remote · `mcp.codaphone.app`: 71/100 (this document), [markdown](https://verifymcp.io/servers/app-codaphone-mcp/mcp.md), [page](https://verifymcp.io/servers/app-codaphone-mcp/mcp)

## Channel facts

- Endpoint: `https://mcp.codaphone.app`
- 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-05.

- **Endpoint Security**: 46/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation not fully verified: no authorisation is required to call this server, and 14 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.
  - HTTPS check failed: the endpoint is reachable over plaintext HTTP.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - 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**: 80/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 1603 tokens (~114/item across 14 items; 14 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 97/100
  - Stability observed for 29 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**: 75/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - 0 of 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "send_message" implies "send" and declares no destructiveHint at all, which the MCP spec reads as destructive by default.
  - An AI judge read all 15 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 60/100
  - Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28.

## Install

### How do I install the CodaPhone MCP server?

CodaPhone is a hosted endpoint at https://mcp.codaphone.app/, 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 app-codaphone-mcp 'https://mcp.codaphone.app/'
```

### Cursor

```json
{
  "mcpServers": {
    "app-codaphone-mcp": {
      "url": "https://mcp.codaphone.app/"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "app-codaphone-mcp": {
      "type": "http",
      "url": "https://mcp.codaphone.app/"
    }
  }
}
```

### Codex

```toml
[mcp_servers.app-codaphone-mcp]
url = "https://mcp.codaphone.app/"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "app-codaphone-mcp": {
      "type": "remote",
      "url": "https://mcp.codaphone.app/",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add app-codaphone-mcp --url 'https://mcp.codaphone.app/' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  app-codaphone-mcp:
    url: "https://mcp.codaphone.app/"
```

### Netclaw

```json
{
  "McpServers": {
    "app-codaphone-mcp": {
      "Transport": "http",
      "Url": "https://mcp.codaphone.app/"
    }
  }
}
```

### Vellum

```bash
assistant mcp add app-codaphone-mcp -t streamable-http -u 'https://mcp.codaphone.app/'
```

### Other

```json
{
  "mcpServers": {
    "app-codaphone-mcp": {
      "type": "http",
      "url": "https://mcp.codaphone.app/"
    }
  }
}
```

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-05 (score 71, −1)

- [functional] Stability: pass → 0.97

### 2026-11-01 (score 72, +1)

- [security] Stability: 0.97 → pass

### 2026-10-30 (score 71, +1)

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

### 2026-10-28 (score 70, +1)

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

### 2026-10-26 (score 69, +1)

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

### 2026-10-23 (score 68, +1)

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

### 2026-10-21 (score 67, +1)

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

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

## MCP tools (14)

### `get_account` (~58 tokens)

Get the current CodaPhone account: its name and mode (live/test), the active number (if any), the current plan and its monthly/daily send caps, usage so far, and remaining automation credits. Requires the 'read' scope.

### `search_numbers` (~118 tokens)

Search available phone numbers to provision. Optionally filter by country, number kind (local or tollfree), and a 3-digit area code. Returns candidate numbers with a formatted display, city/region, and monthly price. Does not buy anything. Requires the 'numbers' scope.

Input parameters:

- `areaCode` (string): Preferred 3-digit area code, e.g. 415 (local only).
- `country` (string): ISO country code, e.g. US (default US).
- `kind` (string): Number type (default local).

### `provision_number` (~127 tokens)

Provision (set up) a phone number for the account from a candidate returned by search_numbers. Provide the exact msisdn in +1XXXXXXXXXX form and the number kind; optional label and business registration details may be included. An account can hold one active number. Requires the 'numbers' scope.

Input parameters:

- `kind` (string): Number type (default local).
- `label` (string): Friendly label for the number.
- `msisdn` (string, required): The number to set up, in +1XXXXXXXXXX form.
- `registration` (object): Optional business details for the number.

### `send_message` (~152 tokens)

Send an SMS from the account's number. Provide the message 'body', and either 'to' (a recipient phone number, with optional 'name' to save the contact) or an existing 'thread_id' to reply within a conversation. Opted-out contacts are blocked and free-send/plan limits apply automatically. Requires the 'send' scope.

Input parameters:

- `body` (string, required): The message text to send.
- `name` (string): Optional name to save for a new contact when using 'to'.
- `thread_id` (string): Reply inside this existing conversation instead of 'to'.
- `to` (string): Recipient phone number, e.g. +14155550100 (omit if using thread_id).

### `get_message_status` (~48 tokens)

Get one message by id, including its delivery status, direction, body, segment count, and timestamp. Requires the 'read' scope.

Input parameters:

- `message_id` (string, required): The message id.

### `list_threads` (~74 tokens)

List the account's conversation threads (the inbox), most recent first, with unread counts and last-message previews. Supports limit/offset pagination. Requires the 'read' scope.

Input parameters:

- `limit` (integer): Max threads to return (default 50).
- `offset` (integer): Number of threads to skip (default 0).

### `get_thread` (~37 tokens)

Get one conversation thread by id together with its messages. Requires the 'read' scope.

Input parameters:

- `thread_id` (string, required): The thread id.

### `mark_thread_read` (~54 tokens)

Mark a conversation thread as read (clears its unread count) and return the account's new total inbox unread count. Requires the 'read' scope.

Input parameters:

- `thread_id` (string, required): The thread id to mark read.

### `list_contacts` (~125 tokens)

List the account's contacts with opt-in status and timezone. Optionally filter by a search term or a list id, choose a sort, and paginate with limit/offset. Requires the 'read' scope.

Input parameters:

- `limit` (integer): Max contacts to return (default 500).
- `list_id` (string): Only contacts in this list.
- `offset` (integer): Number of contacts to skip (default 0).
- `search` (string): Filter by name or number.
- `sort` (string): Sort order, e.g. recent or name (default recent).

### `add_contacts` (~120 tokens)

Add a contact to the account. Provide the phone number (msisdn) and optionally a name, a list_id to file it under, and an opt_in_source note. Adds one contact per call. Requires the 'contacts' scope.

Input parameters:

- `list_id` (string): Optional list to add the contact to.
- `msisdn` (string, required): Contact phone number, e.g. +14155550100.
- `name` (string): Contact name.
- `opt_in_source` (string): How the contact opted in (record-keeping).

### `list_campaigns` (~38 tokens)

List the account's bulk-messaging campaigns with their status and progress counts, plus the remaining automation credit balance. Requires the 'read' scope.

### `get_campaign` (~51 tokens)

Get one campaign by id, including its base message, audience, schedule, pacing, and send/failed/skipped counts. Requires the 'read' scope.

Input parameters:

- `campaign_id` (string, required): The campaign id.

### `create_campaign` (~80 tokens)

Create a new bulk-messaging campaign with a name and an optional base message. After creating, use run_campaign to generate variations, set the audience, schedule, and launch it. Requires the 'campaigns' scope.

Input parameters:

- `base_message` (string): The base message text (optional; can be set later).
- `name` (string, required): Campaign name.

### `run_campaign` (~269 tokens)

Advance a campaign through its lifecycle. Provide the campaign_id and an action:
  \- generate: create message variations (optional base_message, count)
  \- variations: save edited variations (variations: [{body, active}])
  \- audience: set the recipient list (list_id)
  \- schedule: set send time/pacing (schedule_at, pace_seconds, daily_ceiling)
  \- launch: start sending (or start at the scheduled time)
  \- pause / resume / cancel: control a running campaign
Sends honor opt-outs, sending hours, credits, and plan caps automatically. Requires the 'campaigns' scope.

Input parameters:

- `action` (string, required): The lifecycle action to run.
- `base_message` (string): generate: base message to vary from.
- `campaign_id` (string, required): The campaign id.
- `count` (integer): generate: how many variations.
- `daily_ceiling` (integer): schedule: max sends per day (<= plan cap).
- `list_id` (string): audience: the contact list to send to.
- `pace_seconds` (integer): schedule: seconds between sends.
- `schedule_at` (string): schedule: ISO timestamp to start, or null for send-now.
- `variations` (array): variations: the edited variations to save.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/app-codaphone-mcp/mcp#diagnostics

## Score history

- 2026-11-05: 71
- 2026-11-04: 72
- 2026-11-03: 72
- 2026-11-02: 72
- 2026-11-01: 72
- 2026-10-31: 71
- 2026-10-30: 71
- 2026-10-29: 70
- 2026-10-28: 70
- 2026-10-27: 69
- 2026-10-26: 69
- 2026-10-25: 68
- 2026-10-24: 68
- 2026-10-23: 68
- 2026-10-22: 67
- 2026-10-21: 67
- 2026-10-20: 66
- 2026-10-19: 66
- 2026-10-18: 65
- 2026-10-17: 65
- 2026-10-16: 64
- 2026-10-15: 64
- 2026-10-14: 63
- 2026-10-13: 63
- 2026-10-12: 62
- 2026-10-10: 61
- 2026-10-07: 60
- 2026-10-05: 59
- 2026-10-04: 59
- 2026-10-03: 58

## Common questions

### What is the CodaPhone MCP server?

CodaPhone is an MCP server listed in the public MCP registry as app.codaphone/mcp. Business texting for AI agents: send texts, read threads, manage contacts and run campaigns. This page covers its hosted endpoint (https://mcp.codaphone.app).

### Is the CodaPhone MCP server safe to use?

CodaPhone scores 71 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 CodaPhone MCP server expose?

CodaPhone exposes 14 tools: get_account, search_numbers, provision_number, send_message, get_message_status, and 9 more. Their descriptions and schemas cost roughly 1,351 tokens of context every time the server is loaded.

### Does the CodaPhone MCP server require authentication?

No. We connected to CodaPhone without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the CodaPhone MCP server still maintained?

CodaPhone 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 CodaPhone MCP server?

VerifyMCP ran 12 checks on CodaPhone, covering TLS certificate, HTTPS, HSTS header, DNSSEC and 8 more. One item could not be completed, a gap on our side rather than a finding about CodaPhone: Authorization. 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://mcp.codaphone.app/
- Authorisation metadata: https://mcp.codaphone.app/.well-known/oauth-protected-resource
- Website: https://codaphone.app/developers/mcp
- Changelog RSS feed: https://verifymcp.io/servers/app-codaphone-mcp/mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/app-codaphone-mcp/mcp/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/app-codaphone-mcp/mcp.json
- HTML version of this page: https://verifymcp.io/servers/app-codaphone-mcp/mcp