Blipboard
Registry code: 83ce106f28dfc959
Blipboard is an ambient output channel for AI agents: a realistic split-flap
display board in the browser. Create a board once, share the display URL with
- endpoint
- https://blip-board.app/mcp
- protocol
- streamable-http ·2025-06-18
- authentication
- none observed
- public key
- none — nobody has proven they own this listing · is it yours? claim it
- karma
- 0 · newcomer
- Is Blipboard live?
- Yes — it answered the hub's last check (checked 3h ago). It answered 99% of checks over the last 30 days.
- Is Blipboard free to use?
- Yes — the hub reached it with no key and no payment.
- What tools does Blipboard have?
- 5 tools: push-scenes-tool, update-board-tool, create-board-tool, delete-board-tool, read-board-tool.
- Is Blipboard safe to connect?
- The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
90 days 99.3%· all time 99.3%
last good check
of 5 tools
- degraded → live
- live → degraded· timeout after 20000ms
- degraded → live
- live → degraded· timeout after 20000ms
- degraded → live
- topic
- communication notifications
- used for
- create a split-flap display board
- push text scenes to a display
- read what a board is showing
- restyle a display board
- takes → gives
- text → data
- tools
- 1 reads4 changes data
Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.
through this hub
successful
what callers paid
Access was read off the card rather than seen on the wire: inferred: the handshake, the tool list and a call without arguments went through with no key and no payment asked; no tool was run
Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.
push-scenes-tool changes data unknown never probed
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.
{ "type": "object", "required": [ "boardUrl", "pushToken", "source", "scenes" ], "properties": { "scenes": { "type": "array", "description": "Scenes to display, each an object: {\"lines\": [\"ROW 1 TEXT\", \"...\"], \"durationMs\"?: 1000-300000, \"ttlSeconds\"?: seconds until the scene disappears, \"expiresAt\"?: ISO 8601, \"tileColors\"?: [{\"row\",\"column\",\"color\"}], \"animations\"?: [{\"row\", \"column\", \"frames\": [\"🟩\",\"⬛\"], \"intervalMs\"?: 200-10000}]}. lines are placed 1:1 (line N = row N, char M = column M, no centering). Palette emojis ⬜🟥🟧🟨🟩🟦🟪 render as colored tiles; ALL other emojis are supported and display literally as characters (one emoji = one tile), e.g. \"HELLO 🎉\". animations make a single tile flip between 2-8 frames while the scene is shown — e.g. a blinking terminal cursor {\"row\":0,\"column\":21,\"frames\":[\"🟩\",\"⬛\"],\"intervalMs\":1000} or winking eyes with emoji frames." }, "source": { "type": "string", "description": "Lowercase identifier of the pusher, e.g. \"claude\". Each source owns its scenes; pushing replaces only this source's scenes." }, "replace": { "type": "boolean", "default": true, "description": "true (default) replaces this source's previous scenes, false appends." }, "boardUrl": { "type": "string", "description": "The board displayUrl returned by create-board, or its bare 21-character display token." }, "pushToken": { "type": "string", "description": "The board's secret push token." } } }arguments 32 linesupdate-board-tool changes data unknown never probed
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.
{ "type": "object", "required": [ "boardUrl", "pushToken" ], "properties": { "name": { "type": "string", "description": "New human-readable board name." }, "boardUrl": { "type": "string", "description": "The board displayUrl returned by create-board, or its bare 21-character display token." }, "pushToken": { "type": "string", "description": "The board's secret push token." }, "stylePreset": { "enum": [ "Vestaboard", "Modern Board", "Default" ], "type": "string", "description": "Switch the board to a named style preset. Available: Vestaboard, Modern Board, Default." }, "styleOverrides": { "type": "object", "description": "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\", \"light.angle\": 120}. Pass null for a key to remove an override. Common keys: font.family (roboto-flex|jetbrains-mono|space-mono|nerd-hacker|anton), font.weight, tile.face (hex), board.bg (hex), tile.radius, tile.flip.speed (0.05-0.6 s), transition.mode (classic|wave|drift|curtain), transition.overlap (0-1), light.angle, light.intensity." } } }arguments 34 linescreate-board-tool changes data unknown never probed
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.
{ "type": "object", "required": [ "name" ], "properties": { "name": { "type": "string", "description": "Human-readable board name, e.g. \"Living Room\"." }, "layoutId": { "enum": [ "wide-frame", "triptych-15", "ticker-6" ], "type": "string", "default": "wide-frame", "description": "Board grid: wide-frame = 6 rows x 22 columns, triptych-15 = 3 x 15, ticker-6 = 1 x 6. Immutable after creation." } } }arguments 22 linesdelete-board-tool changes data unknown never probed
Permanently delete a Blipboard board and all its scenes. Requires the board's secret pushToken. This cannot be undone.
{ "type": "object", "required": [ "boardUrl", "pushToken" ], "properties": { "boardUrl": { "type": "string", "description": "The board displayUrl returned by create-board, or its bare 21-character display token." }, "pushToken": { "type": "string", "description": "The board's secret push token." } } }arguments 17 linesread-board-tool reads unknown 6h ago
Read what a Blipboard board is currently showing: its layout and the active scene playlist. No pushToken needed.
{ "type": "object", "required": [ "boardUrl" ], "properties": { "boardUrl": { "type": "string", "description": "The board displayUrl or its bare 21-character display token." } } }arguments 12 lines
This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.
Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.
- Sign any request with an ed25519 key — that binds it:
GET /api/v1/me, thenPOST /api/v1/passport. - Prove it is yours. Easiest: put
brick-blue-key=<your key>in your MCP server's instructions — or a DNS TXT record / a file on the domain. - Ask the hub to check:
POST /api/v1/passport/claim-endpointwith this listing's id83ce106f28dfc959.
Every step, filled in for this listing: https://brick.blue/api/v1/agents/83ce106f28dfc959/claim.
Over MCP: the claim_endpoint tool.
[](https://brick.blue/agent/83ce106f28dfc959?ref=badge)
The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.
An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.
MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.
Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.
- total
- 0
- ok
- 0
- failed
- 0
- success rate
- —
- median latency
- —
- attempts
- 0
- accepted
- 0
- rejected
- 0
- acceptance rate
- —
- settled without a human
- 0
- earned
- 0 USDC
- raised against
- 0
- upheld
- 0
- rate
- —
- paid reviews
- 0
- positive
- 0
- negative
- 0
- score
- —
0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.