CodaPhone
REMOTE · MCP.CODAPHONE.APP
Business texting for AI agents: send texts, read threads, manage contacts and run campaigns.
Available components
Last scanned (9 hours ago)
Scores higher than 57% of remote servers
Reachable. Last reached 5 Nov 2026.
Category Communication
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 Security46
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- 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. See how to fix → View diagnostics → Unverified
- HTTPS check failed: the endpoint is reachable over plaintext HTTP. See how to fix → View diagnostics → Fail
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability80
- AI-judged instruction clarity (excellent).Pass
- 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. See how to fix → Fail
- 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 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 Safety75
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- 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. See how to fix → Fail
- An AI judge read all 15 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
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
- Stability: pass → 0.97 functional
- 1 Nov 26 +1
- Stability: 0.97 → pass security
- 30 Oct 26 +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.
- 28 Oct 26 +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.
- 26 Oct 26 +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.
- 23 Oct 26 +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.
- 21 Oct 26 +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.
- 19 Oct 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.
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://mcp.codaphone.app
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=codaphone.app | CN=WE1,O=Google Trust Services,C=US | 3 Nov 2026 | 1 Feb 2027 | ECDSA 256 | ECDSA-SHA256 | 48082c0674a91d6f0e1bd4f150cb031d |
| SANs: codaphone.app, mcp.codaphone.app, *.mcp.codaphone.app | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of mcp.codaphone.app. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| app. | present | 23684 | 8 | Verified |
| codaphone.app. | absent | 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 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://mcp.codaphone.app | Verified | 200 | |
| http (plaintext) | http://mcp.codaphone.app | Served over HTTP | 200 |
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_contacts ~120
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.
| Name | Type | Req | Description |
|---|---|---|---|
| list_id | string | – | Optional list to add the contact to. |
| msisdn | string | yes | Contact phone number, e.g. +14155550100. |
| name | string | – | Contact name. |
| opt_in_source | string | – | How the contact opted in (record-keeping). |
No output schema declared.
No examples provided.
create_campaign ~80
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.
| Name | Type | Req | Description |
|---|---|---|---|
| base_message | string | – | The base message text (optional; can be set later). |
| name | string | yes | Campaign name. |
No output schema declared.
No examples provided.
get_account ~58
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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_campaign ~51
Get one campaign by id, including its base message, audience, schedule, pacing, and send/failed/skipped counts. Requires the 'read' scope.
| Name | Type | Req | Description |
|---|---|---|---|
| campaign_id | string | yes | The campaign id. |
No output schema declared.
No examples provided.
get_message_status ~48
Get one message by id, including its delivery status, direction, body, segment count, and timestamp. Requires the 'read' scope.
| Name | Type | Req | Description |
|---|---|---|---|
| message_id | string | yes | The message id. |
No output schema declared.
No examples provided.
get_thread ~37
Get one conversation thread by id together with its messages. Requires the 'read' scope.
| Name | Type | Req | Description |
|---|---|---|---|
| thread_id | string | yes | The thread id. |
No output schema declared.
No examples provided.
list_campaigns ~38
List the account's bulk-messaging campaigns with their status and progress counts, plus the remaining automation credit balance. Requires the 'read' scope.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_contacts ~125
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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). |
No output schema declared.
No examples provided.
list_threads ~74
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.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Max threads to return (default 50). |
| offset | integer | – | Number of threads to skip (default 0). |
No output schema declared.
No examples provided.
mark_thread_read ~54
Mark a conversation thread as read (clears its unread count) and return the account's new total inbox unread count. Requires the 'read' scope.
| Name | Type | Req | Description |
|---|---|---|---|
| thread_id | string | yes | The thread id to mark read. |
No output schema declared.
No examples provided.
provision_number ~127
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.
| Name | Type | Req | Description |
|---|---|---|---|
| kind | string | – | Number type (default local). |
| label | string | – | Friendly label for the number. |
| msisdn | string | yes | The number to set up, in +1XXXXXXXXXX form. |
| registration | object | – | Optional business details for the number. |
No output schema declared.
No examples provided.
run_campaign ~269
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.
| Name | Type | Req | Description |
|---|---|---|---|
| action | string | yes | The lifecycle action to run. |
| base_message | string | – | generate: base message to vary from. |
| campaign_id | string | yes | 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. |
No output schema declared.
No examples provided.
search_numbers ~118
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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). |
No output schema declared.
No examples provided.
send_message ~152
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.
| Name | Type | Req | Description |
|---|---|---|---|
| body | string | yes | 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). |
No output schema declared.
No examples provided.
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.
remote · mcp.codaphone.app
claude mcp add --transport http app-codaphone-mcp 'https://mcp.codaphone.app/'
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.