Remote MCP · Endpoint
app.blip-board/blipboard MCP server
No. app.blip-board/blipboard answered an MCP handshake 1 hour ago.
UpLast checked 1 hour ago
Server URL
https://blip-board.app/mcp
The last check completed an MCP handshake.
- Registry name
- app.blip-board/blipboard
- Transport
- Streamable HTTP
- Protocol negotiated
- 2025-06-18
- Handshake latency
- 200 ms
- Tools exposed
- 5 tools
- Uptime, last 30 days
- 100% from 19 checks
- Described by its publisher as
- Ambient split-flap display board agents push text to; humans watch it on any screen.
- Website
- https://blip-board.app/
- Listing
- From the official MCP registry (active).
| Checked | Result | Handshake |
|---|---|---|
| 1 hour ago | Handshake completed | 200 ms |
| 10 hours ago | Handshake completed | 284 ms |
| 1 day ago | Handshake completed | 225 ms |
| 2 days ago | Handshake completed | 246 ms |
| 4 days ago | Handshake completed | 162 ms |
| 4 days ago | Handshake completed | 168 ms |
| 5 days ago | Handshake completed | 256 ms |
| 6 days ago | Handshake completed | 239 ms |
| 8 days ago | Handshake completed | 788 ms |
| 11 days ago | Handshake completed | 221 ms |
| 13 days ago | Handshake completed | 168 ms |
| 16 days ago | Handshake completed | 189 ms |
| 18 days ago | Handshake completed | 182 ms |
| 20 days ago | Handshake completed | 160 ms |
| 22 days ago | Handshake completed | 207 ms |
| 24 days ago | Handshake completed | 295 ms |
| 26 days ago | Handshake completed | 237 ms |
| 27 days ago | Handshake completed | 261 ms |
| 29 days ago | Handshake completed | 299 ms |
The last 19 checks. Full history is kept for 30 days; the all-time counter stands at 31 responding of 31.
How to read this
- ·Handshake latency is one measurement from one probe, from our infrastructure. It is a smoke signal about the endpoint, not a benchmark of your own connection to it.
- ·An authentication challenge counts as responding. A hosted server that refuses an anonymous prober is behaving correctly.
- ·A tool count of “behind credentials” means the handshake worked but listing tools needed a token we do not hold.
- ·Uptime covers the last 30 days of our own checks, at most one an hour, and says how many checks it is drawn from.
Listing data comes from the official MCP registry. Glide is not affiliated with app.blip-board/blipboard and makes no claim about it beyond what these checks measured.