Servidor MCP de Boat House

• Nombre en el registrocom.boathousecloud/boathouseverificado en el registro MCP

El nombre en el registro está bajo boathousecloud.com. El registro solo permite usar ese espacio de nombres a quien demuestra control del dominio por DNS o HTTP.

• Estadorespondecomprobado el 2026-10-20
• Herramientas41
• El servidor se llamaboathouse
• Versión del servidor0.3
• Versión del protocolo2025-03-26

El 2026-10-20 el servidor respondió a initialize y tools/list sin iniciar sesión. Primera respuesta en 263 ms.

• Sus herramientas hacen todos los casos de uso comprobados: Put an agent-built tracker online behind sign-in; Share a tool so editors can update its records; Give a trusted developer access to change the source.
• Comprobado 2 de los 7 días necesarios para juzgar su fiabilidad.

Lo dicen reglas a partir de las mediciones de arriba. La primera llamada probable la elige un modelo de la lista de herramientas; lee su descripción antes de fiarte.

• Nota INITE MCPtras una semanala nota necesita 7 comprobaciones diarias: 2 hasta ahora
• Qué puede hacer un agente con él3 de 3 casos de uso
• Uso1 estrellas en GitHub
• Respondiómidiendo2 de las 7 comprobaciones diarias necesarias para mostrar el porcentaje
• Mediana de la primera respuesta267 ms
• Espacio en el contexto del agente≈ 6157 tokenslas definiciones de todas sus herramientas (41), que el agente lleva en cada turno
• Definiciones de herramientasB · 83 de 100
• Resultados tipados0 de 41 herramientasdeclaran outputSchema: el resultado llega tipado y se lee de una vez

• Sin indicar si solo lee o puede destruir: 41 de 41

Un programa comprueba el servidor una vez al día: initialize y tools/list, sin modelo. Los tokens son la longitud de las definiciones, a unos cuatro caracteres por token. La nota promedia seis comprobaciones del nombre, la descripción, el esquema y las anotaciones de cada herramienta; dice lo bien descritas que están, no si funcionan. La nota pondera solo lo medido: si responde (30%), si hace el trabajo del producto (25%), definiciones (20%), contexto (10%) y uso (15%). Lo que no se midió queda fuera, y una instrucción oculta limita la nota a 40. El estado de los servidores MCP de los proveedores: método y números →

• whoami

  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.

• list_tools

  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.

• get_tool

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

• deploy

  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…

• pull

  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.

• logs

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

• releases

  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.

• rollback

  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.

• restart

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

• share

  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…

• unshare

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

• request_access

  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.

• access_requests

  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.

• allow_request

  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.

• set_access

  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.

• secrets_list

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

• secrets_set

  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.

• secrets_delete

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

• users_list

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

• users_add

  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…

• users_invite

  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…

• users_remove

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

• domains_list

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

• domain_check

  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.

• domain_buy

  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.

• domain_renewals

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

• domain_renewal_set

  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.

• domain_attach

  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.

• domain_point

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

• domain_primary

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

• domain_dns

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

• domain_repoint

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

• domain_detach

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

• usage

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

• capacity

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

• billing

  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.

• prices

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

• referral

  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).

• topup

  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…

• card_link

  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.

• delete_tool

  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.