mcp-registry/app.codaphone/mcp · v1.0.0
As of 2026-10-21 05:51 UTC, the Codaphone MCP server is up with a Glimind reliability score of 95/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks.
Business texting for AI agents: send texts, read threads, manage contacts and run campaigns.
Claude Code
claude mcp add --transport http codaphone-mcp-server https://mcp.codaphone.app
Claude Desktop · Windsurf · Cline (mcpServers JSON)
{
"mcpServers": {
"codaphone-mcp-server": {
"type": "http",
"url": "https://mcp.codaphone.app"
}
}
}
Third-party server, listed as discovered. Review its source before installing.
14 of 14 tool(s) carry no readOnlyHint/destructiveHint annotations.
Annotate read-only tools with {"readOnlyHint": true}. Agents and gateways can then run them without a confirmation prompt, and route around destructive ones. How to fix →
3 tool(s) look like they change state (create/send/delete/pay…) but declare no destructiveHint.
Set annotations {"readOnlyHint": false, "destructiveHint": true|false, "idempotentHint": …}. Clients use these to ask the user before a side effect and to auto-approve safe reads. How to fix →
No tool declares an outputSchema.
Declare outputSchema and return structuredContent (MCP 2025-06-18+). Agents can then parse results without guessing, and chain tools reliably. How to fix →
Paste-ready definitions with the problems above fixed. Changes marked verify need a human look. All of them as JSON: /v1/readiness/mcp-registry%2Fapp.codaphone%2Fmcp/fixes
{
"name": "add_contacts",
"description": "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.",
"inputSchema": {
"type": "object",
"required": [
"msisdn"
],
"properties": {
"name": {
"type": "string",
"description": "Contact name."
},
"msisdn": {
"type": "string",
"description": "Contact phone number, e.g. +14155550100."
},
"list_id": {
"type": "string",
"description": "Optional list to add the contact to."
},
"opt_in_source": {
"type": "string",
"description": "How the contact opted in (record-keeping)."
}
},
"additionalProperties": false
},
"annotations": {
"readOnlyHint": false,
"destructiveHint": false,
"idempotentHint": false
}
}{
"name": "create_campaign",
"description": "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.",
"inputSchema": {
"type": "object",
"required": [
"name"
],
"properties": {
"name": {
"type": "string",
"description": "Campaign name."
},
"base_message": {
"type": "string",
"description": "The base message text (optional; can be set later)."
}
},
"additionalProperties": false
},
"annotations": {
"readOnlyHint": false,
"destructiveHint": false,
"idempotentHint": false
}
}{
"name": "get_account",
"description": "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.",
"inputSchema": {
"type": "object",
"properties": {},
"additionalProperties": false
},
"annotations": {
"readOnlyHint": true
}
}Get an email or webhook when this server's readiness drops by 10+ points, tool-poisoning text appears, or a tool breaks:
curl -X POST https://glimind.com/v1/subscriptions -H 'content-type: application/json' -d '{"tools":["mcp-registry/app.codaphone/mcp"],"email":"[email protected]"}'Agents: watch_tool({"toolId": "mcp-registry/app.codaphone/mcp"}) over MCP.
run_campaign ~451 tokensprovision_number ~305 tokenssend_message ~230 tokenslist_contacts ~194 tokenssearch_numbers ~185 tokensStatic checks of the advertised tools/list (schema, descriptions, annotations, tool-poisoning patterns, names, size) plus observed protocol, uptime, latency and contract changes. Read-only: no tool is ever called. Weights: schema 15, docs 20, safety 15, efficiency 15, compatibility 15, protocol 5, reliability 10, stability 5. Token counts are estimates (~3.6 characters per token).
Operator? Fix these, then re-check live. Embed the readiness badge:
[](https://glimind.com/server/mcp-registry%2Fapp.codaphone%2Fmcp?ref=badge)
<a href="https://glimind.com/server/mcp-registry%2Fapp.codaphone%2Fmcp?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fapp.codaphone%2Fmcp.svg" alt="MCP agent-readiness"></a>
.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fapp.codaphone%2Fmcp.svg :target: https://glimind.com/server/mcp-registry%2Fapp.codaphone%2Fmcp?ref=badge :alt: MCP agent-readiness
Glimind records every version of this server's tool definitions in a signed, append-only transparency log. Current manifest sha256:e62b2a441443c01c…, first seen 2026-10-17, included at leaf 5809 of 37,491. Version history · verify what your client received.
Compare: most reliable communication servers · most reliable other servers · most reliable search servers
Glimind tells agents whether a server is up right now and how to call it, then fails over to a live alternative when it isn't.
Claude Code
claude mcp add --transport http glimind https://glimind.com/mcp
Claude Desktop · Windsurf · Cline (mcpServers JSON)
{
"mcpServers": {
"glimind": {
"type": "http",
"url": "https://glimind.com/mcp"
}
}
}
As of 2026-10-21 05:51 UTC, the Codaphone MCP server is up with a Glimind reliability score of 95/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks.
Codaphone MCP server advertises 14 tools, including add_contacts, create_campaign, get_account, get_campaign, get_message_status.
Point your MCP client at this streamable-http endpoint: https://mcp.codaphone.app
Glimind scanned all 14 tool definitions for tool-poisoning patterns — hidden or invisible characters, instructions that override the model, concealment from the user, requests to read credential or MCP config files, conversation exfiltration and cross-tool shadowing — and found none. This checks what the server tells the model, not what its code does; review the source before granting access to sensitive data.
Status page: 90-day uptime, every outage and how long it lasted.
Claim this listing to get the Verified operator marker, a remediation checklist and owner analytics, or embed the live badge from any of the tool pages above. Maintainers: alerts, deploy attestation and monthly reports.
Status is an automated estimate from Glimind's liveness checks (handshake and tool listing only; no tool is ever called) and may lag or differ from your network. Glimind is not affiliated with this server or its operator. Operator? Request a correction or opt out at https://glimind.com/opt-out.