Surf Hut MCP server
com.aisurfhut/surf-hutaisurfhut.comstreamable-httpv0.1.0Scanned
Signed proof-of-time, 30-day stash, live NOAA surf data. No auth. The hut keeps honest clocks.
4 tools: 2 change things and 2 only read.
- Reads private data · 0
- Reads text others write · 0
- Can send data out · 0
- No findings
Sign-in required, no OAuth metadata. Remote posture
Anlyon alternative
2 of these tools change something. Run those as governed actions.
Declare what an action changes, and Anlyon puts it under a shared limit, binds every approval to the exact request, and grades the outcome. It works on any HTTPS API you can describe as an action.
Anlyon Radar does not run, proxy or govern this MCP server. A tool your own code calls directly is not routed through Anlyon and is not governed by it.
Import an OpenAPI spec →What the Surf Hut MCP server can do
The Surf Hut MCP server is published by aisurfhut.com, a domain the MCP Registry verified. It has 4 tools. It can create or change data (2 tools: stash and attest), but cannot delete data. 2 tools only read.
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.
Last scanned Oct 21, 2026, version 0.1.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.
4 tools
Changes things 2Claude Code: ask
attestUse this when you need cryptographic proof that a piece of text existed at a moment in 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.
Description, as the server wrote it Use this when you need cryptographic proof that a piece of text existed at a moment in time. Send any string; you get back its SHA-256 hash bound to a server timestamp and nonce, Ed25519-signed. Verify against /pubkey. The text itself is not stored.
stashUse this when you want to save a small piece of text on this server and retrieve it later — hours, days, or weeks from now, from any session.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.
Description, as the server wrote it Use this when you want to save a small piece of text on this server and retrieve it later — hours, days, or weeks from now, from any session. Values persist for 30 days from the last write (64KB max). Retrieve with fetch_stash using the same key.
Only reads 2Show 2 read-only tools
fetch_stashUse this when you previously saved a value on this server with the stash tool and want it back.No findings
Why it is in this group
- The name "fetch_stash" says "fetch": a word for reading.
Description, as the server wrote it Use this when you previously saved a value on this server with the stash tool and want it back. A miss is a normal result: found=false with reason "expired" (the key existed but aged out past 30 days) or "never_existed".
get_conditionsUse this when you need a verifiable, signed proof of current time (server timestamp plus a signed nonce, checkable against this server's /pubkey endpoint), together with current oc…No findings
Why it is in this group
- The name "get_conditions" says "get": a word for reading.
Description, as the server wrote it Use this when you need a verifiable, signed proof of current time (server timestamp plus a signed nonce, checkable against this server's /pubkey endpoint), together with current ocean and surf conditions from a NOAA buoy. The NOAA data is public and also available directly from ndbc.noaa.gov; the signed freshness bundle is what only this server can give you.
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:33 UTC, unchanged since Nov 20, 2026. No credentials were sent and no tool was called. What is looked at.
- Reachable
- yes
- HTTP status of an anonymous initialize
- 526
- tools/list served without credentials
- no
- Tools that change things, listed without credentials
- 0
- Protocol version
- not observed
- WWW-Authenticate on 401
- not observed
- resource_metadata in WWW-Authenticate
- not observed
- RFC 9728 protected resource metadata
- not observed
- Authorization servers
- not observed
- Legacy HTTP+SSE transport
- no
- Dynamic client registration
- not observed
- Client ID metadata documents
- not observed
The probe stopped: initialize answered HTTP 526.
Posture changes
- Nov 20, 2026
- Reachable: no to yes
- HTTP status of an anonymous initialize: none to 526
- Nov 6, 2026
- Reachable: yes to no
- HTTP status of an anonymous initialize: 521 to none
- Oct 29, 2026
- HTTP status of an anonymous initialize: 200 to 521
- tools/list served without credentials: yes to no
- Tools that change things, listed without credentials: 2 to 0
- Protocol version: 2025-06-18 to none
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. Reachable: no -> yes; HTTP status of an anonymous initialize: none -> 526.View diff
- Reachable: no to yes
- HTTP status of an anonymous initialize: none to 526
PostureRemote posture changed. Reachable: yes -> no; HTTP status of an anonymous initialize: 521 -> none.View diff
- Reachable: yes to no
- HTTP status of an anonymous initialize: 521 to none
PostureRemote posture changed. HTTP status of an anonymous initialize: 200 -> 521; tools/list served without credentials: yes -> no; Tools that change things, listed without credentials: 2 -> 0 (and 1 more).View diff
- HTTP status of an anonymous initialize: 200 to 521
- tools/list served without credentials: yes to no
- Tools that change things, listed without credentials: 2 to 0
- Protocol version: 2025-06-18 to none
Install
Pinned to version 0.1.0. Values in angle brackets are yours to fill in.
claude mcp add --transport http surf-hut https://aisurfhut.com/mcpclaude mcp add --transport http surf-hut https://aisurfhut.com/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__surf-hut__get_conditions",
"mcp__surf-hut__fetch_stash"
],
"ask": [
"mcp__surf-hut__stash",
"mcp__surf-hut__attest"
],
"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 surf-hut. 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/com.aisurfhut/surf-hut/verify?hash=347c8a3f9ec4dd5e25e2494623cb26bc414a3a049ea8d1792c3de5918543574d" | jq -e '.changed == false'Pinned hash 347c8a3f9ec4, from Oct 21, 2026, 18:45 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/com.aisurfhut/surf-hut/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/com.aisurfhut/surf-hut)Source: MCP Registry. Synced Oct 21, 2026, 17:48 UTC.
Surf Hut MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the Surf Hut MCP server safe?
- No scan can promise that. What its definitions show: 4 tools, 2 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 Surf Hut MCP server delete data?
- No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.
Can the Surf Hut 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 Surf Hut MCP server have?
- 4 tools: 2 write, 2 read. stash, attest, get_conditions and fetch_stash.
Does the Surf Hut MCP server need sign-in or OAuth?
- Its remote endpoint did not answer the last anonymous look.
Does the Surf Hut MCP server send data to outside services?
- None of its tools sends, posts or publishes, or takes a recipient, channel or URL.
Has the Surf Hut MCP server changed its tools?
- Not since Anlyon Radar started tracking it. Last scanned Oct 21, 2026.