Skip to content
MCPSTAMP
MCP server report

Boat House MCP server

com.boathousecloud/boathouse

We checked this server on 2 November 2026 with McpStamp Check engine 1.2.0. It scored 78 of 100 (grade C), higher than 23.7% of the 33,003 registry servers that responded over HTTPS that day. Ready for Gemini and MCP Registry. Not ready for Claude and ChatGPT.

Measured facts

Score
78C
Sign-in
No sign-in
Tools listed
41
Protocol version
2025-03-26
Stores

Store readiness

StoreStatusReason
Claude Connectors Directory Not ready Blocked by readOnlyHint or destructiveHint on every tool and Human-readable title on every tool.
ChatGPT app directory Not ready Blocked by readOnlyHint or destructiveHint on every tool, Explicit readOnlyHint, destructiveHint and openWorldHint (ChatGPT) and Human-readable title on every tool.
Gemini Connected Apps Ready No blocking check failed.
Official MCP Registry Ready No blocking check failed.

MCP Registry ready means a valid public remote for the registry, not that the server is listed in a store.

Fixes

4 checks to fix

  1. Fails

    readOnlyHint or destructiveHint on every tool

    tool_annotations

    Blocks Claude and ChatGPT.

    Measured 41/41 tools set neither readOnlyHint nor destructiveHint: whoami, list_tools, get_tool, deploy, pull and 36 more

    Set annotations.readOnlyHint: true on read-only tools and destructiveHint: true on tools that modify or delete data (Claude needs one of them on every tool; ChatGPT needs all three hints, see tool_open_world).

  2. Fails

    Explicit readOnlyHint, destructiveHint and openWorldHint (ChatGPT)

    tool_open_world

    Blocks ChatGPT.

    Measured 41/41 tools miss an explicit hint: whoami, list_tools, get_tool, deploy, pull and 36 more

    Set readOnlyHint, destructiveHint and openWorldHint to explicit true/false on every tool (OpenAI app review requires all three).

  3. Fails

    Human-readable title on every tool

    tool_titles

    Blocks Claude and ChatGPT.

    Measured 41/41 without title: whoami, list_tools, get_tool, deploy, pull and 36 more

    Add a short human-readable "title" to every tool (shown in store UIs and consent screens).

  4. Warning

    Supported protocol version negotiated

    protocol_version

    Measured Negotiated 2025-03-26

    Support protocol version 2025-11-25 (or 2025-06-18) and echo it back in initialize.

13 checks passed, 10 did not run

Passed. Served over HTTPS, initialize over Streamable HTTP, JSON or SSE response Content-Type, JSON-RPC error for unknown method, GET answers SSE or 405, initialize latency, serverInfo name and version, Server instructions, tools capability declared, tools/list returns tools, inputSchema is an object schema, Tool names are valid and portable, Tool descriptions.

Not run. Sign-in method the store supports (OAuth or none), 401 carries WWW-Authenticate resource_metadata, Protected resource metadata (RFC 9728), Resource metadata "resource" equals the server URL, Authorization server metadata (RFC 8414 / OIDC), First metadata URL Gemini tries answers 200 with the required fields, issuer equals the authorization_servers entry; token_endpoint_auth_methods_supported (ChatGPT), PKCE S256 advertised, Client registration (DCR or Client ID Metadata Documents), refresh_token grant advertised. The server asks for no sign-in, so the OAuth checks do not apply.

Run a fresh check

This page is the 2 November 2026 snapshot. If you maintain this server and have shipped fixes since then, re-check it. The live check and the badge show the current result, and the next snapshot will pick up the change.

Re-check now

Badge

README badge

The badge shows the latest score for this URL and links to this report.

McpStamp score for Boat House

Markdown

[![McpStamp score](https://www.mcpstamp.com/badge?url=https%3A%2F%2Fmcp.boathousecloud.com%2Fmcp)](https://www.mcpstamp.com/r/com-boathousecloud-boathouse/)

HTML

<a href="https://www.mcpstamp.com/r/com-boathousecloud-boathouse/"><img src="https://www.mcpstamp.com/badge?url=https%3A%2F%2Fmcp.boathousecloud.com%2Fmcp" alt="McpStamp score" height="20"></a>
Registry entry

About this server

Deploy and share small apps with team login, persistent data, versioned updates and domains.
Registry name
com.boathousecloud/boathouse
Remote URL
https://mcp.boathousecloud.com/mcp
Version
1.0.0
Source
github.com/allenzhangyiteng/boathouse-cloud
Website
boathousecloud.com
Checked
2 November 2026, engine 1.2.0, no credentials

The description above is the server's own text from the official MCP Registry. If a result looks wrong, run a fresh check and email support@zovo.one with the report link.

More grade C servers

All grade C servers · All server reports · State of MCP readiness, November 2026