app.blip-board/blipboard
REMOTE · BLIP-BOARD.APP
Ambient split-flap display board agents push text to; humans watch it on any screen.
Available components
Last scanned (9 minutes ago)
Scores higher than 62% of remote servers
Reachable. Last reached 22 Nov 2026.
Category IoT and Hardware
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 Security57
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 4 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- 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 Usability64
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 1443 tokens (~288/item across 5 items; 5 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- 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 Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety75
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- 0 of 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "delete-board-tool" implies "delete" and declares no destructiveHint at all, which the MCP spec reads as destructive by default. See how to fix → Fail
- An AI judge read all 6 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
Checks we ran (12)
- TLS certificate
- HTTPS
- HSTS header
- DNSSEC
- Transport
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Checks we could not complete (1)
These are gaps on our side, not findings about this hosted endpoint. We only credit what we can confirm, so a category made up entirely of them scores 0.
- Authorization in Endpoint SecurityAuthorisation not fully verified: no authorisation is required to call this server, and 4 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.
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.
- 9 Nov 26 +1
- Stability: 0.97 → pass security
- 8 Nov 26 −1
- Stability: pass → 0.97 functional
- 6 Nov 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
- 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
- 26 Aug 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 Aug 26 0
- Stability: 0.97 → pass security
- 11 Aug 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 22 Nov 2026 · Probed https://blip-board.app/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=blip-board.app | CN=WE1,O=Google Trust Services,C=US | 3 Nov 2026 | 1 Feb 2027 | ECDSA 256 | ECDSA-SHA256 | 3477cf46828248910ee9ad804dad45c7 |
| SANs: blip-board.app | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of blip-board.app. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| app. | DS published | 23684 | 8 | Verified |
| blip-board.app. | 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 |
| Header | Value |
|---|---|
| x-content-type-options | nosniff |
| x-frame-options | deny |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://blip-board.app/mcp | Verified | 200 | |
| http (plaintext) | http://blip-board.app/mcp | HTTPS enforced | 301 | https://blip-board.app/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 →
create-board-tool Create Board Tool ~120
Create a new Blipboard split-flap display board. Returns the display URL (open it on any screen — that IS the board, safe to share) and a secret pushToken used to push content later. No account needed.
| Name | Type | Req | Description |
|---|---|---|---|
| layoutId | string | – | Board grid: wide-frame = 6 rows x 22 columns, triptych-15 = 3 x 15, ticker-6 = 1 x 6. Immutable after creation. |
| name | string | yes | Human-readable board name, e.g. "Living Room". |
No output schema declared.
No examples provided.
delete-board-tool Delete Board Tool ~74
Permanently delete a Blipboard board and all its scenes. Requires the board's secret pushToken. This cannot be undone.
| Name | Type | Req | Description |
|---|---|---|---|
| boardUrl | string | yes | The board displayUrl returned by create-board, or its bare 21-character display token. |
| pushToken | string | yes | The board's secret push token. |
No output schema declared.
No examples provided.
push-scenes-tool Push Scenes Tool ~379
Push text scenes to a Blipboard board. Scenes replace your source's previous scenes by default and rotate as a playlist on the display. Requires the board's secret pushToken.
| Name | Type | Req | Description |
|---|---|---|---|
| boardUrl | string | yes | The board displayUrl returned by create-board, or its bare 21-character display token. |
| pushToken | string | yes | The board's secret push token. |
| replace | boolean | – | true (default) replaces this source's previous scenes, false appends. |
| scenes | array | yes | Scenes to display, each an object: {"lines": ["ROW 1 TEXT", "..."], "durationMs"?: 1000-300000, "ttlSeconds"?: seconds until the scene disappears, "expiresAt"?: ISO 8601, "tileColors"?: [{"row","colu… |
| source | string | yes | Lowercase identifier of the pusher, e.g. "claude". Each source owns its scenes; pushing replaces only this source's scenes. |
No output schema declared.
No examples provided.
read-board-tool Read Board Tool ~53
Read what a Blipboard board is currently showing: its layout and the active scene playlist. No pushToken needed.
| Name | Type | Req | Description |
|---|---|---|---|
| boardUrl | string | yes | The board displayUrl or its bare 21-character display token. |
No output schema declared.
No examples provided.
update-board-tool Update Board Tool ~323
Change a Blipboard board's look without recreating it: switch to a named style preset and/or set fine-grained style overrides (fonts, tile colors, flip speed, transitions). The open display picks the change up within ~10 seconds. Layout stays immutable. Requires the board's secret pushToken.
| Name | Type | Req | Description |
|---|---|---|---|
| boardUrl | string | yes | The board displayUrl returned by create-board, or its bare 21-character display token. |
| name | string | – | New human-readable board name. |
| pushToken | string | yes | The board's secret push token. |
| styleOverrides | object | – | Fine-grained style keys merged on top of the preset, e.g. {"board.bg": "#0a0a0a", "tile.face": "#1a3a2a", "font.family": "jetbrains-mono", "tile.flip.speed": 0.08, "transition.mode": "curtain", "ligh… |
| stylePreset | string | – | Switch the board to a named style preset. Available: Vestaboard, Modern Board, Default. |
No output schema declared.
No examples provided.
How do I install the app.blip-board/blipboard MCP server?
app.blip-board/blipboard is a hosted endpoint at https://blip-board.app/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 · blip-board.app
claude mcp add --transport http app-blip-board-blipboard 'https://blip-board.app/mcp'
What is the app.blip-board/blipboard MCP server?
app.blip-board/blipboard is an MCP server listed in the public MCP registry as app.blip-board/blipboard. Ambient split-flap display board agents push text to; humans watch it on any screen. This page covers its hosted endpoint (https://blip-board.app/mcp).
Is the app.blip-board/blipboard MCP server safe to use?
app.blip-board/blipboard scores 75 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 app.blip-board/blipboard MCP server expose?
app.blip-board/blipboard exposes 5 tools: create-board-tool, push-scenes-tool, read-board-tool, update-board-tool, delete-board-tool. Their descriptions and schemas cost roughly 949 tokens of context every time the server is loaded.
Does the app.blip-board/blipboard MCP server require authentication?
No. We connected to app.blip-board/blipboard without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the app.blip-board/blipboard MCP server still maintained?
app.blip-board/blipboard is still listed as active in the MCP registry. We last reached this channel on 22 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 app.blip-board/blipboard MCP server?
VerifyMCP ran 12 checks on app.blip-board/blipboard, covering TLS certificate, HTTPS, HSTS header, DNSSEC and 8 more. One item could not be completed, a gap on our side rather than a finding about app.blip-board/blipboard: Authorization. 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.