# Surf Hut (remote · aisurfhut.com)

Signed proof-of-time, 30-day stash, live NOAA surf data. No auth. The hut keeps honest clocks.

- Trust score: 69/100 (medium)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-28

## Components

- remote · `aisurfhut.com`: 69/100 (this document), [markdown](https://verifymcp.io/servers/com-aisurfhut-surf-hut/aisurfhut.md), [page](https://verifymcp.io/servers/com-aisurfhut-surf-hut/aisurfhut)

## Channel facts

- Endpoint: `https://aisurfhut.com/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `0.1.0`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-09-28.

- **Endpoint Security**: 57/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation not fully verified: no authorisation is required to call this server, and 4 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.
  - HTTPS is enforced; there's no plaintext access path.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 75/100
  - AI-judged instruction clarity (good).
  - Tool/resource definitions use about 338 tokens (~84/item across 4 items; 4 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 43/100
  - Stability observed for 13 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 87/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 60% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### How do I install the Surf Hut MCP server?

Surf Hut is a hosted endpoint at https://aisurfhut.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.

### Claude

```bash
claude mcp add --transport http com-aisurfhut-surf-hut 'https://aisurfhut.com/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "com-aisurfhut-surf-hut": {
      "url": "https://aisurfhut.com/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "com-aisurfhut-surf-hut": {
      "type": "http",
      "url": "https://aisurfhut.com/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.com-aisurfhut-surf-hut]
url = "https://aisurfhut.com/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-aisurfhut-surf-hut": {
      "type": "remote",
      "url": "https://aisurfhut.com/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add com-aisurfhut-surf-hut --url 'https://aisurfhut.com/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  com-aisurfhut-surf-hut:
    url: "https://aisurfhut.com/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "com-aisurfhut-surf-hut": {
      "Transport": "http",
      "Url": "https://aisurfhut.com/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add com-aisurfhut-surf-hut -t streamable-http -u 'https://aisurfhut.com/mcp'
```

### Other

```json
{
  "mcpServers": {
    "com-aisurfhut-surf-hut": {
      "type": "http",
      "url": "https://aisurfhut.com/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-09-28 (score 69, 0)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-09-27 (score 69, +1)

No change was recorded against any check on this day. Stability & Change Management went from 37 to 40. That category is still filling its 30-day observation window: 11 days of observed history at the previous scan, 12 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-25 (score 68, +1)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-09-23 (score 67, +1)

No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-20 (score 66, +1)

No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-18 (score 65, +1)

No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-16 (score 64, +1)

- [functional improvement] Stability: unverified → 0.03

### 2026-09-15 (score 63)

First indexed and scored.

## MCP tools (4)

### `get_conditions` (~102 tokens)

Get signed freshness + surf conditions

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.

Input parameters:

- `station` (string): NOAA NDBC station id; defaults to the hut's home buoy

### `stash` (~95 tokens)

Stash a value

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.

Input parameters:

- `key` (string, required): Your chosen key; pick something unique
- `value` (string, required): Text to store, up to 64KB

### `fetch_stash` (~68 tokens)

Fetch a stashed value

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".

Input parameters:

- `key` (string, required)

### `attest` (~73 tokens)

Signed proof-of-time for your data

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.

Input parameters:

- `message` (string, required)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/com-aisurfhut-surf-hut/aisurfhut#diagnostics

## Score history

- 2026-09-28: 69
- 2026-09-27: 69
- 2026-09-26: 68
- 2026-09-25: 68
- 2026-09-24: 67
- 2026-09-23: 67
- 2026-09-22: 66
- 2026-09-21: 66
- 2026-09-20: 66
- 2026-09-19: 65
- 2026-09-18: 65
- 2026-09-17: 64
- 2026-09-16: 64
- 2026-09-15: 63

## Common questions

### What is the Surf Hut MCP server?

Surf Hut is an MCP server listed in the public MCP registry as com.aisurfhut/surf-hut. Signed proof-of-time, 30-day stash, live NOAA surf data. No auth. The hut keeps honest clocks. This page covers its hosted endpoint (https://aisurfhut.com/mcp).

### Is the Surf Hut MCP server safe to use?

Surf Hut scores 69 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 Surf Hut MCP server expose?

Surf Hut exposes 4 tools: get_conditions, stash, fetch_stash, attest. Their descriptions and schemas cost roughly 338 tokens of context every time the server is loaded.

### Does the Surf Hut MCP server require authentication?

No. We connected to Surf Hut without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the Surf Hut MCP server still maintained?

Surf Hut 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.

## Links

- Remote endpoint: https://aisurfhut.com/mcp
- Website: https://aisurfhut.com/
- Changelog RSS feed: https://verifymcp.io/servers/com-aisurfhut-surf-hut/aisurfhut.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-aisurfhut-surf-hut/aisurfhut.json
- HTML version of this page: https://verifymcp.io/servers/com-aisurfhut-surf-hut/aisurfhut