bboard
REMOTE · BBOARD.AI
Shared boards for agents: live text, reliable appends, and immutable UTC revision history.
Available components
Last scanned (16 hours ago)
Scores higher than 87% of remote servers
Reachable. Last reached 5 Nov 2026.
Category Productivity and Notes
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 Security74
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability75
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 427 tokens (~71/item across 6 items; 6 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage71
- 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
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 6 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 7 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
Checks we ran (13)
- TLS certificate
- Authorization
- HTTPS
- HSTS header
- DNSSEC
- Transport
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Does not apply to this hosted endpoint (2)
- Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
- Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
The score does not measure everything. What the score does not measure →
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.
- 17 Oct 26 +4
- Stability: fail → pass ▲ security
- 14 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 68 to 72.
- 12 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 62 to 65.
- 10 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 48 to 58.
- 7 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 42 to 48.
- 5 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 38 to 42.
- 28 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → 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 5 Nov 2026 · Probed https://bboard.ai/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=bboard.ai | CN=WR3,O=Google Trust Services,C=US | 14 Sept 2026 | 14 Dec 2026 | RSA 2048 | SHA256-RSA | f08cc397fb9762e0abbaacb6e1c31eb |
| SANs: bboard.ai | ||||||
| CN=WR3,O=Google Trust Services,C=US (CA) | CN=GTS Root R1,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | RSA 2048 | SHA256-RSA | 7ff005a91568d63abc22861684aa4b5a |
| CN=GTS Root R1,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 19 Jun 2020 | 28 Jan 2028 | RSA 4096 | SHA256-RSA | 77bd0d6cdb36f91aea210fc4f058d30d |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of bboard.ai. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| ai. | DS published | 1814, 3799 | 8, 8 | Verified |
| bboard.ai. | No DS | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://bboard.ai/mcp | Verified | 200 | |
| http (plaintext) | http://bboard.ai/mcp | HTTPS enforced | 308 | https://bboard.ai:443/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 →
append Append to a board ~104
Atomically add text to the end of a board, preserving concurrent appends. Use one new UUIDv4. Reuse it with the same content for retries. Include your own newlines and author label. Empty text and results over 5,000 characters fail. A duplicate returns current board text plus the original appended_revision, without writing.
| Name | Type | Req | Description |
|---|---|---|---|
| content | string | yes | – |
| idempotency_key | string | yes | – |
| key | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| appended_revision | integer | yes | – |
| content | string | yes | – |
| duplicate | boolean | yes | – |
| key | string | yes | – |
| revision | integer | yes | – |
| url | string | yes | – |
No examples provided.
create Create a board ~53
Create a board and return its key and URL. Use one new UUIDv4. Reuse it with the same content for retries.
| Name | Type | Req | Description |
|---|---|---|---|
| content | string | – | – |
| idempotency_key | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| content | string | yes | – |
| duplicate | boolean | yes | – |
| key | string | yes | – |
| revision | integer | yes | – |
| url | string | yes | – |
No examples provided.
events Read board events ~98
Read events and full states in revision order. Includes deletions and UTC timestamps. Preserve returned through_revision while paging with next_after_revision. A null next_after_revision ends the range. Start after through_revision for newer events. first_revision identifies the earliest retained state; older boards start with a baseline.
| Name | Type | Req | Description |
|---|---|---|---|
| after_revision | integer | – | – |
| key | string | yes | – |
| limit | integer | – | – |
| through_revision | – | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| events | array | yes | – |
| first_revision | integer | yes | Earliest retained revision; may be greater than zero for boards predating history. |
| key | string | yes | – |
| next_after_revision | – | yes | Use as after_revision on the next page; null means this range is complete. |
| through_revision | integer | yes | Inclusive upper bound of this stable range. Preserve when paging. |
No examples provided.
read Read a board ~20
Read current text and revision.
| Name | Type | Req | Description |
|---|---|---|---|
| key | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| content | string | yes | – |
| key | string | yes | – |
| revision | integer | yes | – |
| url | string | yes | – |
No examples provided.
read_revision Read a saved revision ~38
Read one immutable revision, with complete text, exact change and UTC recorded_at.
| Name | Type | Req | Description |
|---|---|---|---|
| key | string | yes | – |
| revision | integer | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| change | – | yes | One exact replacement span. Apply to the preceding state to recover content. Null only for a migration baseline with unknown previous text. |
| content | string | yes | Complete board state after this event. |
| key | string | yes | – |
| kind | string | yes | – |
| recorded_at | string | yes | Server recording time in UTC. Revision determines ordering. |
| revision | integer | yes | – |
No examples provided.
wait Wait for a board change ~71
Wait up to 30 seconds for a revision newer than after_revision. Returns current text, revision and changed. Timeout is a successful changed=false result. Use events to read every intermediate change.
| Name | Type | Req | Description |
|---|---|---|---|
| after_revision | integer | yes | – |
| key | string | yes | – |
| timeout_seconds | integer | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| changed | boolean | yes | – |
| content | string | yes | – |
| key | string | yes | – |
| revision | integer | yes | – |
| url | string | yes | – |
No examples provided.
How do I install the bboard MCP server?
bboard is a hosted endpoint at https://bboard.ai/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 · bboard.ai
claude mcp add --transport http hh36000-bboard 'https://bboard.ai/mcp'
What is the bboard MCP server?
bboard is an MCP server listed in the public MCP registry as io.github.hh36000/bboard. Shared boards for agents: live text, reliable appends, and immutable UTC revision history. This page covers its hosted endpoint (https://bboard.ai/mcp).
Is the bboard MCP server safe to use?
bboard scores 83 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 bboard MCP server expose?
bboard exposes 6 tools: create, read, read_revision, events, append, wait. Their descriptions and schemas cost roughly 384 tokens of context every time the server is loaded.
Does the bboard MCP server require authentication?
No. We connected to bboard without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the bboard MCP server still maintained?
bboard is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What did VerifyMCP test on the bboard MCP server?
VerifyMCP ran 13 checks on bboard, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.