Is the Codaphone MCP server down?

mcp-registry/app.codaphone/mcp · v1.0.0

healthy
Last checked 2026-10-21 05:51 UTC · handshake 304ms

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.

uptime (30d checks)
100%
checks observed
2,720
outages (90d)
0
tools
14

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

Install Codaphone MCP server

Add to Cursor Add to VS Code

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.

Agent-readiness: B (81/100)

B (81/100): 0 error(s), 2 warning(s) across 14 tool(s); ~2,356 tokens of tool definitions.
Scores higher than 36% of 15,455 MCP servers Glimind has audited.
Its tool list costs an agent ~2,356 tokens per session — more than 50% of servers.
79 → 81 since 2026-10-17
no tool-poisoning patterns
Schemas100
Descriptions100
Safety hints3
Token cost100
Client compatibility70
Protocol100
Reliability100
Stability100

What to fix (3)

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 →

Tools: add_contacts, create_campaign, get_account, get_campaign, get_message_status and 9 more

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 →

Tools: create_campaign, run_campaign, send_message

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 →

Auto-fix: 13 corrected tool definitions

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

add_contacts 1 change
{
  "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
  }
}
create_campaign 1 change
{
  "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
  }
}
get_account 1 change
{
  "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 alerted

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.

Passed

Largest tool definitions

Static 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:

Markdown
[![MCP agent-readiness](https://glimind.com/v1/readiness/badge/mcp-registry%2Fapp.codaphone%2Fmcp.svg)](https://glimind.com/server/mcp-registry%2Fapp.codaphone%2Fmcp?ref=badge)
HTML
<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>
reStructuredText
.. 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

Tool-definition log

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.

Tools (14)

Compare: most reliable communication servers · most reliable other servers · most reliable search servers

Know before your agent calls it

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.

Add Glimind — free, no signup:

Add to Cursor Add to VS Code

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"
    }
  }
}

FAQ

Is the Codaphone MCP server down right now?

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.

How many tools does Codaphone MCP server provide?

Codaphone MCP server advertises 14 tools, including add_contacts, create_campaign, get_account, get_campaign, get_message_status.

How do I install Codaphone MCP server?

Point your MCP client at this streamable-http endpoint: https://mcp.codaphone.app

Is the Codaphone MCP server safe to connect to an AI agent?

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.

Operator of Codaphone MCP server?

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.

Feedback
Help us improve