Is the Boathousecloud Boathouse MCP server down?

mcp-registry/com.boathousecloud/boathouse · v0.3

healthy
Last checked 2026-10-17 22:56 UTC · handshake 217ms

As of 2026-10-17 22:56 UTC, the Boathousecloud Boathouse MCP server is up with a Glimind reliability score of 90/100 (grade A). Over the last 30 days it answered 99.9% of Glimind's liveness checks. It had 2 outages in 90 days, with a median recovery of 8 minutes.

uptime (30d checks)
99.9%
checks observed
3,565
outages (90d)
2
tools
41

Deploy and share small apps with team login, persistent data, versioned updates and domains.

Install Boathousecloud Boathouse MCP server

Add to Cursor Add to VS Code

Claude Code

claude mcp add --transport http boathousecloud-boathouse-mcp-server https://mcp.boathousecloud.com/mcp

Claude Desktop · Windsurf · Cline (mcpServers JSON)

{
  "mcpServers": {
    "boathousecloud-boathouse-mcp-server": {
      "type": "http",
      "url": "https://mcp.boathousecloud.com/mcp"
    }
  }
}

Third-party server, listed as discovered. Review its source before installing.

Agent-readiness: C (73/100)

C (73/100): 0 error(s), 5 warning(s) across 41 tool(s); ~6,837 tokens of tool definitions.
Scores higher than 9% of 15,327 MCP servers Glimind has audited.
Its tool list costs an agent ~6,837 tokens per session — more than 65% of servers.
no tool-poisoning patterns
Schemas100
Descriptions100
Safety hints4
Token cost75
Client compatibility70
Protocol40
Reliability85
Stability100

What to fix (6)

41 of 41 tool(s) carry no readOnlyHint/destructiveHint annotations.

Annotate read-only tools with {"readOnlyHint": true}. Agents and gateways can then run them without a confirmation prompt, and route around destructive ones.

Tools: access_requests, allow_request, billing, capacity, card_link and 36 more

41 tools on one server. Tool-selection accuracy drops as the menu grows, and some clients (e.g. Cursor) cap the number of active tools.

Group tools by task into smaller servers or toolsets, and merge near-duplicates behind one tool with a mode parameter.

8 tool(s) look like they change state (create/send/delete/pay…) but declare no destructiveHint.

Set annotations {"readOnlyHint": false, "destructiveHint": true|false, "idempotentHint": …}. Clients use these to ask the user before a side effect and to auto-approve safe reads.

Tools: delete_tool, deploy, domain_buy, domain_renewal_set, secrets_delete and 3 more

Negotiates MCP 2025-03-26. Structured output, tool output schemas and elicitation arrived in 2025-06-18.

Upgrade the MCP SDK and negotiate 2025-06-18 or newer.

Handshake + tools/list takes ~1,788 ms.

Serve tools/list from memory, keep the process warm, and host close to your users. Every new agent session pays this before its first call.

No tool declares an outputSchema.

Declare outputSchema and return structuredContent (MCP 2025-06-18+). Agents can then parse results without guessing, and chain tools reliably.

Auto-fix: 16 corrected tool definitions

Paste-ready definitions with the problems above fixed. Changes marked verify need a human look. All of them as JSON: /v1/readiness/mcp-registry%2Fcom.boathousecloud%2Fboathouse/fixes

delete_tool 1 change
{
  "name": "delete_tool",
  "description": "Delete a tool: its container, its releases and its sharing. By default the tool's database and files are kept. purge true also destroys them forever, and then requires purge_confirm true as well.",
  "inputSchema": {
    "type": "object",
    "required": [
      "tool"
    ],
    "properties": {
      "tool": {
        "type": "string",
        "description": "The tool's short name, for example 'finance', or 'acme/finance' to select its workspace."
      },
      "purge": {
        "type": "boolean",
        "description": "Also destroy the tool's database and uploaded files. Irreversible."
      },
      "workspace": {
        "type": "string",
        "description": "Workspace slug to act in. Use this when you belong to several workspaces; whoami lists them."
      },
      "purge_confirm": {
        "type": "boolean",
        "description": "Must be true alongside purge, as a second confirmation."
      }
    }
  },
  "annotations": {
    "readOnlyHint": false,
    "destructiveHint": true,
    "idempotentHint": true
  }
}
deploy 1 change
{
  "name": "deploy",
  "description": "Deploy a folder as a tool and make it live at https://<tool>.<workspace domain>. Send the whole folder in `files`, which MUST include a top-level Dockerfile whose process listens on $PORT (8080). Creates the tool on the first deploy; afterwards it replaces the running container. If you got these files from `pull`, pass the release number you pulled as `base` so a deploy someone else made in the meantime is not silently overwritten.",
  "inputSchema": {
    "type": "object",
    "required": [
      "tool",
      "files"
    ],
    "properties": {
      "base": {
        "type": "integer",
        "description": "The release number these files were pulled from. The deploy is refused with STALE_BASE if a newer release is live."
      },
      "name": {
        "type": "string",
        "description": "Human name for the tool, used when it is created (e.g. 'CRCS Finance')."
      },
      "note": {
        "type": "string",
        "description": "Why this release exists; shown in the release list."
      },
      "tool": {
        "type": "string",
        "description": "The tool's short name, for example 'finance', or 'acme/finance' to select its workspace."
      },
      "files": {
        "type": "object",
        "description": "The folder: relative path -> the file's text content, e.g. {\"Dockerfile\": \"FROM python:3.12-slim\\n...\", \"app.py\": \"...\"}. No leading slash and no '..' in paths.",
        "additionalProperties": {
          "type": "string"
        }
      },
      "base64": {
        "type": "object",
        "description": "Optional binary files: relative path -> base64 of the bytes.",
        "additionalProperties": {
          "type": "string"
        }
      },
      "workspace": {
        "type": "string",
        "description": "Workspace slug to act in. Use this when you belong to several workspaces; whoami lists them."
      }
    }
  },
  "annotations": {
    "readOnlyHint": false,
    "destructiveHint": false,
    "idempotentHint": false
  }
}
domain_buy 1 change
{
  "name": "domain_buy",
  "description": "Buy a domain through Boathouse's registrar and point it at this box, paid from the workspace's prepaid balance. Without confirm it only returns the quote (cost now, renewal price, your balance) and buys nothing. Owners only.",
  "inputSchema": {
    "type": "object",
    "required": [
      "domain"
    ],
    "properties": {
      "domain": {
        "type": "string",
        "description": "The domain to buy, e.g. 'crcstools.com'."
      },
      "confirm": {
        "type": "boolean",
        "description": "False or absent returns the quote and does nothing. True actually does it."
      },
      "quote_id": {
        "type": "string",
        "description": "The quote_id from the dry run. Required to confirm; reuse it on retries."
      },
      "workspace": {
        "type": "string",
        "description": "Workspace slug to act in. Use this when you belong to several workspaces; whoami lists them."
      },
      "max_cost_cents": {
        "type": "integer",
        "minimum": 1,
        "description": "Maximum approved total, including Boathouse's margin. Required to confirm."
      }
    }
  },
  "annotations": {
    "readOnlyHint": false,
    "destructiveHint": false,
    "idempotentHint": false
  }
}

Get alerted

Get an email or webhook when this server's readiness drops by 10+ points, tool-poisoning text appears, or a tool breaks:

curl -X POST https://glimind.com/v1/subscriptions -H 'content-type: application/json' -d '{"tools":["mcp-registry/com.boathousecloud/boathouse"],"email":"[email protected]"}'

Agents: watch_tool({"toolId": "mcp-registry/com.boathousecloud/boathouse"}) over MCP.

Passed

Largest tool definitions

Static checks of the advertised tools/list (schema, descriptions, annotations, tool-poisoning patterns, names, size) plus observed protocol, uptime, latency and contract changes. Read-only: no tool is ever called. Weights: schema 15, docs 20, safety 15, efficiency 15, compatibility 15, protocol 5, reliability 10, stability 5. Token counts are estimates (~3.6 characters per token).

Operator? Fix these, then re-check live. Embed the readiness badge:

Markdown
[![MCP agent-readiness](https://glimind.com/v1/readiness/badge/mcp-registry%2Fcom.boathousecloud%2Fboathouse.svg)](https://glimind.com/server/mcp-registry%2Fcom.boathousecloud%2Fboathouse?ref=badge)
HTML
<a href="https://glimind.com/server/mcp-registry%2Fcom.boathousecloud%2Fboathouse?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fcom.boathousecloud%2Fboathouse.svg" alt="MCP agent-readiness"></a>
reStructuredText
.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fcom.boathousecloud%2Fboathouse.svg
   :target: https://glimind.com/server/mcp-registry%2Fcom.boathousecloud%2Fboathouse?ref=badge
   :alt: MCP agent-readiness

Tool-definition log

Glimind records every version of this server's tool definitions in a signed, append-only transparency log. Current manifest sha256:f1e74d619eb833c9…, first seen 2026-10-17, included at leaf 2419 of 18,998. Version history · verify what your client received.

Tools (41)

Compare: most reliable communication servers · most reliable billing servers · most reliable payments servers · most reliable devops servers · most reliable other servers

Know before your agent calls it

Glimind tells agents whether a server is up right now and how to call it, then fails over to a live alternative when it isn't.

Add Glimind — free, no signup:

Add to Cursor Add to VS Code

Claude Code

claude mcp add --transport http glimind https://glimind.com/mcp

Claude Desktop · Windsurf · Cline (mcpServers JSON)

{
  "mcpServers": {
    "glimind": {
      "type": "http",
      "url": "https://glimind.com/mcp"
    }
  }
}

FAQ

Is the Boathousecloud Boathouse MCP server down right now?

As of 2026-10-17 22:56 UTC, the Boathousecloud Boathouse MCP server is up with a Glimind reliability score of 90/100 (grade A). Over the last 30 days it answered 99.9% of Glimind's liveness checks. It had 2 outages in 90 days, with a median recovery of 8 minutes.

How many tools does Boathousecloud Boathouse MCP server provide?

Boathousecloud Boathouse MCP server advertises 41 tools, including access_requests, allow_request, billing, capacity, card_link.

How do I install Boathousecloud Boathouse MCP server?

Point your MCP client at this streamable-http endpoint: https://mcp.boathousecloud.com/mcp

Is the Boathousecloud Boathouse MCP server safe to connect to an AI agent?

Glimind scanned all 41 tool definitions for tool-poisoning patterns — hidden or invisible characters, instructions that override the model, concealment from the user, requests to read credential or MCP config files, conversation exfiltration and cross-tool shadowing — and found none. This checks what the server tells the model, not what its code does; review the source before granting access to sensitive data.

Operator of Boathousecloud Boathouse MCP server?

Status page: 90-day uptime, every outage and how long it lasted.

Claim this listing to get the Verified operator marker, a remediation checklist and owner analytics, or embed the live badge from any of the tool pages above. Maintainers: alerts, deploy attestation and monthly reports.

Status is an automated estimate from Glimind's liveness checks (handshake and tool listing only; no tool is ever called) and may lag or differ from your network. Glimind is not affiliated with this server or its operator. Operator? Request a correction or opt out at https://glimind.com/opt-out.