mcp-registry/com.jojapi/sms-verify · v1.0.0
As of 2026-10-19 02:43 UTC, the Jojapi Sms Verify MCP server is up with a Glimind reliability score of 93/100 (grade A). Over the last 30 days it answered 99.9% of Glimind's liveness checks. It had 2 outages in 90 days, with a median recovery of 8 minutes.
SMS Verify: SMS Verify API is a secure and easy-to-integrate service that sends verification codes.
Claude Code
claude mcp add --transport http jojapi-sms-verify-mcp-server https://mcp.jojapi.com/sms-verify
Claude Desktop · Windsurf · Cline (mcpServers JSON)
{
"mcpServers": {
"jojapi-sms-verify-mcp-server": {
"type": "http",
"url": "https://mcp.jojapi.com/sms-verify"
}
}
}
Third-party server, listed as discovered. Review its source before installing.
2 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 →
2 of 2 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 →
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%2Fcom.jojapi%2Fsms-verify/fixes
{
"name": "post_estimate_cost",
"description": "Estimate Cost Billing per call: 0 Credits.",
"inputSchema": {
"type": "object",
"properties": {
"body": {
"type": "object",
"description": "JSON request body. Example: {\"target\":\"+44 7459 034784\"}"
}
},
"additionalProperties": false
},
"annotations": {
"readOnlyHint": false,
"destructiveHint": false,
"idempotentHint": false
},
"title": "Estimate Cost"
}{
"name": "post_send_numeric_verify",
"description": "Send Verify SMS Billing per call: Credits: metered (~101 avg).",
"inputSchema": {
"type": "object",
"properties": {
"body": {
"type": "object",
"description": "JSON request body. Example: {\"target\":\"+44 7459 034784\"}"
}
},
"additionalProperties": false
},
"annotations": {
"readOnlyHint": false,
"destructiveHint": false,
"idempotentHint": false
},
"title": "Send Verify SMS"
}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/com.jojapi/sms-verify"],"email":"[email protected]"}'Agents: watch_tool({"toolId": "mcp-registry/com.jojapi/sms-verify"}) over MCP.
post_send_numeric_verify ~82 tokenspost_estimate_cost ~74 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%2Fcom.jojapi%2Fsms-verify?ref=badge)
<a href="https://glimind.com/server/mcp-registry%2Fcom.jojapi%2Fsms-verify?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fcom.jojapi%2Fsms-verify.svg" alt="MCP agent-readiness"></a>
.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fcom.jojapi%2Fsms-verify.svg :target: https://glimind.com/server/mcp-registry%2Fcom.jojapi%2Fsms-verify?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:8a4242ad7b5f48c7…, first seen 2026-10-19, included at leaf 24156 of 24,447. Version history · verify what your client received.
Compare: most reliable other servers · most reliable communication 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-19 02:43 UTC, the Jojapi Sms Verify MCP server is up with a Glimind reliability score of 93/100 (grade A). Over the last 30 days it answered 99.9% of Glimind's liveness checks. It had 2 outages in 90 days, with a median recovery of 8 minutes.
Jojapi Sms Verify MCP server advertises 2 tools, including post_estimate_cost, post_send_numeric_verify.
Point your MCP client at this streamable-http endpoint: https://mcp.jojapi.com/sms-verify
Glimind scanned all 2 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.