mcp-registry/co.roterminal/roterminal · registry v0.1.0 · server reports v0.5.0
Also listed as github/elijahmadonia/roterminal-ai
claude mcp add --transport http glimind https://glimind.com/mcp?ref=install-server. Other clientsAs of 2026-11-16 21:41 UTC, the RoTerminal MCP server is up with a Glimind reliability score of 68/100 (grade C). Over the last 30 days it answered 98.2% of Glimind's liveness checks. It had 101 outages in 90 days, with a median recovery of 2 minutes.
Live data on every Roblox game: players now, history, rising games, trends and studios.
Point your MCP client at this streamable-http endpoint: https://roterminal.co/mcp
Up 94.5% of the time over the 28 days we have observed; median recovery 2 min.
Agents fail over to an alternative the first time a call fails. Add health checks and restart-on-failure, and avoid cold starts on serverless hosts.
7 parameter(s) across 5 tool(s) have no description.
Add a "description" to each parameter with its format and an example ("ISO 8601 date, e.g. 2026-10-17"). This is the commonest cause of wrong arguments on the first call. 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 →
In the last 30 days: 0 tool(s) removed and 8 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/co.roterminal/roterminal"],"email":"[email protected]"}'Agents: watch_tool({"toolId": "mcp-registry/co.roterminal/roterminal"}) over MCP.
routine ~614 tokenstrack ~580 tokenscharts ~424 tokensseries ~414 tokensdossier ~399 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.
Shows whether the server is live and its agent-readiness score; it updates within the hour.
[](https://glimind.com/server/mcp-registry%2Fco.roterminal%2Froterminal?ref=badge)
<a href="https://glimind.com/server/mcp-registry%2Fco.roterminal%2Froterminal?ref=badge"><img src="https://glimind.com/badge/mcp-registry%2Fco.roterminal%2Froterminal.svg" alt="MCP server status"></a>
Glimind records every version of this server's tool definitions in a signed, append-only transparency log. Current manifest sha256:ecbaa28402092097…, first seen 2026-11-04, included at leaf 163150 of 305,823. Version history · verify what your client received.
Compare: most reliable data servers · most reliable search servers · most reliable knowledge servers · most reliable analytics servers · most reliable productivity 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?ref=install-server
Claude Desktop · Windsurf · Cline (mcpServers JSON)
{
"mcpServers": {
"glimind": {
"type": "http",
"url": "https://glimind.com/mcp?ref=install-server"
}
}
}
As of 2026-11-16 21:41 UTC, the RoTerminal MCP server is up with a Glimind reliability score of 68/100 (grade C). Over the last 30 days it answered 98.2% of Glimind's liveness checks. It had 101 outages in 90 days, with a median recovery of 2 minutes.
RoTerminal MCP server advertises 29 tools, including charts, compare, days, dossier, find.
Point your MCP client at this streamable-http endpoint: https://roterminal.co/mcp
Glimind scanned all 29 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.