# Boat House (remote · mcp.boathousecloud.com)

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

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

## Components

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

## Channel facts

- Endpoint: `https://mcp.boathousecloud.com/mcp`
- Transports: `streamable-http`
- Auth: `required`
- Version: `1.0.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**: 63/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 41 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.
  - 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**: 81/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 4517 tokens (~110/item across 41 items; 41 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 37/100
  - Stability observed for 11 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 75/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - 0 of 4 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "deploy" implies "deploy" and declares no destructiveHint at all, which the MCP spec reads as destructive by default.
  - An AI judge read all 42 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 40/100
  - Spec-recency check failed: implements MCP spec 2025-03-26; the latest is 2026-07-28.

## Install

### How do I install the Boat House MCP server?

Boat House is a hosted endpoint at https://mcp.boathousecloud.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-boathousecloud-boathouse 'https://mcp.boathousecloud.com/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "com-boathousecloud-boathouse": {
      "url": "https://mcp.boathousecloud.com/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "com-boathousecloud-boathouse": {
      "type": "http",
      "url": "https://mcp.boathousecloud.com/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.com-boathousecloud-boathouse]
url = "https://mcp.boathousecloud.com/mcp"
```

### opencode

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

### OpenClaw

```bash
openclaw mcp add com-boathousecloud-boathouse --url 'https://mcp.boathousecloud.com/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  com-boathousecloud-boathouse:
    url: "https://mcp.boathousecloud.com/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "com-boathousecloud-boathouse": {
      "Transport": "http",
      "Url": "https://mcp.boathousecloud.com/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add com-boathousecloud-boathouse -t streamable-http -u 'https://mcp.boathousecloud.com/mcp'
```

### Other

```json
{
  "mcpServers": {
    "com-boathousecloud-boathouse": {
      "type": "http",
      "url": "https://mcp.boathousecloud.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 30 to 33. That category is still filling its 30-day observation window: 9 days of observed history at the previous scan, 10 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 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.

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

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

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

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

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

- [functional improvement] Stability: unverified → 0.03

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

First indexed and scored.

## MCP tools (41)

### `whoami` (~75 tokens)

Who this project key belongs to: the email, the workspace, the domain its tools live on, and the prepaid balance. Call it first if you are not sure which workspace you are acting in.

Input parameters:

- `workspace` (string): Workspace slug to act in. Use this when you belong to several workspaces; whoami lists them.

### `list_tools` (~78 tokens)

Every tool in the workspace with its state (running/absent), current release, public URL and who can see it. A 'tool' is one small web app Boathouse runs behind the workspace login.

Input parameters:

- `workspace` (string): Workspace slug to act in. Use this when you belong to several workspaces; whoami lists them.

### `get_tool` (~94 tokens)

One tool in detail: URL, container state, current release, who it is visible to, and the list of people it has been shared with.

Input parameters:

- `tool` (string, required): The tool's short name, for example 'finance', or 'acme/finance' to select its workspace.
- `workspace` (string): Workspace slug to act in. Use this when you belong to several workspaces; whoami lists them.

### `deploy` (~303 tokens)

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.

Input parameters:

- `base` (integer): The release number these files were pulled from. The deploy is refused with STALE_BASE if a newer release is live.
- `base64` (object): Optional binary files: relative path -> base64 of the bytes.
- `files` (object, required): 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.
- `name` (string): Human name for the tool, used when it is created (e.g. 'CRCS Finance').
- `note` (string): Why this release exists; shown in the release list.
- `tool` (string, required): The tool's short name, for example 'finance', or 'acme/finance' to select its workspace.
- `workspace` (string): Workspace slug to act in. Use this when you belong to several workspaces; whoami lists them.

### `pull` (~123 tokens)

Fetch the exact source folder a release was built from, so you can edit it and deploy it back. Returns the release number and the files as text (binary files come back base64 encoded). Tool admins only.

Input parameters:

- `release` (integer): Which release to fetch. Defaults to the live one.
- `tool` (string, required): The tool's short name, for example 'finance', or 'acme/finance' to select its workspace.
- `workspace` (string): Workspace slug to act in. Use this when you belong to several workspaces; whoami lists them.

### `logs` (~122 tokens)

The tool container's recent log lines, newest last. Use this to find out why a tool is failing.

Input parameters:

- `since` (integer): Unix seconds: only lines after this moment.
- `tail` (integer): How many lines from the end (default 200, max 5000).
- `tool` (string, required): The tool's short name, for example 'finance', or 'acme/finance' to select its workspace.
- `workspace` (string): Workspace slug to act in. Use this when you belong to several workspaces; whoami lists them.

### `releases` (~103 tokens)

The last 20 releases of a tool: number, status (live/superseded/failed), when, who and the note. A failed release shows the last line of its build log.

Input parameters:

- `tool` (string, required): The tool's short name, for example 'finance', or 'acme/finance' to select its workspace.
- `workspace` (string): Workspace slug to act in. Use this when you belong to several workspaces; whoami lists them.

### `rollback` (~113 tokens)

Put an earlier release back in service. With no `to`, goes back to the release before the live one. This rolls back the software, never the database.

Input parameters:

- `to` (integer): Release number to restore. Defaults to the previous one.
- `tool` (string, required): The tool's short name, for example 'finance', or 'acme/finance' to select its workspace.
- `workspace` (string): Workspace slug to act in. Use this when you belong to several workspaces; whoami lists them.

### `restart` (~76 tokens)

Restart the tool's container with its current release and current secrets.

Input parameters:

- `tool` (string, required): The tool's short name, for example 'finance', or 'acme/finance' to select its workspace.
- `workspace` (string): Workspace slug to act in. Use this when you belong to several workspaces; whoami lists them.

### `share` (~201 tokens)

Give one person access to one tool by email, at a tier: viewer (read only; the gateway blocks their writes), editor (may change the data), admin (may change the software, secrets, sharing). If the person is new, Boat House emails a secure invitation when email is configured. Check emailed in the result; if delivery failed, share the invitation page so the person can request their secure email.

Input parameters:

- `email` (string, required): The person's email address.
- `labels` (array): Optional app-specific words passed to the tool as headers (e.g. ['consultant']). Labels are not permissions.
- `tier` (string): viewer, editor or admin. Default viewer.
- `tool` (string, required): The tool's short name, for example 'finance', or 'acme/finance' to select its workspace.
- `workspace` (string): Workspace slug to act in. Use this when you belong to several workspaces; whoami lists them.

### `unshare` (~90 tokens)

Take away one person's access to one tool. They keep their workspace account.

Input parameters:

- `email` (string, required): The person's email address.
- `tool` (string, required): The tool's short name, for example 'finance', or 'acme/finance' to select its workspace.
- `workspace` (string): Workspace slug to act in. Use this when you belong to several workspaces; whoami lists them.

### `request_access` (~126 tokens)

Ask to be let into a tool in someone else's workspace, at viewer, editor or admin. Its owners get an email with one Allow button; nobody there runs a command. The person is emailed when it is allowed.

Input parameters:

- `message` (string): One line the owners see, e.g. who you are and why.
- `target` (string, required): <workspace>/<tool>, for example chloe/db.
- `tier` (string): Default viewer.
- `workspace` (string): Workspace slug to act in. Use this when you belong to several workspaces; whoami lists them.

### `access_requests` (~66 tokens)

Everyone waiting to be let into one of this workspace's tools: request id, email, tier asked for, and their message. Owners and tool admins.

Input parameters:

- `workspace` (string): Workspace slug to act in. Use this when you belong to several workspaces; whoami lists them.

### `allow_request` (~81 tokens)

Let a waiting person in at the tier they asked for. Their tool grant is made and they get an email saying what to do next. Owners and tool admins.

Input parameters:

- `id` (string, required): The request id from access_requests.
- `workspace` (string): Workspace slug to act in. Use this when you belong to several workspaces; whoami lists them.

### `set_access` (~165 tokens)

Set who a tool is open to by default: 'members' means anyone in the workspace (at the given tier), 'listed' means only the people it has been explicitly shared with. Use 'listed' for anything sensitive.

Input parameters:

- `mode` (string, required): members (anyone in the workspace), listed (only people shared with), or public (anyone on the internet may read; writes still need sign-in).
- `tier` (string): The tier workspace members get when mode is 'members'.
- `tool` (string, required): The tool's short name, for example 'finance', or 'acme/finance' to select its workspace.
- `workspace` (string): Workspace slug to act in. Use this when you belong to several workspaces; whoami lists them.

### `secrets_list` (~92 tokens)

The names of a tool's secrets (API keys and the like), when each was last set and by whom. Values are never returned.

Input parameters:

- `tool` (string, required): The tool's short name, for example 'finance', or 'acme/finance' to select its workspace.
- `workspace` (string): Workspace slug to act in. Use this when you belong to several workspaces; whoami lists them.

### `secrets_set` (~138 tokens)

Set one secret on a tool. It is injected as an environment variable of that name and the tool is restarted. Names are UPPER_SNAKE_CASE. Never echo the value back to the user.

Input parameters:

- `name` (string, required): UPPER_SNAKE_CASE environment variable name, e.g. STRIPE_KEY.
- `tool` (string, required): The tool's short name, for example 'finance', or 'acme/finance' to select its workspace.
- `value` (string, required): The secret value.
- `workspace` (string): Workspace slug to act in. Use this when you belong to several workspaces; whoami lists them.

### `secrets_delete` (~93 tokens)

Remove one secret from a tool. It disappears on the tool's next restart or deploy.

Input parameters:

- `name` (string, required): The secret's name.
- `tool` (string, required): The tool's short name, for example 'finance', or 'acme/finance' to select its workspace.
- `workspace` (string): Workspace slug to act in. Use this when you belong to several workspaces; whoami lists them.

### `users_list` (~59 tokens)

Everyone in the workspace: role (owner, member or guest), name, and whether they have set a password yet.

Input parameters:

- `workspace` (string): Workspace slug to act in. Use this when you belong to several workspaces; whoami lists them.

### `users_add` (~123 tokens)

Add a person to the workspace, or change their role. owner = may spend money, buy domains and manage people, and is admin on every tool; member = may see tools open to members and deploy their own; guest = sees only what is explicitly shared with them. Returns a one-time invite link for someone new. Owners only.

Input parameters:

- `email` (string, required): The person's email address.
- `role` (string): Default member.
- `workspace` (string): Workspace slug to act in. Use this when you belong to several workspaces; whoami lists them.

### `users_invite` (~104 tokens)

Resend an invitation to someone in the workspace. New accounts confirm their mailbox through the emailed link; established accounts receive a normal sign-in URL. Password recovery is self-service on that page, and only the account holder's mailbox receives a reset link. Check emailed before offering a fallback.

Input parameters:

- `email` (string, required): The person's email address.
- `workspace` (string): Workspace slug to act in. Use this when you belong to several workspaces; whoami lists them.

### `users_remove` (~70 tokens)

Remove a person from the workspace. Their sessions, project keys, invites and tool grants stop working immediately. Owners only.

Input parameters:

- `email` (string, required): The person's email address.
- `workspace` (string): Workspace slug to act in. Use this when you belong to several workspaces; whoami lists them.

### `domains_list` (~67 tokens)

The addresses this workspace answers on: the free <workspace>.boathousecloud.com address, the primary domain, and every custom domain with its DNS state.

Input parameters:

- `workspace` (string): Workspace slug to act in. Use this when you belong to several workspaces; whoami lists them.

### `domain_check` (~101 tokens)

Ask the registrar whether a domain is free and what it costs per year. Buys nothing. total_cents is the price the workspace pays (registrar_cents plus Boathouse's margin_cents); show that one.

Input parameters:

- `domain` (string, required): A full domain name, e.g. 'crcstools.com'.
- `workspace` (string): Workspace slug to act in. Use this when you belong to several workspaces; whoami lists them.

### `domain_buy` (~172 tokens)

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.

Input parameters:

- `confirm` (boolean): False or absent returns the quote and does nothing. True actually does it.
- `domain` (string, required): The domain to buy, e.g. 'crcstools.com'.
- `max_cost_cents` (integer): Maximum approved total, including Boathouse's margin. Required to confirm.
- `quote_id` (string): The quote_id from the dry run. Required to confirm; reuse it on retries.
- `workspace` (string): Workspace slug to act in. Use this when you belong to several workspaces; whoami lists them.

### `domain_renewals` (~54 tokens)

Read domain expiry dates, renewal status, spending limits and billing problems. Owners only.

Input parameters:

- `workspace` (string): Workspace slug to act in. Use this when you belong to several workspaces; whoami lists them.

### `domain_renewal_set` (~151 tokens)

Set automatic renewal and a maximum prepaid renewal charge. Quote the change first, then require explicit approval with confirm true. Turning renewal off lets the domain expire. Owners only.

Input parameters:

- `confirm` (boolean): False or absent returns the quote and does nothing. True actually does it.
- `domain` (string, required): A domain owned through this organization, including detached domains.
- `enabled` (boolean, required): True renews from prepaid credit; false lets the domain expire.
- `max_cost_cents` (integer): Approved maximum per renewal including the service fee; required when enabling.
- `workspace` (string): Workspace slug to act in. Use this when you belong to several workspaces; whoami lists them.

### `domain_attach` (~119 tokens)

Bring a domain the workspace already owns elsewhere: Boathouse starts answering on it and returns the DNS records to make at the current DNS host. Optionally point it at one tool at the same time. Owners only.

Input parameters:

- `domain` (string, required): A full domain name you control, e.g. 'crcstools.com'.
- `tool` (string): Optional: the tool the bare domain and www should open.
- `workspace` (string): Workspace slug to act in. Use this when you belong to several workspaces; whoami lists them.

### `domain_point` (~98 tokens)

Make a domain (and its www) open one tool instead of the workspace's tool list. An empty tool clears it. Owners only.

Input parameters:

- `domain` (string, required): A domain the workspace answers on.
- `tool` (string): The tool to open, or an empty string to show the tool list again.
- `workspace` (string): Workspace slug to act in. Use this when you belong to several workspaces; whoami lists them.

### `domain_primary` (~70 tokens)

Make one of the workspace's domains the primary one: the address tool URLs and emails use. Owners only.

Input parameters:

- `domain` (string, required): A domain the workspace answers on.
- `workspace` (string): Workspace slug to act in. Use this when you belong to several workspaces; whoami lists them.

### `domain_dns` (~68 tokens)

The DNS records the registrar currently holds for a domain Boathouse bought or manages. Changes nothing.

Input parameters:

- `domain` (string, required): A domain the workspace answers on.
- `workspace` (string): Workspace slug to act in. Use this when you belong to several workspaces; whoami lists them.

### `domain_repoint` (~81 tokens)

Rewrite a Boathouse-managed domain's DNS records to point at this Boathouse again (after a move, or if someone changed them). Owners only.

Input parameters:

- `domain` (string, required): A domain the workspace answers on.
- `workspace` (string): Workspace slug to act in. Use this when you belong to several workspaces; whoami lists them.

### `domain_detach` (~69 tokens)

Stop serving a domain. The registration itself is untouched and domain_attach brings it back. Owners only.

Input parameters:

- `domain` (string, required): A domain the workspace answers on.
- `workspace` (string): Workspace slug to act in. Use this when you belong to several workspaces; whoami lists them.

### `usage` (~81 tokens)

Check storage, memory, CPU and the reason an app is paused. Tool admins only.

Input parameters:

- `tool` (string, required): The tool's short name, for example 'finance', or 'acme/finance' to select its workspace.
- `workspace` (string): Workspace slug to act in. Use this when you belong to several workspaces; whoami lists them.

### `capacity` (~168 tokens)

Quote additional app storage. Show the maximum extra monthly price and get owner approval before confirming. No automatic upgrade. Owners only.

Input parameters:

- `confirm` (boolean): False or absent returns the quote and does nothing. True actually does it.
- `max_extra_monthly_cents` (integer): Maximum extra monthly price from the approved quote, in cents.
- `quote_id` (string): The exact capacity quote the owner approved.
- `storage_gb` (integer): Requested total storage in whole GB; starts with a price quote.
- `tool` (string, required): The tool's short name, for example 'finance', or 'acme/finance' to select its workspace.
- `workspace` (string): Workspace slug to act in. Use this when you belong to several workspaces; whoami lists them.

### `billing` (~73 tokens)

The workspace's money: prepaid balance, whether it is paused, how fast running tools burn credit, how many days are left, whether a card is on file, and the last ledger lines.

Input parameters:

- `workspace` (string): Workspace slug to act in. Use this when you belong to several workspaces; whoami lists them.

### `prices` (~64 tokens)

What Boathouse charges, in plain words: one organization plan for up to five lightweight tools, shared limits, storage, and the domain margin.

Input parameters:

- `workspace` (string): Workspace slug to act in. Use this when you belong to several workspaces; whoami lists them.

### `referral` (~68 tokens)

This person's referral code and link, the deal in words, and what each referred workspace has earned them so far (10% of usage charges, paid monthly in cash).

Input parameters:

- `workspace` (string): Workspace slug to act in. Use this when you belong to several workspaces; whoami lists them.

### `topup` (~162 tokens)

Open secure Stripe checkout to add prepaid hosting credit; the owner completes payment there. Without confirm it only quotes and returns operation_id. Confirm the same cents and operation_id after user approval; reuse the ID on retries. Between $5.00 (500) and $1,000.00 (100000). Owners only.

Input parameters:

- `cents` (integer, required): Amount in cents, e.g. 2000 for $20.00.
- `confirm` (boolean): False or absent returns the quote and does nothing. True actually does it.
- `operation_id` (string): The payment quote ID, required when confirming or retrying.
- `workspace` (string): Workspace slug to act in. Use this when you belong to several workspaces; whoami lists them.

### `card_link` (~66 tokens)

A one-time link where a workspace owner types a card into Stripe. This is the only part of Boathouse that needs a browser. Owners only.

Input parameters:

- `workspace` (string): Workspace slug to act in. Use this when you belong to several workspaces; whoami lists them.

### `delete_tool` (~142 tokens)

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.

Input parameters:

- `purge` (boolean): Also destroy the tool's database and uploaded files. Irreversible.
- `purge_confirm` (boolean): Must be true alongside purge, as a second confirmation.
- `tool` (string, required): The tool's short name, for example 'finance', or 'acme/finance' to select its workspace.
- `workspace` (string): Workspace slug to act in. Use this when you belong to several workspaces; whoami lists them.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/com-boathousecloud-boathouse/mcp#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: 65
- 2026-09-19: 65
- 2026-09-18: 64
- 2026-09-17: 64

## Common questions

### What is the Boat House MCP server?

Boat House is an MCP server listed in the public MCP registry as com.boathousecloud/boathouse. Deploy and share small apps with team login, persistent data, versioned updates and domains. This page covers its hosted endpoint (https://mcp.boathousecloud.com/mcp).

### Is the Boat House MCP server safe to use?

Boat House 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 Boat House MCP server expose?

Boat House exposes 41 tools: whoami, list_tools, get_tool, deploy, pull, and 36 more. Their descriptions and schemas cost roughly 4,369 tokens of context every time the server is loaded.

### Does the Boat House MCP server require authentication?

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

### Is the Boat House MCP server still maintained?

Boat House 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://mcp.boathousecloud.com/mcp
- Authorisation metadata: https://mcp.boathousecloud.com/.well-known/oauth-protected-resource/mcp
- Repository: https://github.com/allenzhangyiteng/boathouse-cloud
- Website: https://boathousecloud.com/
- Changelog RSS feed: https://verifymcp.io/servers/com-boathousecloud-boathouse/mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-boathousecloud-boathouse/mcp.json
- HTML version of this page: https://verifymcp.io/servers/com-boathousecloud-boathouse/mcp