# Surfing Dog Inbox (remote · inbox.surfingdog.ai)

Message, ask for a quote or book a call with Surfing Dog, through its open-source inbox.

- Trust score: 66/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-29

## Components

- remote · `inbox.surfingdog.ai`: 66/100 (this document), [markdown](https://verifymcp.io/servers/ai-surfingdog-inbox/inbox.md), [page](https://verifymcp.io/servers/ai-surfingdog-inbox/inbox)

## Channel facts

- Endpoint: `https://inbox.surfingdog.ai/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-29.

- **Endpoint Security**: 63/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation check failed: no authorisation is required to call this server, and it exposes a tool marked destructive (decline_offer).
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - 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**: 61/100
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 3199 tokens (~199/item across 16 items; 16 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 20/100
  - Stability observed for 6 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 88/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 63% 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.
  - All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.
  - An AI judge read all 17 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a current MCP spec version (2026-07-28).

## Install

### How do I install the Surfing Dog Inbox MCP server?

Surfing Dog Inbox is a hosted endpoint at https://inbox.surfingdog.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.

### Claude

```bash
claude mcp add --transport http ai-surfingdog-inbox 'https://inbox.surfingdog.ai/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "ai-surfingdog-inbox": {
      "url": "https://inbox.surfingdog.ai/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "ai-surfingdog-inbox": {
      "type": "http",
      "url": "https://inbox.surfingdog.ai/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.ai-surfingdog-inbox]
url = "https://inbox.surfingdog.ai/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "ai-surfingdog-inbox": {
      "type": "remote",
      "url": "https://inbox.surfingdog.ai/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add ai-surfingdog-inbox --url 'https://inbox.surfingdog.ai/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  ai-surfingdog-inbox:
    url: "https://inbox.surfingdog.ai/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "ai-surfingdog-inbox": {
      "Transport": "http",
      "Url": "https://inbox.surfingdog.ai/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add ai-surfingdog-inbox -t streamable-http -u 'https://inbox.surfingdog.ai/mcp'
```

### Other

```json
{
  "mcpServers": {
    "ai-surfingdog-inbox": {
      "type": "http",
      "url": "https://inbox.surfingdog.ai/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 66, +1)

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

### 2026-09-26 (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-25 (score 64, 0)

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

### 2026-09-24 (score 64, 0)

- [security] The server rewrote its instructions, which are the text every model session reads
- [security] The server changed its declared name: surfingdog-inbox → Surfing Dog
- [security] New tool “decline_offer”, which the server declares destructive
- [security] Tool “cancel_item” rewrote its description, which is the text the model reads
- [security] Tool “check_availability” rewrote its description, which is the text the model reads
- [security] Tool “create_booking” rewrote its description, which is the text the model reads
- [security] Tool “create_order” rewrote its description, which is the text the model reads
- [security] Tool “get_item_status” rewrote its description, which is the text the model reads
- [security] Tool “list_services” rewrote its description, which is the text the model reads
- [functional regression] Schema quality: pass → fail
- [functional improvement] Tool coverage: 37% → 63%
- [functional improvement] Stability: unverified → 0.03
- [functional] New tool “accept_offer”
- [functional] New tool “provide_details”
- [functional] New tool “suggest_time”
- [functional] New tool “verify_customer”
- [cosmetic] “acknowledge_receipt” added an optional parameter “key”
- [cosmetic] “acknowledge_receipt” added an optional parameter “pass”
- [cosmetic] “acknowledge_receipt” added an optional parameter “receipt_id”
- [cosmetic] “cancel_item” added an optional parameter “key”
- [cosmetic] “cancel_item” added an optional parameter “pass”
- [cosmetic] “create_booking” added an optional parameter “key”
- [cosmetic] “create_booking” added an optional parameter “pass”
- [cosmetic] “create_order” added an optional parameter “key”
- [cosmetic] “create_order” added an optional parameter “pass”
- [cosmetic] “get_item_status” added an optional parameter “key”
- [cosmetic] “get_item_status” added an optional parameter “pass”
- [cosmetic] “request_quote” added an optional parameter “key”
- [cosmetic] “request_quote” added an optional parameter “pass”
- [cosmetic] “send_message” added an optional parameter “key”
- [cosmetic] “send_message” added an optional parameter “pass”
- [cosmetic] “acknowledge_receipt” reworded the description of “counter_signature”
- [cosmetic] “acknowledge_receipt” made “counter_signature” optional

### 2026-09-23 (score 64)

First indexed and scored.

## MCP tools (16)

### `get_business_profile` (~25 tokens)

Business profile

Name, time zone, currency, languages and the item types this business accepts.

### `list_services` (~61 tokens)

Services

Bookable services with duration and price. A price per person (price.per = person) is for each person in the booking: send partySize, and the total is the price times it.

Input parameters:

- `cursor` (string)
- `limit` (integer)

### `list_products` (~38 tokens)

Products

Orderable products with prices in minor units.

Input parameters:

- `cursor` (string)
- `limit` (integer)
- `q` (string)

### `check_availability` (~99 tokens)

Check availability

Free start times for a service between two instants (at most 14 days). A time that has started, or that starts within the business's minimum notice, is not offered.

Input parameters:

- `from` (string, required): Start of the window to search, ISO 8601.
- `party_size` (integer)
- `service_id` (string, required)
- `to` (string, required): End of the window, at most 14 days after from.

### `request_quote` (~169 tokens)

Request a quote

Ask for a price on something custom. Creates a quote_request item.

Input parameters:

- `contact` (object)
- `idempotency_key` (string): Same key + same request = same answer. Required for agents.
- `key` (string): The person's key (sdkey1_…), if that is all you have: it is exchanged once for a pass, which comes back in identity.passes — keep the pass and send it next time instead. Never stored.
- `message` (string)
- `pass` (string): The person's passes (sdpass1_…), space-separated, at most 8: presented to the network that issued each, so the business recognises the customer. Or send them in the Sdi-Pass header. Never stored.
- `payload` (object, required)

### `create_booking` (~207 tokens)

Request a booking

Request a service at a time. Check availability first. A fixed-price service costs the business's price from list_services; a different totalPrice you send is only noted for the business. Returns the item and, if you have no account, an access_token.

Input parameters:

- `contact` (object)
- `idempotency_key` (string): Same key + same request = same answer. Required for agents.
- `key` (string): The person's key (sdkey1_…), if that is all you have: it is exchanged once for a pass, which comes back in identity.passes — keep the pass and send it next time instead. Never stored.
- `message` (string)
- `pass` (string): The person's passes (sdpass1_…), space-separated, at most 8: presented to the network that issued each, so the business recognises the customer. Or send them in the Sdi-Pass header. Never stored.
- `payload` (object, required)

### `create_order` (~214 tokens)

Place an order

Order products. Prices are in minor units. A line naming a product (productId or sku) costs the business's price from list_products, and the total follows; a different price you send is only noted for the business. A line naming no product waits for the business to price it.

Input parameters:

- `contact` (object)
- `idempotency_key` (string): Same key + same request = same answer. Required for agents.
- `key` (string): The person's key (sdkey1_…), if that is all you have: it is exchanged once for a pass, which comes back in identity.passes — keep the pass and send it next time instead. Never stored.
- `message` (string)
- `pass` (string): The person's passes (sdpass1_…), space-separated, at most 8: presented to the network that issued each, so the business recognises the customer. Or send them in the Sdi-Pass header. Never stored.
- `payload` (object, required)

### `get_item_status` (~201 tokens)

Item status

The current state of an item you created, in the business's words: what it proposed and waits for your person to answer (offer, with its terms_sha), who it waits on, what they can do next, and the conversation so far (thread: the business's replies and your person's messages).

Input parameters:

- `access_token` (string): Capability secret returned when the item was created without an account.
- `item_id` (string, required)
- `key` (string): The person's key (sdkey1_…), if that is all you have: it is exchanged once for a pass, which comes back in identity.passes — keep the pass and send it next time instead. Never stored.
- `pass` (string): The person's passes (sdpass1_…), space-separated, at most 8: presented to the network that issued each, so the business recognises the customer. Or send them in the Sdi-Pass header. Never stored.

### `accept_offer` (~274 tokens)

Accept what the business proposed

Accept another time the business proposed for a booking, or its quote. This binds your person, so send terms_sha — offer.terms_sha from get_item_status — only after they said yes to offer.human. Without terms_sha nothing is booked: you get the terms to show them. An accepted quote becomes a confirmed booking or order (linked).

Input parameters:

- `access_token` (string): Capability secret returned when the item was created without an account.
- `idempotency_key` (string): Same key + same request = same answer. Required for agents.
- `item_id` (string, required)
- `key` (string): The person's key (sdkey1_…), if that is all you have: it is exchanged once for a pass, which comes back in identity.passes — keep the pass and send it next time instead. Never stored.
- `pass` (string): The person's passes (sdpass1_…), space-separated, at most 8: presented to the network that issued each, so the business recognises the customer. Or send them in the Sdi-Pass header. Never stored.
- `terms_sha` (string): The fingerprint of the terms your person said yes to: offer.terms_sha from get_item_status. Leave it out to be told the terms first; nothing is booked without it.

### `decline_offer` (~208 tokens)

Decline what the business proposed

Say no to another time the business proposed (the booking request is closed) or to its quote. Add reason for anything your person wants the business to know.

Input parameters:

- `access_token` (string): Capability secret returned when the item was created without an account.
- `idempotency_key` (string): Same key + same request = same answer. Required for agents.
- `item_id` (string, required)
- `key` (string): The person's key (sdkey1_…), if that is all you have: it is exchanged once for a pass, which comes back in identity.passes — keep the pass and send it next time instead. Never stored.
- `pass` (string): The person's passes (sdpass1_…), space-separated, at most 8: presented to the network that issued each, so the business recognises the customer. Or send them in the Sdi-Pass header. Never stored.
- `reason` (string): Anything your person wants the business to know.

### `suggest_time` (~243 tokens)

Ask for another time

Instead of the time the business proposed, ask for another: start_time must be one of the free times check_availability lists (the end follows the service's length). The business confirms it or proposes again.

Input parameters:

- `access_token` (string): Capability secret returned when the item was created without an account.
- `idempotency_key` (string): Same key + same request = same answer. Required for agents.
- `item_id` (string, required)
- `key` (string): The person's key (sdkey1_…), if that is all you have: it is exchanged once for a pass, which comes back in identity.passes — keep the pass and send it next time instead. Never stored.
- `note` (string)
- `pass` (string): The person's passes (sdpass1_…), space-separated, at most 8: presented to the network that issued each, so the business recognises the customer. Or send them in the Sdi-Pass header. Never stored.
- `start_time` (string, required): The start your person would like instead: one of the free times check_availability lists. The end follows the service's length.

### `provide_details` (~213 tokens)

Send the details

Answer what the business asked about an item (get_item_status says it needs a detail). The item moves on; on any other item your details are kept as a message for the business.

Input parameters:

- `access_token` (string): Capability secret returned when the item was created without an account.
- `details` (string, required): The answer to what the business asked.
- `idempotency_key` (string): Same key + same request = same answer. Required for agents.
- `item_id` (string, required)
- `key` (string): The person's key (sdkey1_…), if that is all you have: it is exchanged once for a pass, which comes back in identity.passes — keep the pass and send it next time instead. Never stored.
- `pass` (string): The person's passes (sdpass1_…), space-separated, at most 8: presented to the network that issued each, so the business recognises the customer. Or send them in the Sdi-Pass header. Never stored.

### `cancel_item` (~208 tokens)

Cancel

Cancel an item you created. After the business's cancellation window, a confirmed booking is cancelled late where the business records late cancellations (it may count against the customer), and refused where it does not.

Input parameters:

- `access_token` (string): Capability secret returned when the item was created without an account.
- `idempotency_key` (string): Same key + same request = same answer. Required for agents.
- `item_id` (string, required)
- `key` (string): The person's key (sdkey1_…), if that is all you have: it is exchanged once for a pass, which comes back in identity.passes — keep the pass and send it next time instead. Never stored.
- `pass` (string): The person's passes (sdpass1_…), space-separated, at most 8: presented to the network that issued each, so the business recognises the customer. Or send them in the Sdi-Pass header. Never stored.
- `reason` (string)

### `send_message` (~214 tokens)

Send a message

Start a conversation, or reply on an item you own.

Input parameters:

- `access_token` (string): Capability secret returned when the item was created without an account.
- `body` (string, required)
- `contact` (object)
- `idempotency_key` (string): Same key + same request = same answer. Required for agents.
- `item_id` (string): Reply on an existing item; omit to start a new conversation.
- `key` (string): The person's key (sdkey1_…), if that is all you have: it is exchanged once for a pass, which comes back in identity.passes — keep the pass and send it next time instead. Never stored.
- `message_id` (string)
- `pass` (string): The person's passes (sdpass1_…), space-separated, at most 8: presented to the network that issued each, so the business recognises the customer. Or send them in the Sdi-Pass header. Never stored.
- `subject` (string)

### `acknowledge_receipt` (~439 tokens)

Acknowledge a receipt

Counter-sign a receipt this item earned, so both sides hold it. Read the item to find its receipts; then send a compact JWS signed with your own Ed25519 key — header {alg:'EdDSA', typ:'sdi-receipt-ack+jws', jwk:<your public jwk>}, payload {rcp:<receipt id>, sha:<base64url(SHA-256(receipt jws))>, iat:<unix seconds>}. The instance verifies it against the key you carry and keeps it. Acknowledging twice is harmless.

Input parameters:

- `access_token` (string): Capability secret returned when the item was created without an account.
- `counter_signature` (string): A compact JWS by the customer's agent, EdDSA, header carrying its Ed25519 public `jwk`, payload `{"rcp": "<receipt id>", "sha": "<base64url(SHA-256(receipt JWS))>", "iat": <unix seconds>}`. Or, for a…
- `item_id` (string, required)
- `key` (string): The person's key (sdkey1_…), if that is all you have: it is exchanged once for a pass, which comes back in identity.passes — keep the pass and send it next time instead. Never stored.
- `pass` (string): The person's passes (sdpass1_…), space-separated, at most 8: presented to the network that issued each, so the business recognises the customer. Or send them in the Sdi-Pass header. Never stored.
- `receipt` (string): The receipt JWS being acknowledged, if you want the instance to check it is the one it holds.
- `receipt_id` (string): The receipt to acknowledge, for an agent that signs this request (sdi-agent/1) with a key delegated to the pass reference it sends: the inbox forwards the signature to the network (ADR-017 §3.4). Sen…

### `verify_customer` (~112 tokens)

Prove a known customer

When a result says identity.recognised is weak, the person gave the email of a customer the business knows. Call this with item_id and access_token to email them six digits; ask the person for the code and call it again with code. Then the business recognises them.

Input parameters:

- `access_token` (string): Capability secret returned when the item was created without an account.
- `code` (string): The six digits the customer received. Omit to have them sent.
- `item_id` (string, required)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/ai-surfingdog-inbox/inbox#diagnostics

## Score history

- 2026-09-29: 66
- 2026-09-28: 66
- 2026-09-27: 65
- 2026-09-26: 65
- 2026-09-25: 64
- 2026-09-24: 64
- 2026-09-23: 64

## Common questions

### What is the Surfing Dog Inbox MCP server?

Surfing Dog Inbox is an MCP server listed in the public MCP registry as ai.surfingdog/inbox. Message, ask for a quote or book a call with Surfing Dog, through its open-source inbox. This page covers its hosted endpoint (https://inbox.surfingdog.ai/mcp).

### Is the Surfing Dog Inbox MCP server safe to use?

Surfing Dog Inbox scores 66 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 Surfing Dog Inbox MCP server expose?

Surfing Dog Inbox exposes 16 tools: get_business_profile, list_services, list_products, check_availability, request_quote, and 11 more. Their descriptions and schemas cost roughly 2,925 tokens of context every time the server is loaded.

### Does the Surfing Dog Inbox MCP server require authentication?

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

### Is the Surfing Dog Inbox MCP server still maintained?

Surfing Dog Inbox is still listed as active in the MCP registry. We last reached this channel on 29 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://inbox.surfingdog.ai/mcp
- Repository: https://github.com/surfingdogai/inbox
- Website: https://surfingdog.ai/
- Changelog RSS feed: https://verifymcp.io/servers/ai-surfingdog-inbox/inbox.xml
- Changelog JSON feed: https://verifymcp.io/servers/ai-surfingdog-inbox/inbox.json
- HTML version of this page: https://verifymcp.io/servers/ai-surfingdog-inbox/inbox