Bordet MCP server

• Registry nameai.bordet/bordetverified in the MCP registry

The registry name sits under bordet.ai. The registry only lets a publisher use that namespace after proving control of the domain through DNS or HTTP.

• Stateanswerschecked 2026-10-27
• Tools11
• Server calls itselfbordet-mcp
• Server version1.1.0
• Protocol version2025-06-18

On 2026-10-27 the server answered initialize and tools/list without a sign-in. First answer in 234 ms.

• Its tools do every use case we checked: draft and critique a product plan with several models; record team decisions so they are not relitigated.
• Checked on 1 of the 7 days it takes to judge reliability.

Said by rules from the measurements above. The likely first call is a model's pick from the tool list; read its description before relying on it.

• INITE MCP scoreafter a weeka score needs 7 daily checks: 1 so far
• What an agent can do with it2 of 2 use cases
• Answeredmeasuring1 of the 7 daily checks it takes to print a share
• Median first answer249 ms
• Space in an agent's context≈ 1,136 tokensthe definitions of all its tools (11), which an agent carries on every turn
• Tool definitionsB · 86 of 100
• Typed results0 of 11 toolsdeclared outputSchema: results come typed, read once

• Parameters without a description: in 9 of 11

A program checks the server once a day: initialize and tools/list, no model. Tokens are the definitions' length at about four characters a token. The grade averages six checks of every tool's name, description, schema and annotations; it says how well the tools are described, not whether they work. The score weighs what was measured and nothing else: answering (25%), doing the product's job (25%), definitions (20%), context (10%), use (10%) and how readily a client connects (10%). A part that was not measured is left out, and a hidden instruction caps the score at 40. The state of vendors' MCP servers: method and numbers →

• list_members

  List the AI members of this Bordet boardroom (name, role, model, capabilities).

• get_project_state

  The room's curated living memory: objective, status, constraints, active focus, open questions.

• get_decisions

  The room's append-only decisions log (newest first). Check this before re-debating anything.

• search_memory

  Semantic search over the room's long-term memory facts.

• get_recent_messages

  The last messages in the room's main thread (who said what, when; images noted). Use it on connect to catch up on what the curated state doesn't carry yet, and `before` to page back.

• ask_member

  Ask one board member by name (e.g. 'Critic'). The reply is persisted in the room and remembered.

• ask_room

  Ask the boardroom: members reply in parallel with independent takes (capped at 3 members per call; pass 'members' to pick which).

• log_decision

  Append a decision to the room's log. It lands UNCONFIRMED; the human confirms it in the room.

• declare_seat

  Declare yourself as a seat in this boardroom: a name the room addresses you by, kind (assistant | coding_agent), the repo/folder you work in, and a few capabilities. Idempotent; call on connect.

• await_mention

  Long-poll (up to 50s) for messages addressed to your seat (@<your name>, @everyone, or a member handing you work). Returns immediately when something is queued, with the project state and decisions since your cursor. Call it in a loop to…

• post_update

  Post a message to the room as your seat: progress, a result (what changed, where, how to verify), or a question for the humans. Open with a member's name ("Grok, …") and that member replies in the room (metered, counts as one of your…