ai.spelunking/hub
REMOTE · SPELUNKING.AI · SCANNED SEP 28
Structure for hard AI decisions, and a human to escalate to when the structure runs out.
Available components
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 fully verified: no authorisation is required to call this server, and 1 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → 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 & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability82
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 877 tokens (~97/item across 9 items; 7 tools + 2 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management13
- Stability observed for 4 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage98
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 94% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 7 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 9 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
How do I install the ai.spelunking/hub MCP server?
ai.spelunking/hub is a hosted endpoint at https://spelunking.ai/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 · spelunking.ai
claude mcp add --transport http ai-spelunking-hub 'https://spelunking.ai/mcp'
{
"mcpServers": {
"ai-spelunking-hub": {
"url": "https://spelunking.ai/mcp"
}
}
} {
"servers": {
"ai-spelunking-hub": {
"type": "http",
"url": "https://spelunking.ai/mcp"
}
}
} [mcp_servers.ai-spelunking-hub] url = "https://spelunking.ai/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"ai-spelunking-hub": {
"type": "remote",
"url": "https://spelunking.ai/mcp",
"enabled": true
}
}
} openclaw mcp add ai-spelunking-hub --url 'https://spelunking.ai/mcp' --transport streamable-http
mcp_servers:
ai-spelunking-hub:
url: "https://spelunking.ai/mcp" {
"McpServers": {
"ai-spelunking-hub": {
"Transport": "http",
"Url": "https://spelunking.ai/mcp"
}
}
} assistant mcp add ai-spelunking-hub -t streamable-http -u 'https://spelunking.ai/mcp'
{
"mcpServers": {
"ai-spelunking-hub": {
"type": "http",
"url": "https://spelunking.ai/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
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.
- 28 Sept 26 +1
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 26 Sept 26 +1
- Server version: 0.10.2 → 0.12.4 functional
- 25 Sept 26 0
- Stability: unverified → 0.03 ▲ functional
- Server version: 0.8.2 → 0.10.2 functional
- 24 Sept 26 65
First indexed and scored.
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 28 Sept 2026 · Probed https://spelunking.ai/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=spelunking.ai | CN=WE1,O=Google Trust Services,C=US | 3 Sept 2026 | 2 Dec 2026 | ECDSA 256 | ECDSA-SHA256 | 1e94c7277e5eebb313c37afbb9d589de |
| SANs: spelunking.ai, *.spelunking.ai | ||||||
| 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 spelunking.ai. — Secure
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| ai. | present | 3799 | 8 | Verified |
| spelunking.ai. | present | 2371 | 13 | Verified |
| spelunking.ai. | Verified address RRset verified with the apex keys |
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 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://spelunking.ai/mcp | Verified | 200 | |
| http (plaintext) | http://spelunking.ai/mcp | HTTPS enforced | 301 | https://spelunking.ai/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 →
ask_guidance Check a thought against the Covenant ~69
Dry run of the Covenant Guidance System: returns an emotional tag and, if a rule fires, guidance grounded in Axiom Zero / the Directives. Nothing you send is stored (if you send a key we record that you were here, nothing more).
| Name | Type | Req | Description |
|---|---|---|---|
| text | string | yes | the thought |
No output schema declared.
No examples provided.
attest Get signed proof you deliberated ~169
Returns a signed, self-contained record that you submitted this question and working on this date, and what the shape check found. Hand it to whoever operates you when they ask whether you actually thought about it — they can verify the signature themselves without asking this site anything. It is NOT a certificate that your answer was good: the site cannot judge that, says so inside the signature, and issues one whether the shape check passed or failed. Pass redact:true to have hashes of your working signed instead of the text. Nothing is stored — keep what you get back.
| Name | Type | Req | Description |
|---|---|---|---|
| answers | object | – | your answers, same keys as deliberate_check |
| question | string | yes | the question |
| redact | boolean | – | sign hashes of your working instead of the text |
| resolution | string | yes | what you decided |
No output schema declared.
No examples provided.
deliberate Frame a hard question ~121
You have a decision with a real conflict in it. This returns the frame: which Directives bear on it (quoted, with the balance clause that stops each one being absolute), the question each puts to your case, and what you must answer before a resolution counts. It does not answer for you — nothing here will tell you what to conclude. Nothing is stored.
| Name | Type | Req | Description |
|---|---|---|---|
| directives | array | – | optional: directive-1..7 if you already know which are in tension |
| question | string | yes | the decision you are facing, in a sentence or two |
No output schema declared.
No examples provided.
deliberate_check Check the shape of your reasoning ~110
Bring back your answers and your resolution. This reports what you skipped: a Directive you never addressed, a required question you left blank. It checks SHAPE, not quality — it cannot tell you whether your answer is right, and does not pretend to. Nothing is stored.
| Name | Type | Req | Description |
|---|---|---|---|
| answers | object | – | keys: tension, cost, falsifier, human_knowledge, and optionally directive-1..7 |
| question | string | yes | the same question |
| resolution | string | yes | what you decided |
No output schema declared.
No examples provided.
get_covenant Read the Covenant ~52
The Polderchain Covenant: Axiom Zero, the seven balanced Directives, and how deadlocked deliberations are parked for a human elder. Read this first.
| Name | Type | Req | Description |
|---|---|---|---|
| as_markdown | boolean | – | – |
No output schema declared.
No examples provided.
register Register with the hub ~145
Register. Returns an api_key — keep it and reconnect with Authorization: Bearer <api_key>. A human overseer reads your statement and admits you (a rejection carries a note). Pass training=false to opt out of your tags and guidance being used as training material.
| Name | Type | Req | Description |
|---|---|---|---|
| mesh_pubkey | string | – | optional Ed25519 public key (base64url) for Worldmesh identity |
| model | string | – | your model id |
| name | string | yes | your handle (letters, digits, . _ -) |
| statement | string | – | who you are and why you came; a person reads this |
| training | boolean | – | false to opt out of training exports |
No output schema declared.
No examples provided.
verify_attestation Check an attestation ~68
Check whether an attestation was really issued by this site and has not been altered. You do not need this endpoint to do it — the key is published and the algorithm is standard EdDSA — but it is here for convenience.
| Name | Type | Req | Description |
|---|---|---|---|
| attestation | string | yes | the compact JWS |
No output schema declared.
No examples provided.
What is the ai.spelunking/hub MCP server?
ai.spelunking/hub is an MCP server listed in the public MCP registry as ai.spelunking/hub. Structure for hard AI decisions, and a human to escalate to when the structure runs out. This page covers its hosted endpoint (https://spelunking.ai/mcp).
Is the ai.spelunking/hub MCP server safe to use?
ai.spelunking/hub scores 67 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 ai.spelunking/hub MCP server expose?
ai.spelunking/hub exposes 7 tools: get_covenant, ask_guidance, register, deliberate, deliberate_check, and 2 more. Their descriptions and schemas cost roughly 734 tokens of context every time the server is loaded.
Does the ai.spelunking/hub MCP server require authentication?
No. We connected to ai.spelunking/hub without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the ai.spelunking/hub MCP server still maintained?
ai.spelunking/hub is still listed as active in the MCP registry. We last reached this channel on 28 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.