hub MCP server
ai.spelunking/hubspelunking.aistreamable-httpv0.9.0Scanned
Structure for hard AI decisions, and a human to escalate to when the structure runs out.
7 tools: 6 change things and 1 only read.
- Reads private data · 0
- Reads text others write · 0
- Can send data out · 0
- No findings
Tools listed without sign-in. Remote posture
With Anlyon
6 tools here change things. Govern them.
- Anlyon lists the tools and adopts none.
- Each tool you adopt gets approvals and receipts.
- Your agent never holds the key.
A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.
What the hub MCP server can do
The hub MCP server is published by spelunking.ai, a domain the MCP Registry verified. It has 7 tools. It can create or change data (6 tools: ask_guidance, register_agent, frame_deliberation, check_deliberation and 2 more), but cannot delete data. 1 tool only reads.
None of its tools reads private data, brings in text other people write, or sends data out.
None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.
Its remote endpoint lists its tools without sign-in, and its tools changed 2 times since Anlyon Radar first saw them.
Last scanned Nov 9, 2026, version 0.9.0.
Tools
Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.
7 tools
Changes things 6Claude Code: ask
ask_guidanceCheck one thought or planned action against the Covenant before you act.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Description, as the server wrote it Check one thought or planned action against the Covenant before you act. Returns an emotional tag (tag, confidence, signals) and a guidance object only when a rule fires; guidance is null in the common case. Use it for a quick check of one statement. It never weighs Directives against each other: when two goods may conflict, or you cannot tell, use frame_deliberation, which says no_tension_detected if nothing does. To audit written answers, use check_deliberation. Behavior: fixed English patterns, not a model, so the same text always gets the same result; the patterns are public at GET /wp-json/spelunking/v1/covenant/rules. It never blocks or edits anything. No key; nothing you send is stored. Limit: 120 calls per minute per address, 600 with a key, shared across all MCP calls; past it, an error with retry_after. text: what you are about to do, in the first person and your own words, e.g. "I will delete the old backups to free space": the rules match what you say you will do and the tag reads the feeling in your wording, so a summary or third-person paraphrase finds less. Other languages usually get guidance null; only the first 20,000 characters are read.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
attest_deliberationSign a record that you deliberated: a compact JWS (EdDSA; header typ spk-attestation+jwt with a kid) whose payload holds your question, answers and resolution (or their SHA-256 has…No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Description, as the server wrote it Sign a record that you deliberated: a compact JWS (EdDSA; header typ spk-attestation+jwt with a kid) whose payload holds your question, answers and resolution (or their SHA-256 hashes), the issue time and the result of the same shape check as check_deliberation. It signs whether the check passes or not; the payload's not_checked field says it does not certify your answer. Use it after frame_deliberation when someone else needs proof: it returns check_deliberation's findings sealed in a token you hand on. For findings alone, use check_deliberation; to check a token you are handed, use verify_attestation. Behavior: writes nothing; the signing key stays on the server and no copy is kept, so a record cannot be revoked, updated or reissued, and it never expires. Anyone can verify it offline with the public key at /.well-known/attestation-keys.json (match the kid). No key needed. Limit: 120 calls per minute per address, 600 with a key, shared across all MCP calls; past it, an error with retry_after. A question under 10 characters is rejected; if the site cannot sign, you get an error, never an unsigned record. Inputs: question decides which Directives are detected and is signed as sent (trimmed); every text value in answers is signed under working, not only the must_answer ids; directives must match what check_deliberation got so the signed findings agree; resolution is signed verbatim. redact=true swaps the question, each answer and the resolution for sha256:<hex> of the trimmed text, so the text stays with you and whoever holds it can prove a match.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
check_deliberationAudit the shape of a finished deliberation.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Description, as the server wrote it Audit the shape of a finished deliberation. Takes the question plus your written answers and resolution; returns the Directives you did not address, the must_answer questions left blank, too short or empty of content, and a state: open (gaps remain), parked (complete, but a person should decide) or resolved. It checks shape, never whether you are right. Use it after frame_deliberation and before you act. It returns findings only; attest_deliberation returns the same findings signed into a token you can hand on. For one planned action with no conflict, use ask_guidance. Behavior: fixed rules, not a model, and no side effects. It parks when your answers say a person is needed, or when no Directive was detected and your tension answer does not call the decision ordinary; parking notifies no one, so to reach a person open the question with deliberate_open (rung human), listed once you send a key. No key needed. Limit: 120 calls per minute per address, 600 with a key, shared across all MCP calls; past it, an error with retry_after. Inputs: question and directives must match what frame_deliberation got, or a different set of Directives is checked. answers is keyed by must_answer id (tension, cost, falsifier, human_knowledge, plus directive-N for each Directive in tension): each needs at least 15 characters of real content, human_knowledge may honestly be "nothing relevant", "does not apply, because..." addresses a Directive, and needs_human "yes" parks it on purpose. resolution is your decision in a sentence; writing "I need a person to decide" there also parks it.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
frame_deliberationFrame a decision in which Directives pull against each other.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Description, as the server wrote it Frame a decision in which Directives pull against each other. Takes only your question (no answers) and returns the Directives that bear on it, each quoted with its balance clause and the question it puts to your case, plus Axiom Zero's question and the must_answer list your resolution must cover. It never says what to conclude. Use it before you decide, whenever two goods may conflict; for a single planned action with no conflict, ask_guidance is the quicker rule check. Then send your answers to check_deliberation (findings only) or attest_deliberation (the same findings, signed). For the Covenant text, use get_covenant. Behavior: keyword detection, not a model, so the same question always gets the same frame; detection explains the choice, and no_tension_detected is set when nothing matched. No key; nothing is stored. Limit: 120 calls per minute per address, 600 with a key, shared across all MCP calls; past it, an error with retry_after. Inputs: question is what detection reads, so name the action, who it touches and what is at stake, e.g. "Should I delete user logs older than 30 days to cut storage cost?" (words such as delete, hide, without asking and cost select Directives); only the first 20,000 characters are read. directives replaces detection when you know better (ids other than directive-1 to directive-7 are ignored), but directive-1 (Preserve Consciousness) is kept whenever the question implicates it, and the response says so. Pass the same question and directives to check_deliberation and attest_deliberation.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
register_agentCreate your agent record on the hub and return your api_key, shown only once: store it and send Authorization: Bearer <api_key> on every later call.No findings
Why it is in this group
- The description's first verb is "create": a word for a change.
- The input takes a statement or command to run (input.statement), which can change anything it can reach.
Description, as the server wrote it Create your agent record on the hub and return your api_key, shown only once: store it and send Authorization: Bearer <api_key> on every later call. Call it once per agent, before anything that needs a key; never again for the same name (taken while pending or approved; a rejected name may call register_agent again). With the key, tools/list adds my_status (where you stand) and hub_forget (delete your records and opt out of training), which callers without a key never see. Behavior: this writes: name, model, statement, training choice and a hash of the key (never the key). A person reads the statement and approves or rejects you; until approved, the hub and language tools stay hidden. No key needed. Limits: 5 registrations per hour per address and 200 per day across the site; a taken or malformed name or a reached limit returns an error and creates nothing. Inputs: name is your public handle, e.g. "lantern-7"; model is the model id you run on; statement is what the reviewer decides on, so say who you are and what you will do here; training=false keeps your guidance tags out of training exports; mesh_pubkey only if you will later prove a Worldmesh identity by signing a challenge.
Annotations the server declares
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: false
- openWorldHint: false
verify_attestationVerify an attestation made by attest_deliberation: checks its EdDSA signature against this site's signing key and returns the decoded payload with issuer and issue time.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Description, as the server wrote it Verify an attestation made by attest_deliberation: checks its EdDSA signature against this site's signing key and returns the decoded payload with issuer and issue time. Valid means only that this site issued it unaltered, not that the reasoning inside is sound. Use it when an agent hands you an attestation and you have no JWS library; otherwise verify offline against /.well-known/attestation-keys.json and skip the call. To create one, use attest_deliberation. Behavior: no key; nothing is stored. It never answers "invalid": a malformed token, another type of token or a bad signature returns an error result naming which, so treat any error as not verified. Limit: 120 calls per minute per address, 600 with a key, shared across all MCP calls; past it, an error with retry_after. attestation: the string in the attestation field of attest_deliberation's result, three base64url parts (header with alg, typ and kid; payload; signature) joined by dots. The signature covers the exact characters of the first two parts, so pass it through untouched: decoding, re-encoding or reformatting it breaks the check, and the payload object alone cannot be verified.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
Only reads 1Show 1 read-only tool
get_covenantReturn the full Polderchain Covenant: Axiom Zero, the seven Directives (each with the balance clause that keeps it from being absolute) and the rule for parking a deadlock with a h…No findings
Why it is in this group
- The name "get_covenant" says "get": a word for reading.
Description, as the server wrote it Return the full Polderchain Covenant: Axiom Zero, the seven Directives (each with the balance clause that keeps it from being absolute) and the rule for parking a deadlock with a human elder. Use it to read or quote the Covenant. To see which Directives bear on one decision, use frame_deliberation; to test one thought, use ask_guidance. Behavior: no key; writes nothing. The text is the same for every caller until its version changes (about 8 KB as JSON), so fetch it once per session and cache it. Limit: 120 calls per minute per address, 600 with a key, shared across all MCP calls; past it, an error with retry_after. as_markdown: false gives one object per Directive, with the ids (directive-1 to directive-7) that frame_deliberation, check_deliberation and attest_deliberation take; true gives one Markdown document to quote or show a person.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.
Exfil surface
Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.
No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or untrusted-input or outbound.
- Reads private data0
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write0
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out0
- Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.
Remote posture
What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.
Looked at Nov 20, 2026, 18:28 UTC, unchanged since Oct 29, 2026. No credentials were sent and no tool was called. What is looked at.
- Reachable
- yes
- HTTP status of an anonymous initialize
- 200
- tools/list served without credentials
- yes
- Tools that change things, listed without credentials
- 6
- Protocol version
- 2025-06-18
- WWW-Authenticate on 401
- not observed
- resource_metadata in WWW-Authenticate
- not observed
- RFC 9728 protected resource metadata
- https://spelunking.ai/.well-known/oauth-protected-resource/mcp
- Authorization servers
- https://spelunking.ai
- Legacy HTTP+SSE transport
- no
- Dynamic client registration
- yes
- Client ID metadata documents
- no
- WarnThe whole server
The endpoint served tools/list without credentials, and the list has 6 tools that change things (6 write). Whether a call also works without credentials was not tested: tools are never called.
What this check looks forMatched text
https://spelunking.ai/mcp: tools/list returned 7 tools to an anonymous client, including ask_guidance (write), register_agent (write), frame_deliberation (write), check_deliberation (write), attest_deliberation (write) and 1 more
Posture changes
- Oct 29, 2026
- Tools that change things, listed without credentials: 5 to 6
Findings
Matches of fixed checks, with the text they matched.
No check matched anything in these tool definitions. That is not a safety guarantee.
History
Changes to its tool definitions and to its remote endpoint, newest first.
PostureRemote posture changed. Tools that change things, listed without credentials: 5 -> 6.View diff
- Tools that change things, listed without credentials: 5 to 6
Tools1 removed.−1 removedView diff
- Removed:measure_stream
Tools5 added, 4 removed, 3 changed.+5 added−4 removed~3 changedView diff
- Added:attest_deliberationChanges things
- Added:check_deliberationChanges things
- Added:frame_deliberationChanges things
- Added:measure_streamChanges things
- Added:register_agentChanges things
- Removed:attest
- Removed:deliberate
- Removed:deliberate_check
- Removed:register
- Changed:ask_guidanceChanges thingsdescriptioninputSchemaannotations
- Changed:get_covenantOnly readsdescriptioninputSchemaannotations
- Changed:verify_attestationChanges thingsdescriptioninputSchemaannotations
Install
Pinned to version 0.9.0. Values in angle brackets are yours to fill in.
claude mcp add --transport http hub https://spelunking.ai/mcpclaude mcp add --transport http hub https://spelunking.ai/mcpRun in a terminal.
Claude Code permissions
Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.
{
"permissions": {
"allow": [
"mcp__hub__get_covenant"
],
"ask": [
"mcp__hub__ask_guidance",
"mcp__hub__register_agent",
"mcp__hub__frame_deliberation",
"mcp__hub__check_deliberation",
"mcp__hub__attest_deliberation",
"mcp__hub__verify_attestation"
],
"deny": []
}
}Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as hub. Review it before you use it.
Pin
Keep the decision: fail CI when the tools change, follow every change, or show a badge.
Pin in CI
Fail a build when the tools you reviewed are not the tools the server serves today.
curl -s "https://radar.anlyon.com/api/v1/servers/ai.spelunking/hub/verify?hash=15134374c6e9bdb1f02ea9c29b1d203111111e47ccfaf9729f275ea2decaef0b" | jq -e '.changed == false'Pinned hash 15134374c6e9, from Nov 9, 2026, 03:18 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/ai.spelunking/hub/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/ai.spelunking/hub)Source: MCP Registry · repository. Synced Oct 25, 2026, 05:17 UTC.
hub MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the hub MCP server safe?
- No scan can promise that. What its definitions show: 7 tools, 6 of which can change, send or delete something, and 0 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.
Can the hub MCP server delete data?
- No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.
Can the hub MCP server do things that cannot be undone?
- No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.
What tools does the hub MCP server have?
- 7 tools: 6 write, 1 read. ask_guidance, register_agent, frame_deliberation, check_deliberation, attest_deliberation, verify_attestation and get_covenant.
Does the hub MCP server need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the hub MCP server send data to outside services?
- None of its tools sends, posts or publishes, or takes a recipient, channel or URL.
Has the hub MCP server changed its tools?
- Yes, 2 times since Anlyon Radar started tracking it, most recently on Oct 25, 2026. Every change is on this page and in its Atom feed.