mcp-registry/io.github.brntech/myotp · v0.1.14
Verdict. Brntech Myotp MCP server answered 99.97% of Glimind's liveness checks over 30 days, better than 40% of MCP servers, with 1557 ms median handshake and 1 outage in 90 days. Its agent-readiness grade is A (98/100) across 10 tools, costing an agent about 3,044 tokens to load. Checked every few minutes; no tool is ever called.
Data as of .
| Metric | Value | Better than |
|---|---|---|
| Uptime, 30 days | 99.97% | 40% of MCP servers |
| Median handshake latency | 1557 ms | 10% of MCP servers |
| p95 handshake latency | 3842 ms | — |
| Checks in 30 days | 4,889 | — |
| Outages, 90 days | 1 | — |
| Median recovery | 7 min | — |
| Agent-readiness score | 98/100 (A) | 92% of MCP servers |
| Tools | 10 | — |
| Tool-list size for an agent | ~3,044 tokens | 45% of MCP servers |
| Days observed | 29 | — |
As of 2026-10-26 18:40 UTC, the Brntech Myotp MCP server is up with a Glimind reliability score of 94/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks. It had 1 outage in 90 days, with a median recovery of 7 minutes.
Send and verify one-time passcodes over SMS, WhatsApp and Telegram.
Claude Code
claude mcp add --transport http brntech-myotp-mcp-server https://mcp.myotp.app/mcp
Claude Desktop · Windsurf · Cline (mcpServers JSON)
{
"mcpServers": {
"brntech-myotp-mcp-server": {
"type": "http",
"url": "https://mcp.myotp.app/mcp"
}
}
}
Third-party server, listed as discovered. Review its source before installing.
Handshake + tools/list takes ~1,511 ms.
Serve tools/list from memory, keep the process warm, and host close to your users. Every new agent session pays this before its first call.
In the last 30 days: 0 tool(s) removed and 1 schema change(s).
Add new tools or optional parameters instead of renaming or removing; deprecate first (say so in the description) and remove later. Agents cache tool contracts. How to fix →
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/io.github.brntech/myotp"],"email":"[email protected]"}'Agents: watch_tool({"toolId": "mcp-registry/io.github.brntech/myotp"}) over MCP.
generate_otp ~906 tokensverify_otp ~364 tokensget_usage_report ~357 tokensextend_otp ~290 tokenstop_up_credits ~248 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%2Fio.github.brntech%2Fmyotp?ref=badge)
<a href="https://glimind.com/server/mcp-registry%2Fio.github.brntech%2Fmyotp?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.github.brntech%2Fmyotp.svg" alt="MCP agent-readiness"></a>
.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.github.brntech%2Fmyotp.svg :target: https://glimind.com/server/mcp-registry%2Fio.github.brntech%2Fmyotp?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:0f4eab4c21f2753c…, first seen 2026-10-17, included at leaf 2554 of 74,788. Version history · verify what your client received.
Compare: most reliable security servers · most reliable communication servers · most reliable other servers · most reliable finance servers · most reliable data 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-26 18:40 UTC, the Brntech Myotp MCP server is up with a Glimind reliability score of 94/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks. It had 1 outage in 90 days, with a median recovery of 7 minutes.
Brntech Myotp MCP server advertises 10 tools, including check_otp_status, create_account, extend_otp, generate_otp, get_account_info.
Point your MCP client at this streamable-http endpoint: https://mcp.myotp.app/mcp
Glimind scanned all 10 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.