Is com.thetempleofdoom.hyperion/hyperion up? Live MCP status

Not checked just now. The live check did not run for this request (more than 120 status pages asked for a fresh check in the last minute). Reload in a minute; the monthly census result is below.

Endpointhttps://hyperion.thetempleofdoom.com/mcp
Page built

One MCP handshake with the listed endpoint (server/discover at 2026-07-28, then initialize for a server on the older revision), with no credential and no retry, identifying itself as agentwares-mcp-liveness/0.1 (+https://agentwares-agentcheck.vercel.app/bot). It runs when this page is requested and the result is reused for 10 minutes, so the time above is when it was taken.

Live status every few hours: Wellknown

Email me when this server changes

That was one look. To hear when it stops answering or its tools change, leave an address.

Free, no password or GitHub: one confirmation email first, then a check every hour and an email when it stops answering or its tools change. Every email has a link to stop. More about it.

Monthly census, 6 October 2026

The census sends the same request to every remote listing in the official registry once a month. On 6 October 2026 this one answered a stock client with no credential. Every listing’s result: index.ndjson (what the files hold: index.meta.json).

Agent discovery documents at this origin

A2A agent cardNot published (HTTP 404).
/.well-known/agent-card.json
MCP server card (SEP-2127)Not published (HTTP 404).
https://hyperion.thetempleofdoom.com/mcp/server-card
MCP server card (SEP-1649 location)Not published (HTTP 404).
/.well-known/mcp/server-card.json — SEP-1649, a draft superseded by SEP-2127 on 21 January 2026
Web Bot Auth key directoryNot published (HTTP 404).
/.well-known/http-message-signatures-directory

Read at https://hyperion.thetempleofdoom.com with the monthly census on 9 October 2026: one GET each, no credential, never a signed request. A2A against v1.0.1, the server card against the MCP Server Card schema (SEP-2127), the card at SEP-1649’s location against the shape it has, the key directory against the Web Bot Auth draft of 1 September 2026. Who publishes them.

Tool changes between snapshots

In the 2026-10 snapshot it listed 355 tools: ascii, chart, cron, data_convert, diff, echo_beacon, echo_order, echo_tts, encode, execute_js, fc_map, fc_scrape, fc_search, hash, http_client, lynx_inspect, lynx_recon, lynx_steg, math, mcp_discover, mcp_readme, mcp_stats, mobsf_report, mobsf_scans, netutils, o_abusecontact, o_agify, o_airquality, o_antipode, o_api_key_scan, o_archiveorg, o_arxiv, o_ascii85, o_asn, o_asnlookup, o_asrank, o_atbash, o_attack_surface, o_barcode, o_base_convert, o_base32, o_base36, o_base64, o_bgphistory, o_bimi, o_binarytext, o_blockheight, o_bluesky, o_breach_aggregator, o_breachdb, o_breachdirectory, o_breachsearch, o_btcaddr, o_btcfees, o_c2_infrastructure, o_caesar, o_casify, o_cdnjs, o_cfradar, o_checksum, o_chesscom, o_cidr, o_circlhash, o_clickjacking, o_cloud, o_codeberg, o_codeforces, o_color, o_cookies, o_cors, o_cratedownloads, o_crates, o_cratestats, o_crc32, o_credential_stuffing, o_crossrefauthor, o_crypto, o_cryptomarket, o_csp_parse, o_cve, o_cve_poc_checker, o_cve_severity, o_cve_timeline, o_cvedetail, o_datacite, o_datauri, o_decode, o_dehashed_domain, o_depsdev, o_devto, o_dirlisting, o_disasters, o_dns, o_dnsbl, o_dnsgraph, o_dnsmx, o_dnsprop, o_dnsquery, o_dnsrecon, o_dnsverify and 255 more.

Its tools changed between 2026-09 and 2026-10:

Which tools were added or removed, and whose description or schemas changed, from content hashes in the monthly snapshots. Per tool, as JSON: /v1/drift.

The listing

Registry namecom.thetempleofdoom.hyperion/hyperion
Endpointhttps://hyperion.thetempleofdoom.com/mcp
Publisher repositorynot known: the registry did not return this listing within 4 seconds

Also

The full check by name, as JSON (on a 401 it also follows the OAuth discovery chain) · Watch it · Check another server · llms.txt

Free, no key, no signup. Terms · Privacy