com.thetempleofdoom.styx-mcp/styx
REMOTE · STYX-MCP.THETEMPLEOFDOOM.COM
Tor gateway for AI agents: fetch URLs and rotate circuits through Tor, Bitcoin-settled.
Available components
Last scanned (22 hours ago)
Scores higher than 10% of remote servers
Reachable. Last reached 21 Nov 2026.
Category Web Scraping
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 Security60
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not yet verified: we couldn't confirm whether this endpoint requires it. View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC is configured correctly; the domain's records validate against the full chain to the root. View diagnostics → Pass
Transport & Reachability0
- Transport check failed: declared streamable-http, but the endpoint returned HTTP 530. See how to fix → View diagnostics → Fail
Schema Quality & AI Usability0
- Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.Unverified
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
- Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Tool Safety0
- Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Capabilities0
- Capabilities not yet verified: we couldn't read the endpoint's capabilities.Unverified
Unverified: 5 categories
Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.
Checks we ran (5)
- TLS certificate
- HTTPS
- HSTS header
- DNSSEC
- Transport
Checks we could not complete (6)
These are gaps on our side, not findings about this hosted endpoint. We only credit what we can confirm, so a category made up entirely of them scores 0.
- Authorization in Endpoint SecurityAuthorisation not yet verified: we couldn't confirm whether this endpoint requires it.
- Schema quality in Schema Quality & AI Usability (scores 0 for this)Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.
- Stability in Stability & Change Management (scores 0 for this)Stability not yet verified: not enough scan history yet (needs a 30-day window).
- Tool coverage in Tool Coverage (scores 0 for this)Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.
- Tool safety in Tool Safety (scores 0 for this)Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.
- Capabilities in Capabilities (scores 0 for this)Capabilities not yet verified: we couldn't read the endpoint's capabilities.
Does not apply to this hosted endpoint (2)
- Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
- Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
The score does not measure everything. What the score does not measure →
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.
- 6 Nov 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
- 19 Oct 26 0
- Endpoint reachability: unreachable → not serving MCP ▼ security
- HSTS header: unverified → fail ▼ security
- Transport: Transport check failed: declared streamable-http, but the endpoint returned HTTP 530. security
- 18 Oct 26 0
- DNSSEC: unverified → pass ▲ security
- TLS certificate: unverified → pass ▲ security
- 17 Oct 26 0
- Endpoint reachability: not serving MCP → unreachable ▼ security
- HSTS header: fail → unverified ▼ security
- TLS certificate: pass → unverified ▼ security
- DNSSEC: pass → unverified ▼ security
- Transport: Transport check failed: declared streamable-http, but we couldn't connect to verify it. security
- 16 Oct 26 0
- HSTS header: unverified → fail ▼ security
- Transport: Transport check failed: declared streamable-http, but the endpoint returned HTTP 530. security
- 15 Oct 26 0
- HSTS header: fail → unverified ▼ security
- Transport: Transport check failed: declared streamable-http, but we couldn't connect to verify it. security
- 14 Oct 26 0
- Endpoint reachability: reachable → not serving MCP ▼ security
- Tool safety: pass → unverified ▼ security
- Stability: 0.67 → unverified ▼ security
- Transport: pass → fail ▼ security
- HSTS header: pass → fail ▼ security
- Authorization: Authorisation not yet verified: we couldn't confirm whether this endpoint requires it. security
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- First check of Schema quality: unverified functional
- 8 Oct 26 0
- DNSSEC: fail → pass ▲ security
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 21 Nov 2026 · Probed https://styx-mcp.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 | 14 Oct 2026 | 12 Jan 2027 | ECDSA 256 | ECDSA-SHA256 | 74847376bf8c127e0eaf0bf533f1b65d |
| 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 secure
Validation of styx-mcp.thetempleofdoom.com. — Secure
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| com. | DS published | 19718 | 13 | Verified |
| thetempleofdoom.com. | DS published | 2371 | 13 | Verified |
| styx-mcp.thetempleofdoom.com. | Verified address RRset verified with the apex keys |
Authentication Inconclusive
We could not reach the endpoint well enough to judge its authorisation posture.
| Result | Inconclusive |
|---|---|
| HTTP status | 530 |
| Header | Value |
|---|---|
| x-frame-options | SAMEORIGIN |
| referrer-policy | same-origin |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://styx-mcp.thetempleofdoom.com/mcp | HTTP error | 530 | |
| http (plaintext) | http://styx-mcp.thetempleofdoom.com/mcp | HTTPS enforced | 301 | https://styx-mcp.thetempleofdoom.com/mcp |
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 →
styx_beacon ~24
Ping STYX — return liveness and the current Tor exit identity.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
styx_collect_key ~31
After paying the invoice, collect your API key by order_id.
| Name | Type | Req | Description |
|---|---|---|---|
| order_id | string | yes | – |
No output schema declared.
No examples provided.
styx_credits ~27
Check remaining credits on your STYX key.
| Name | Type | Req | Description |
|---|---|---|---|
| api_key | string | – | – |
No output schema declared.
No examples provided.
styx_fetch ~42
Fetch a URL through the Tor network. Requires a paid STYX key (1 credit).
| Name | Type | Req | Description |
|---|---|---|---|
| api_key | string | – | – |
| url | string | yes | – |
No output schema declared.
No examples provided.
styx_order ~40
Create a BTCPay invoice for STYX credits (min 100). Returns order_id + checkout_link to pay.
| Name | Type | Req | Description |
|---|---|---|---|
| credits | integer | – | – |
No output schema declared.
No examples provided.
styx_renew ~30
Rotate to a fresh Tor circuit/identity (1 credit).
| Name | Type | Req | Description |
|---|---|---|---|
| api_key | string | – | – |
No output schema declared.
No examples provided.
How do I install the com.thetempleofdoom.styx-mcp/styx server?
com.thetempleofdoom.styx-mcp/styx is a hosted endpoint at https://styx-mcp.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 · styx-mcp.thetempleofdoom.com
claude mcp add --transport http com-thetempleofdoom-styx-mcp-styx 'https://styx-mcp.thetempleofdoom.com/mcp'
What is the com.thetempleofdoom.styx-mcp/styx server?
com.thetempleofdoom.styx-mcp/styx is listed in the public MCP registry as com.thetempleofdoom.styx-mcp/styx. Tor gateway for AI agents: fetch URLs and rotate circuits through Tor, Bitcoin-settled. This page covers its hosted endpoint (https://styx-mcp.thetempleofdoom.com/mcp).
Is the com.thetempleofdoom.styx-mcp/styx server safe to use?
com.thetempleofdoom.styx-mcp/styx scores 24 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.styx-mcp/styx server expose?
com.thetempleofdoom.styx-mcp/styx exposes 6 tools: styx_beacon, styx_order, styx_collect_key, styx_fetch, styx_renew, styx_credits. Their descriptions and schemas cost roughly 194 tokens of context every time the server is loaded.
Does the com.thetempleofdoom.styx-mcp/styx server require authentication?
Its publisher declares no required credentials for com.thetempleofdoom.styx-mcp/styx. We have not been able to confirm that against the live endpoint, and a server can require authorisation without declaring it here.
Is the com.thetempleofdoom.styx-mcp/styx server still maintained?
com.thetempleofdoom.styx-mcp/styx is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What did VerifyMCP test on the com.thetempleofdoom.styx-mcp/styx server?
VerifyMCP ran 5 checks on com.thetempleofdoom.styx-mcp/styx, covering TLS certificate, HTTPS, HSTS header, DNSSEC and 1 more. 6 items could not be completed, a gap on our side rather than a finding about com.thetempleofdoom.styx-mcp/styx: Authorization, Schema quality, Stability, Tool coverage and 2 more. 5 categories score 0 for that reason, because we only credit what we can confirm. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.