com.thetempleofdoom.draco/draco
REMOTE · DRACO.THETEMPLEOFDOOM.COM
Coding & security oracle grounded in 1855 real books. Cited answers via MCP.
Available components
Last scanned (18 minutes ago)
Scores higher than 10% of remote servers
Reachable. Last reached 5 Nov 2026.
Category Code Search and Documentation
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.
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.
- 27 Oct 26 −2
- HSTS header: pass → fail ▼ security
- 26 Oct 26 +2
- HSTS header: fail → pass ▲ security
- 22 Oct 26 −2
- HSTS header: pass → fail ▼ security
- 21 Oct 26 +2
- HSTS header: fail → pass ▲ security
- 18 Oct 26 0
- Endpoint reachability: unreachable → not serving MCP ▼ security
- HSTS header: unverified → fail ▼ security
- DNSSEC: unverified → pass ▲ security
- TLS certificate: unverified → pass ▲ security
- Transport: Transport check failed: declared streamable-http, but the endpoint returned HTTP 530. 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
- 14 Oct 26 −46
- Endpoint reachability: reachable → not serving MCP ▼ security
- Stability: 0.37 → unverified ▼ security
- Tool safety: pass → 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
- 13 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes.
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 5 Nov 2026 · Probed https://draco.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 draco.thetempleofdoom.com. — Secure
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| thetempleofdoom.com. | present | 2371 | 13 | Verified |
| draco.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://draco.thetempleofdoom.com/mcp | HTTP error | 530 | |
| http (plaintext) | http://draco.thetempleofdoom.com/mcp | HTTPS enforced | 301 | https://draco.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 →
draco_ask ~48
Ask DRACO a coding or security question. Answers are grounded in hundreds of real programming and hacking books, with [n] citations and source titles.
| Name | Type | Req | Description |
|---|---|---|---|
| question | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
draco_search ~39
Search DRACO's book library (BM25) for passages matching a topic.
| Name | Type | Req | Description |
|---|---|---|---|
| k | integer | – | – |
| query | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
draco_status ~16
DRACO health + library size.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
How do I install the com.thetempleofdoom.draco/draco MCP server?
com.thetempleofdoom.draco/draco is a hosted endpoint at https://draco.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 · draco.thetempleofdoom.com
claude mcp add --transport http com-thetempleofdoom-draco-draco 'https://draco.thetempleofdoom.com/mcp'
What is the com.thetempleofdoom.draco/draco MCP server?
com.thetempleofdoom.draco/draco is an MCP server listed in the public MCP registry as com.thetempleofdoom.draco/draco. Coding & security oracle grounded in 1855 real books. Cited answers via MCP. This page covers its hosted endpoint (https://draco.thetempleofdoom.com/mcp).
Is the com.thetempleofdoom.draco/draco MCP server safe to use?
com.thetempleofdoom.draco/draco 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.draco/draco MCP server expose?
com.thetempleofdoom.draco/draco exposes 3 tools: draco_ask, draco_search, draco_status. Their descriptions and schemas cost roughly 103 tokens of context every time the server is loaded.
Does the com.thetempleofdoom.draco/draco MCP server require authentication?
Its publisher declares no required credentials for com.thetempleofdoom.draco/draco. 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.draco/draco MCP server still maintained?
com.thetempleofdoom.draco/draco is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.