mcp-registry/com.thetempleofdoom.hyperion/hyperion · v1.0.0
As of 2026-10-18 02:43 UTC, the Thetempleofdoom Hyperion Hyperion MCP server is down with a Glimind reliability score of 38/100 (grade F). Over the last 30 days it answered 98% of Glimind's liveness checks. It had 25 outages in 90 days, with a median recovery of 16 minutes.
Hyperion — MCP tool marketplace for AI agents: web, OSINT, security, research via one key.
Point your MCP client at this streamable-http endpoint: https://hyperion.thetempleofdoom.com/mcp
The endpoint did not complete an MCP handshake.
Check the URL, TLS certificate and that the server answers a JSON-RPC "initialize" POST. How to fix →
355 of 355 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 →
355 tools on one server. Tool-selection accuracy drops as the menu grows, and some clients (e.g. Cursor) cap the number of active tools.
Group tools by task into smaller servers or toolsets, and merge near-duplicates behind one tool with a mode parameter. How to fix →
5 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 →
Loading this server's tool list costs an agent ~16,586 tokens before any work — more than 90% of MCP servers.
Split rarely-used tools into a separate server or a toolset the client can enable, or expose one "search tools" entry point. Many agents load every connected server's tools into every request. How to fix →
Reachable 98.0% of the time over the last 30 days; median recovery 16 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.
Handshake + tools/list takes ~2,053 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: 10 tool(s) removed and 76 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 →
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 →
Runs commands or code supplied by the model. Legitimate for dev tools; clients should require confirmation. Example (execute_js, name): "execute_js(code)"
Declare destructiveHint/readOnlyHint on these tools and say plainly in the description what runs, where, and with what limits. 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.thetempleofdoom.hyperion%2Fhyperion/fixes
{
"name": "data_convert",
"description": "JSON/CSV/YAML/XML/query-string transforms (200 sats/call; free tier 100 calls/mo)",
"inputSchema": {
"type": "object",
"required": [
"data",
"fromFormat",
"toFormat"
],
"properties": {
"data": {
"type": "string",
"description": "Input data payload string."
},
"toFormat": {
"enum": [
"json",
"csv",
"yaml",
"query_string",
"xml"
],
"type": "string",
"description": "Target format."
},
"fromFormat": {
"enum": [
"json",
"csv",
"yaml",
"query_string"
],
"type": "string",
"description": "Source format."
}
}
},
"annotations": {
"readOnlyHint": true
}
}{
"name": "echo_order",
"description": "Buy voice credits (BTCPay invoice) (0 sats/call; free tier 100 calls/mo)",
"inputSchema": {
"type": "object",
"properties": {}
},
"annotations": {
"readOnlyHint": false,
"destructiveHint": false,
"idempotentHint": false
}
}{
"name": "execute_js",
"description": "Run JS in a sandbox, capture output (300 sats/call; free tier 100 calls/mo)",
"inputSchema": {
"type": "object",
"required": [
"code"
],
"properties": {
"code": {
"type": "string",
"description": "JavaScript expression or script snippet."
}
}
},
"annotations": {
"readOnlyHint": false,
"destructiveHint": false,
"idempotentHint": false
}
}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.thetempleofdoom.hyperion/hyperion"],"email":"[email protected]"}'Agents: watch_tool({"toolId": "mcp-registry/com.thetempleofdoom.hyperion/hyperion"}) over MCP.
math ~208 tokenschart ~180 tokenshttp_client ~175 tokensascii ~149 tokensregex ~140 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.thetempleofdoom.hyperion%2Fhyperion?ref=badge)
<a href="https://glimind.com/server/mcp-registry%2Fcom.thetempleofdoom.hyperion%2Fhyperion?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fcom.thetempleofdoom.hyperion%2Fhyperion.svg" alt="MCP agent-readiness"></a>
.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fcom.thetempleofdoom.hyperion%2Fhyperion.svg :target: https://glimind.com/server/mcp-registry%2Fcom.thetempleofdoom.hyperion%2Fhyperion?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:deb08b1ba0e1f4ad…, first seen 2026-10-17, included at leaf 464 of 23,299. Version history · verify what your client received.
Compare: most reliable media servers · most reliable productivity servers · most reliable data servers · most reliable payments servers · most reliable code 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-18 02:43 UTC, the Thetempleofdoom Hyperion Hyperion MCP server is down with a Glimind reliability score of 38/100 (grade F). Over the last 30 days it answered 98% of Glimind's liveness checks. It had 25 outages in 90 days, with a median recovery of 16 minutes.
Thetempleofdoom Hyperion Hyperion MCP server advertises 300+ tools, including ascii, chart, cron, data_convert, diff.
Point your MCP client at this streamable-http endpoint: https://hyperion.thetempleofdoom.com/mcp
Glimind scanned all 355 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.