Surfing Dog Inbox
REMOTE · INBOX.SURFINGDOG.AI · SCANNED SEP 29
Message, ask for a quote or book a call with Surfing Dog, through its open-source inbox.
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 Security63
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation check failed: no authorisation is required to call this server, and it exposes a tool marked destructive (decline_offer). See how to fix → View diagnostics → Fail
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability61
- AI-judged instruction clarity (good).Pass
- 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. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management20
- Stability observed for 6 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage88
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 63% 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
- All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
- An AI judge read all 17 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
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.
remote · inbox.surfingdog.ai
claude mcp add --transport http ai-surfingdog-inbox 'https://inbox.surfingdog.ai/mcp'
{
"mcpServers": {
"ai-surfingdog-inbox": {
"url": "https://inbox.surfingdog.ai/mcp"
}
}
} {
"servers": {
"ai-surfingdog-inbox": {
"type": "http",
"url": "https://inbox.surfingdog.ai/mcp"
}
}
} [mcp_servers.ai-surfingdog-inbox] url = "https://inbox.surfingdog.ai/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"ai-surfingdog-inbox": {
"type": "remote",
"url": "https://inbox.surfingdog.ai/mcp",
"enabled": true
}
}
} openclaw mcp add ai-surfingdog-inbox --url 'https://inbox.surfingdog.ai/mcp' --transport streamable-http
mcp_servers:
ai-surfingdog-inbox:
url: "https://inbox.surfingdog.ai/mcp" {
"McpServers": {
"ai-surfingdog-inbox": {
"Transport": "http",
"Url": "https://inbox.surfingdog.ai/mcp"
}
}
} assistant mcp add ai-surfingdog-inbox -t streamable-http -u 'https://inbox.surfingdog.ai/mcp'
{
"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.
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
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.
- 25 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 24 Sept 26 0
- 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 security
- Schema quality: pass → fail ▼ functional
- Tool coverage: 37% → 63% ▲ functional
- Stability: unverified → 0.03 ▲ functional
- New tool “accept_offer” functional
- New tool “provide_details” functional
- New tool “suggest_time” functional
- New tool “verify_customer” functional
- “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 cosmetic
- 23 Sept 26 64
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 29 Sept 2026 · Probed https://inbox.surfingdog.ai/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=surfingdog.ai | CN=WE1,O=Google Trust Services,C=US | 23 Aug 2026 | 21 Nov 2026 | ECDSA 256 | ECDSA-SHA256 | 561ec22dbd2358610e52834029366460 |
| SANs: surfingdog.ai, *.surfingdog.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 insecure
Validation of inbox.surfingdog.ai. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| ai. | present | 3799 | 8 | Verified |
| surfingdog.ai. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
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 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=15552000 |
| content-security-policy | frame-ancestors 'none' |
| x-content-type-options | nosniff |
| x-frame-options | DENY |
| referrer-policy | strict-origin-when-cross-origin |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://inbox.surfingdog.ai/mcp | Verified | 200 | |
| http (plaintext) | http://inbox.surfingdog.ai/mcp | HTTPS enforced | 301 | https://inbox.surfingdog.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 →
accept_offer Accept what the business proposed ~274
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).
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | – |
| 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. |
No output schema declared.
No examples provided.
acknowledge_receipt Acknowledge a receipt ~439
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | – |
| 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… |
No output schema declared.
No examples provided.
cancel_item Cancel ~208
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | – |
| 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 | – | – |
No output schema declared.
No examples provided.
check_availability Check availability ~99
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.
| Name | Type | Req | Description |
|---|---|---|---|
| from | string | yes | Start of the window to search, ISO 8601. |
| party_size | integer | – | – |
| service_id | string | yes | – |
| to | string | yes | End of the window, at most 14 days after from. |
No output schema declared.
No examples provided.
create_booking Request a booking ~207
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | – |
No output schema declared.
No examples provided.
create_order Place an order ~214
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | – |
No output schema declared.
No examples provided.
decline_offer Decline what the business proposed ~208
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | – |
| 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. |
No output schema declared.
No examples provided.
get_business_profile Business profile ~25
Name, time zone, currency, languages and the item types this business accepts.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_item_status Item status ~201
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).
| Name | Type | Req | Description |
|---|---|---|---|
| access_token | string | – | Capability secret returned when the item was created without an account. |
| item_id | string | yes | – |
| 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. |
No output schema declared.
No examples provided.
list_products Products ~38
Orderable products with prices in minor units.
| Name | Type | Req | Description |
|---|---|---|---|
| cursor | string | – | – |
| limit | integer | – | – |
| q | string | – | – |
No output schema declared.
No examples provided.
list_services Services ~61
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.
| Name | Type | Req | Description |
|---|---|---|---|
| cursor | string | – | – |
| limit | integer | – | – |
No output schema declared.
No examples provided.
provide_details Send the details ~213
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.
| Name | Type | Req | Description |
|---|---|---|---|
| access_token | string | – | Capability secret returned when the item was created without an account. |
| details | string | yes | The answer to what the business asked. |
| idempotency_key | string | – | Same key + same request = same answer. Required for agents. |
| item_id | string | yes | – |
| 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. |
No output schema declared.
No examples provided.
request_quote Request a quote ~169
Ask for a price on something custom. Creates a quote_request item.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | – |
No output schema declared.
No examples provided.
send_message Send a message ~214
Start a conversation, or reply on an item you own.
| Name | Type | Req | Description |
|---|---|---|---|
| access_token | string | – | Capability secret returned when the item was created without an account. |
| body | string | yes | – |
| 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 | – | – |
No output schema declared.
No examples provided.
suggest_time Ask for another time ~243
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | – |
| 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 | yes | The start your person would like instead: one of the free times check_availability lists. The end follows the service's length. |
No output schema declared.
No examples provided.
verify_customer Prove a known customer ~112
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | – |
No output schema declared.
No examples provided.
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.