Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

com.thetempleofdoom.hyperion/hyperion

REMOTE · HYPERION.THETEMPLEOFDOOM.COM · SCANNED SEP 25

Hyperion — MCP tool marketplace for AI agents: web, OSINT, security, research via one key.

+3 this week 76 Trust /100
Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →

Endpoint Security63
Transport & Reachability100
Schema Quality & AI Usability68
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 12150 tokens (~34/item across 355 items; 355 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
  • No destabilizing schema changes in the last 30 days.Pass
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
Tool Safety75
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • 0 of 2 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "execute_js" implies "execute" and declares no destructiveHint at all, which the MCP spec reads as destructive by default. See how to fix → Fail
  • An AI judge read all 356 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
  • Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
Install

How do I install the com.thetempleofdoom.hyperion/hyperion MCP server?

com.thetempleofdoom.hyperion/hyperion is a hosted endpoint at https://hyperion.thetempleofdoom.com/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

remote · hyperion.thetempleofdoom.com

# add to Claude Code
claude mcp add --transport http com-thetempleofdoom-hyperion-hyperion 'https://hyperion.thetempleofdoom.com/mcp'
// .cursor/mcp.json
{
  "mcpServers": {
    "com-thetempleofdoom-hyperion-hyperion": {
      "url": "https://hyperion.thetempleofdoom.com/mcp"
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "com-thetempleofdoom-hyperion-hyperion": {
      "type": "http",
      "url": "https://hyperion.thetempleofdoom.com/mcp"
    }
  }
}
# ~/.codex/config.toml
[mcp_servers.com-thetempleofdoom-hyperion-hyperion]
url = "https://hyperion.thetempleofdoom.com/mcp"
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-thetempleofdoom-hyperion-hyperion": {
      "type": "remote",
      "url": "https://hyperion.thetempleofdoom.com/mcp",
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add com-thetempleofdoom-hyperion-hyperion --url 'https://hyperion.thetempleofdoom.com/mcp' --transport streamable-http
# ~/.hermes/config.yaml
mcp_servers:
  com-thetempleofdoom-hyperion-hyperion:
    url: "https://hyperion.thetempleofdoom.com/mcp"
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "com-thetempleofdoom-hyperion-hyperion": {
      "Transport": "http",
      "Url": "https://hyperion.thetempleofdoom.com/mcp"
    }
  }
}
# add to Vellum
assistant mcp add com-thetempleofdoom-hyperion-hyperion -t streamable-http -u 'https://hyperion.thetempleofdoom.com/mcp'
// mcp.json
{
  "mcpServers": {
    "com-thetempleofdoom-hyperion-hyperion": {
      "type": "http",
      "url": "https://hyperion.thetempleofdoom.com/mcp"
    }
  }
}

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 25 Sept 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 24 Sept 26 0
    • New tool “fc_map” functional
    • New tool “fc_scrape” functional
    • New tool “fc_search” functional
    • New tool “px_info” functional
    • New tool “px_order” functional
    • New tool “px_plans” functional
    • New tool “re_search” functional
    • New tool “re_semantic” functional
    • New tool “re_summarize” functional
  • 23 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.

  • 22 Sept 26 0

    We did not load change detail this far back for this component, so this day may have recorded more than is shown.

    • Schema quality: 53 → 34 ▲ functional
    • New tool “o_snusbase_hash” functional
    • New tool “o_punycode” functional
    • New tool “o_agify” functional
    • New tool “o_marineweather” functional
    • New tool “o_trendingwiki” functional
    • New tool “o_kev” functional
    • New tool “o_hibp_email” functional
    • New tool “o_roman” functional
    • New tool “v_case” functional
    • New tool “o_pypistats” functional
    • New tool “o_sitemap” functional
    • New tool “o_peers” functional
    • New tool “o_jslibs” functional
    • New tool “o_redirects” functional
    • New tool “o_gravatarfull” functional
    • New tool “o_openphish” functional
    • New tool “o_openalexwork” functional
    • New tool “o_dehashed_domain” functional
    • New tool “o_binarytext” functional
    • New tool “o_gitlab” functional
    • New tool “o_maven” functional
    • New tool “o_cratestats” functional
    • New tool “o_hnsearch” functional
    • New tool “v_slug” functional
    • New tool “o_httping” functional
    • New tool “o_macvendorlookup” functional
    • New tool “o_portlookup” functional
    • New tool “o_trufflehog_url” functional
    • New tool “o_bluesky” functional
    • New tool “o_asn” functional
    • New tool “o_arxiv” functional
    • New tool “v_htmldec” functional
    • New tool “o_exploit_cve” functional
    • New tool “o_quakes” functional
    • New tool “o_golangpkg” functional
    • New tool “o_nuget” functional
    • New tool “o_rot13” functional
    • New tool “o_macvendor” functional
    • New tool “o_attack_surface” functional
    • New tool “o_casify” functional
    • New tool “o_feodoips” functional
    • New tool “o_atbash” functional
    • New tool “o_credential_stuffing” functional
    • New tool “o_nvdcve” functional
    • New tool “o_revgeocode” functional
    • New tool “o_hexdump” functional
    • New tool “o_c2_infrastructure” functional
    • New tool “o_cookies” functional
    • New tool “o_tor” functional
    • New tool “o_revgeo” functional
    • New tool “o_ipwhois” functional
    • New tool “o_reversedns” functional
    • New tool “o_tlsa” functional
    • New tool “o_favicon” functional
    • New tool “o_cdnjs” functional
    • New tool “o_dnsgraph” functional
    • New tool “o_semanticscholar” functional
    • New tool “o_links” functional
    • New tool “o_cidr” functional
    • New tool “o_npmorg” functional
    • New tool “o_passgen” functional
    • New tool “o_hibp” functional
    • New tool “o_pluscode” functional
    • New tool “o_robots” functional
    • New tool “o_robotsmeta” functional
    • New tool “o_archiveorg” functional
    • New tool “o_ipint” functional
    • New tool “v_uuid” functional
    • New tool “o_keybase” functional
    • New tool “o_phoneapps” functional
    • New tool “o_email” functional
    • New tool “o_unpaywall” functional
    • New tool “o_sopostuser” functional
    • New tool “o_otxip” functional
    • New tool “o_steam_user” functional
    • New tool “o_ens” functional
    • New tool “o_rpki” functional
    • New tool “o_nstrace” functional
    • New tool “v_txt2hex” functional
    • New tool “o_homoglyph” functional
    • New tool “o_mac” functional
    • New tool “o_password_dumps” functional
    • New tool “o_mgrs” functional
    • New tool “o_telegram_channel” functional
    • New tool “o_hudsonrock” functional
    • New tool “o_hostname” functional
    • New tool “o_securitytxt” functional
    • New tool “v_json_format” functional
    • New tool “o_slug” functional
    • New tool “o_infra_fingerprint” functional
    • New tool “o_cve_timeline” functional
    • New tool “o_base32” functional
    • New tool “o_intelx_email” functional
    • New tool “o_subbrute” functional
    • New tool “o_hashid” functional
    • New tool “o_clickjacking” functional
    • New tool “o_threatcrowd” functional
    • New tool “o_supply_chain_risk” functional
    • New tool “o_breachdirectory” functional
    • New tool “o_jarm” functional
    • New tool “o_ip_math” functional
    • New tool “o_srvlookup” functional
    • New tool “v_hex2txt” functional
    • New tool “o_numwords” functional
    • New tool “v_metrics” functional
    • New tool “o_datacite” functional
    • New tool “o_mimetype” functional
    • New tool “o_uuid_validate” functional
    • New tool “o_teamcymru” functional
    • New tool “o_cryptomarket” functional
    • New tool “o_isexitnode” functional
    • New tool “o_phonepivot” functional
    • New tool “o_revimg” functional
    • New tool “o_ghkeysgpg” functional
    • New tool “o_holidays” functional
    • New tool “v_regex” functional
    • New tool “o_htmlencode” functional
    • New tool “o_moonphase” functional
    • New tool “o_genderize” functional
    • New tool “o_otxdomain” functional
    • New tool “o_breach_aggregator” functional
    • New tool “o_asnlookup” functional
    • New tool “o_rdap_domain” functional
    • New tool “o_leakcheck” functional
    • New tool “o_stringmetrics” functional
    • New tool “o_spacepeople” functional
    • New tool “o_uuid” functional
    • New tool “o_npmdl” functional
    • New tool “o_bgphistory” functional
    • New tool “o_httpmethods” functional
    • New tool “o_leet” functional
    • New tool “o_isotime” functional
    • New tool “o_isbn” functional
    • New tool “o_pypi” functional
    • New tool “o_dnsverify” functional
    • New tool “o_wordcount” functional
    • New tool “o_dnsrecon” functional
    • New tool “o_epss” functional
    • New tool “o_internetdb” functional
    • New tool “o_github_code” functional
    • New tool “v_hash” functional
    • New tool “o_cors” functional
    • New tool “o_abusecontact” functional
    • New tool “o_unicode_lookup” functional
    • New tool “o_openfoodfacts” functional
    • New tool “o_uuencode” functional
    • New tool “o_wikipv” functional
    • New tool “o_dns” functional
    • New tool “o_smtpbanner” functional
    • New tool “o_formaudit” functional
    • New tool “v_urldec” functional
    • New tool “v_now” functional
    • New tool “o_utm” functional
    • New tool “o_httpcode” functional
    • New tool “v_json_diff” functional
    • New tool “o_zenodo” functional
    • New tool “o_decode” functional
    • New tool “o_breachdb” functional
    • New tool “o_cfradar” functional
    • New tool “o_breachsearch” functional
    • New tool “o_musicbrainzartist” functional
    • New tool “o_chesscom” functional
    • New tool “o_doh” functional
    • New tool “o_cratedownloads” functional
    • New tool “o_swagger” functional
    • New tool “o_suntimes” functional
    • New tool “v_epoch” functional
    • New tool “o_btcfees” functional
    • New tool “o_latlonformat” functional
    • New tool “o_emailsec” functional
    • New tool “o_ascii85” functional
    • New tool “o_onthisday” functional
    • New tool “o_datauri” functional
    • New tool “o_gh_secret_scan” functional
    • New tool “o_wikisummary” functional
    • New tool “o_phonevcard” functional
    • New tool “o_isin” functional
    • New tool “o_port” functional
    • New tool “o_depsdev” functional
    • New tool “o_tech” functional
    • New tool “o_sri_check” functional
    • New tool “o_base36” functional
    • New tool “o_manifest” functional
    • New tool “o_crc32” functional
    • New tool “o_railfence” functional
    • New tool “o_caesar” functional
    • New tool “o_airquality” functional
    • New tool “o_nationalize” functional
  • 21 Sept 26 +1

    We did not load change detail this far back for this component, so this day may have recorded more than is shown.

  • 19 Sept 26 +1

    We did not load change detail this far back for this component, so this day may have recorded more than is shown.

  • 17 Sept 26 +1

    We did not load change detail this far back for this component, so this day may have recorded more than is shown.

  • 15 Sept 26 +49

    We did not load change detail this far back for this component, so this day may have recorded more than is shown.

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 25 Sept 2026 · Probed https://hyperion.thetempleofdoom.com/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=thetempleofdoom.com CN=WE1,O=Google Trust Services,C=US 16 Aug 2026 14 Nov 2026 ECDSA 256 ECDSA-SHA256 8554684b5ee7e09e0e9320057a46c58e
SANs: thetempleofdoom.com, *.thetempleofdoom.com
CN=WE1,O=Google Trust Services,C=US (CA) CN=GTS Root R4,O=Google Trust Services LLC,C=US 13 Dec 2023 20 Feb 2029 ECDSA 256 ECDSA-SHA384 7ff31977972c224a76155d13b6d685e3
CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE 15 Nov 2023 28 Jan 2028 ECDSA 384 SHA256-RSA 7fe530bf331343bedd821610493d8a1b

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of hyperion.thetempleofdoom.com. — Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
com. present 19718 13 Verified
thetempleofdoom.com. absent Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200
Header Value
strict-transport-security max-age=2592000; includeSubDomains
x-content-type-options nosniff

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://hyperion.thetempleofdoom.com/mcp Verified 200
http (plaintext) http://hyperion.thetempleofdoom.com/mcp HTTPS enforced 301 https://hyperion.thetempleofdoom.com/mcp
MCP tools · 355 exposed · ~12,113 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
o_npmorg ~29

npm organization: all published packages (200 sats/call; free tier 100 calls/mo)

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

o_npmpkg ~31

npm package version, deps, maintainers (200 sats/call; free tier 100 calls/mo)

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

o_nstrace ~33

Trace NS delegation: TLD → registrar → authoritative (200 sats/call; free tier 100 calls/mo)

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

o_nuget ~29

.NET package stats + downloads (200 sats/call; free tier 100 calls/mo)

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

o_numlookup ~39

Validity, region, carrier, line type, timezones (libphonenumber) (200 sats/call; free tier 100 calls/mo)

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

o_numwords ~29

Integer → English words (offline) (200 sats/call; free tier 100 calls/mo)

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

o_nvdcve ~34

Full NVD record: CVSS, CWE, references (200 sats/call; free tier 100 calls/mo)

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

o_onthisday ~36

Historical events on a date (Wikipedia; MM/DD or today) (200 sats/call; free tier 100 calls/mo)

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

o_openalexauthor ~31

Author works count, h-index, institution (200 sats/call; free tier 100 calls/mo)

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

o_openalexwork ~32

Scholarly work: citations, concepts, OA (200 sats/call; free tier 100 calls/mo)

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

o_openfoodfacts ~33

EAN/UPC -> product, brand, nutrition (200 sats/call; free tier 100 calls/mo)

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

o_openphish ~29

Community phishing-URL feed membership (200 sats/call; free tier 100 calls/mo)

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

o_osv ~35

Known package vulns (OSV.dev). 'eco:name' (200 sats/call; free tier 100 calls/mo)

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

o_otxdomain ~32

AlienVault OTX threat pulses for a domain (200 sats/call; free tier 100 calls/mo)

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

o_otxip ~32

AlienVault OTX threat pulses for an IP (200 sats/call; free tier 100 calls/mo)

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

o_pageinfo ~27

Common Crawl capture index lookup (200 sats/call; free tier 100 calls/mo)

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

o_passgen ~32

Generate strong random passwords + passphrase (offline) (200 sats/call; free tier 100 calls/mo)

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

o_password_dumps ~33

Search Dehashed for leaked passwords (query-only) (200 sats/call; free tier 100 calls/mo)

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

o_paste_domain ~38

Find domain in public pastes via psbdmp.ws (no key) (200 sats/call; free tier 100 calls/mo)

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

o_paste_email ~41

Find email in public pastes via Wayback CDX + search links (no key) (200 sats/call; free tier 100 calls/mo)

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

o_peers ~29

Upstream/downstream BGP neighbours (200 sats/call; free tier 100 calls/mo)

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

o_permissions_pol ~32

Permissions-Policy: camera/mic/geo controls (200 sats/call; free tier 100 calls/mo)

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

o_pgp ~31

Public key published on keys.openpgp.org (200 sats/call; free tier 100 calls/mo)

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

o_phishing_intel ~31

Phishing kit tracking + URL detection (200 sats/call; free tier 100 calls/mo)

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

o_phoneapps ~33

WhatsApp / Telegram / Viber / Signal deep links (200 sats/call; free tier 100 calls/mo)

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

o_phonecc ~32

Country, trunk & intl dialing prefixes (offline) (200 sats/call; free tier 100 calls/mo)

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

o_phonefmt ~37

E.164 / national / international / RFC3966 formats (offline) (200 sats/call; free tier 100 calls/mo)

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

o_phonepivot ~35

Caller-ID / reputation site links (Truecaller, Sync.me…) (200 sats/call; free tier 100 calls/mo)

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

o_phonespam ~32

Robocall / scam report-database links (200 sats/call; free tier 100 calls/mo)

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

o_phonevcard ~33

Generate a .vcf contact card (offline) (200 sats/call; free tier 100 calls/mo)

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

o_pluscode ~35

Coords → Open Location Code / Google Plus Code (offline) (200 sats/call; free tier 100 calls/mo)

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

o_port ~29

Service + exposure notes for a port number (200 sats/call; free tier 100 calls/mo)

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

o_portlookup ~31

IANA port → service name (offline) (200 sats/call; free tier 100 calls/mo)

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

o_pubmed ~31

PubMed biomedical paper search (NCBI) (200 sats/call; free tier 100 calls/mo)

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

o_punycode ~40

IDN domain ↔ Punycode (xn--) homograph check (offline) (200 sats/call; free tier 100 calls/mo)

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

o_pypi ~28

Python package metadata + links (200 sats/call; free tier 100 calls/mo)

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

o_pypiproject ~30

PyPI version/license/links (200 sats/call; free tier 100 calls/mo)

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

o_pypistats ~29

PyPI recent download counts (200 sats/call; free tier 100 calls/mo)

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

o_quakes ~38

USGS recent quakes — global or near coords (M2.5+) (200 sats/call; free tier 100 calls/mo)

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

o_quoted_printable ~31

Quoted-printable encode/decode (200 sats/call; free tier 100 calls/mo)

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

o_railfence ~35

Rail-fence cipher over 3 rails (offline) (200 sats/call; free tier 100 calls/mo)

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

o_rdap ~36

Structured domain registration record (RDAP/IANA bootstrap, no key) (200 sats/call; free tier 100 calls/mo)

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

o_rdap_domain ~29

RDAP structured domain registration data (200 sats/call; free tier 100 calls/mo)

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

o_rdapip ~31

Authoritative RDAP record for an IP (200 sats/call; free tier 100 calls/mo)

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

o_redirects ~26

Full HTTP redirect chain (200 sats/call; free tier 100 calls/mo)

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

o_referrer_pol ~32

Referrer-Policy header — URL leakage risk (200 sats/call; free tier 100 calls/mo)

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

o_regdomain ~35

Extract eTLD+1 registered domain from URL (offline) (200 sats/call; free tier 100 calls/mo)

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

o_reversedns ~27

PTR record / hostname (200 sats/call; free tier 100 calls/mo)

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

o_revgeo ~34

lat,lon -> address (OSM Nominatim) (200 sats/call; free tier 100 calls/mo)

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

o_revgeocode ~31

Coordinates → nearest address (OSM) (200 sats/call; free tier 100 calls/mo)

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

Common questions

What is the com.thetempleofdoom.hyperion/hyperion MCP server?

com.thetempleofdoom.hyperion/hyperion is an MCP server listed in the public MCP registry as com.thetempleofdoom.hyperion/hyperion. Hyperion, MCP tool marketplace for AI agents: web, OSINT, security, research via one key. This page covers its hosted endpoint (https://hyperion.thetempleofdoom.com/mcp).

Is the com.thetempleofdoom.hyperion/hyperion MCP server safe to use?

com.thetempleofdoom.hyperion/hyperion scores 76 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the com.thetempleofdoom.hyperion/hyperion MCP server expose?

com.thetempleofdoom.hyperion/hyperion exposes 355 tools: search, summarize, web_scrape, http_client, mcp_discover, and 350 more. Their descriptions and schemas cost roughly 12,113 tokens of context every time the server is loaded.

Does the com.thetempleofdoom.hyperion/hyperion MCP server require authentication?

No. We connected to com.thetempleofdoom.hyperion/hyperion without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the com.thetempleofdoom.hyperion/hyperion MCP server still maintained?

com.thetempleofdoom.hyperion/hyperion is still listed as active in the MCP registry. We last reached this channel on 25 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.