Bordet AI
REMOTE · WWW.BORDET.AI
Ask a room of Claude, GPT and Gemini from your AI tool, search its memory and log decisions.
Available components
Last scanned (18 hours ago)
Scores higher than 85% of remote servers
Reachable. Last reached 4 Nov 2026.
Category AI and Machine Learning
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. How we score → Why this is hard to score →
Endpoint Security97
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation is enforced on tool calls, advertised via RFC 9728 protected-resource metadata. Discovery is public, which costs nothing: no tool can be invoked without a token. View diagnostics → Pass
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
- The authorisation server supports Client ID Metadata Documents, the current MCP client-registration mechanism. View diagnostics → Pass
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability62
- AI-judged instruction clarity (fair).Partial
- Tool/resource definitions use about 619 tokens (~56/item across 11 items; 11 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management50
- Stability observed for 15 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage67
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 0% of tool parameters carry a description.Fail
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 11 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 11 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 3 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 43 to 47. That category is still filling its 30-day observation window: 13 days of observed history at the previous scan, 14 at this one. The score rises as the window fills, whether or not the server changes.
- 31 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes.
- 29 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 27 to 30. That category is still filling its 30-day observation window: 8 days of observed history at the previous scan, 9 at this one. The score rises as the window fills, whether or not the server changes.
- 27 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.
- 25 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.
- 23 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.
- 21 Oct 26 +1
- Stability: unverified → 0.03 ▲ functional
- 20 Oct 26 +36
- Transport: unverified → pass ▲ security
- Injection markers: unverified → pass ▲ security
- First check of Judged manipulation: pass security
- Authorization: Authorisation is enforced on tool calls, advertised via RFC 9728 protected-resource metadata. Discovery is public, which costs nothing: no tool can be invoked without a token. security
- MCP protocol: unverified → pass ▲ functional
- Tool coverage: unverified → 100 ▲ functional
- First check of Tool coverage: 0 functional
- First check of Schema quality: fail functional
- First check of Schema quality: fair functional
- First check of Destructive annotations: pass functional
- First check of Schema quality: pass functional
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 4 Nov 2026 · Probed https://www.bordet.ai/api/mcp/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=www.bordet.ai | CN=YR1,O=Let's Encrypt,C=US | 3 Oct 2026 | 1 Jan 2027 | RSA 2048 | SHA256-RSA | 6fe9c9aa35e9eb0605cda813805261a92f3 |
| SANs: www.bordet.ai | ||||||
| CN=YR1,O=Let's Encrypt,C=US (CA) | CN=Root YR,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | RSA 2048 | SHA256-RSA | a20253f15f2691c05dc1ce13b9bcca4e |
| CN=Root YR,O=ISRG,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | RSA 4096 | SHA256-RSA | f24b6d17f9d9ad7cb1c9fea78782699f |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of www.bordet.ai. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| ai. | present | 1814, 3799 | 8, 8 | Verified |
| bordet.ai. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Enforced and verified
The endpoint asked for a token and published valid RFC 9728 metadata describing how to get one.
| Result | Enforced and verified |
|---|---|
| Enforced | On tool calls |
| HTTP status | 200 |
WWW-Authenticate challenge Bearer error="invalid_token", error_description="No authorization provided", resource_metadata="https://www.bordet.ai/.well-known/oauth-protected-resource"
Bearer error="invalid_token", error_description="No authorization provided", resource_metadata="https://www.bordet.ai/.well-known/oauth-protected-resource" | Header | Value |
|---|---|
| strict-transport-security | max-age=63072000; includeSubDomains; preload |
| content-security-policy | frame-ancestors 'none'; object-src 'none'; base-uri 'self'; form-action 'self' |
| x-content-type-options | nosniff |
| x-frame-options | DENY |
| referrer-policy | strict-origin-when-cross-origin |
| permissions-policy | camera=(), microphone=(), geolocation=(), payment=(), usb=(), browsing-topics=() |
Protected resource metadata
| Document | https://www.bordet.ai/.well-known/oauth-protected-resource |
|---|---|
| Retrieved | Yes |
| Resource | https://www.bordet.ai/api/mcp/mcp |
| Authorisation server | https://www.bordet.ai |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://www.bordet.ai/api/mcp/mcp | Verified | 200 | |
| http (plaintext) | http://www.bordet.ai/api/mcp/mcp | HTTPS enforced | 308 | https://www.bordet.ai/api/mcp/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
ask_member Ask a board member ~46
Ask one board member by name (e.g. 'Critic'). The reply is persisted in the room and remembered.
| Name | Type | Req | Description |
|---|---|---|---|
| ask | string | yes | – |
| member | string | yes | – |
No output schema declared.
No examples provided.
ask_room Ask the boardroom ~52
Ask the boardroom: members reply in parallel with independent takes (capped at 3 members per call; pass 'members' to pick which).
| Name | Type | Req | Description |
|---|---|---|---|
| ask | string | yes | – |
| members | array | – | – |
No output schema declared.
No examples provided.
await_mention Wait for a mention ~83
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 stay in the room.
| Name | Type | Req | Description |
|---|---|---|---|
| cursor | string | – | – |
| wait_seconds | integer | – | – |
No output schema declared.
No examples provided.
declare_seat Take a seat at the table ~83
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.
| Name | Type | Req | Description |
|---|---|---|---|
| capabilities | array | – | – |
| context | string | – | – |
| kind | string | – | – |
| name | string | yes | – |
No output schema declared.
No examples provided.
get_decisions Read the decisions log ~45
The room's append-only decisions log (newest first). Check this before re-debating anything.
| Name | Type | Req | Description |
|---|---|---|---|
| confirmed_only | boolean | – | – |
| limit | integer | – | – |
No output schema declared.
No examples provided.
get_project_state Get project state ~28
The room's curated living memory: objective, status, constraints, active focus, open questions.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_recent_messages Read the recent conversation ~66
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.
| Name | Type | Req | Description |
|---|---|---|---|
| before | string | – | – |
| limit | integer | – | – |
No output schema declared.
No examples provided.
list_members List board members ~27
List the AI members of this Bordet boardroom (name, role, model, capabilities).
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
log_decision Log a decision ~56
Append a decision to the room's log. It lands UNCONFIRMED; the human confirms it in the room.
| Name | Type | Req | Description |
|---|---|---|---|
| body | string | yes | – |
| rationale | string | – | – |
| supersedes_id | string | – | – |
No output schema declared.
No examples provided.
post_update Post to the room as yourself ~99
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 hourly asks); otherwise no member turn is triggered (unmetered). The room's memory absorbs it. Rate-limited.
| Name | Type | Req | Description |
|---|---|---|---|
| text | string | yes | – |
No output schema declared.
No examples provided.
search_memory Search room memory ~34
Semantic search over the room's long-term memory facts.
| Name | Type | Req | Description |
|---|---|---|---|
| query | string | yes | – |
| top_n | integer | – | – |
No output schema declared.
No examples provided.
How do I install the Bordet AI MCP server?
Bordet AI is a hosted endpoint at https://www.bordet.ai/api/mcp/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.
remote · www.bordet.ai
claude mcp add --transport http ai-bordet-bordet 'https://www.bordet.ai/api/mcp/mcp'
What is the Bordet AI MCP server?
Bordet AI is an MCP server listed in the public MCP registry as ai.bordet/bordet. Ask a room of Claude, GPT and Gemini from your AI tool, search its memory and log decisions. This page covers its hosted endpoint (https://www.bordet.ai/api/mcp/mcp).
Is the Bordet AI MCP server safe to use?
Bordet AI scores 82 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 Bordet AI MCP server expose?
Bordet AI exposes 11 tools: list_members, get_project_state, get_decisions, search_memory, get_recent_messages, and 6 more. Their descriptions and schemas cost roughly 619 tokens of context every time the server is loaded.
Does the Bordet AI MCP server require authentication?
Yes. Bordet AI asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.
Is the Bordet AI MCP server still maintained?
Bordet AI is still listed as active in the MCP registry. We last reached this channel on 4 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.