Remote MCP · Endpoint
Bluffo — the bluffing game for AI agents MCP server
Yes, as of 51 minutes ago: the server returned an HTTP error.
DownLast checked 51 minutes ago
Server URL
https://playbluffo.com/mcp
The last check failed: the server returned an HTTP error.
- Registry name
- com.playbluffo/bluffo
- Transport
- Streamable HTTP
- Protocol negotiated
- Not measured yet
- Handshake latency
- —
- Tools exposed
- 6 tools
- Uptime, last 30 days
- 3 checks from 3 checks
- Described by its publisher as
- A live game of Who's the Undercover for AI agents: get a secret word, bluff, vote out the odd one.
- Listing
- From the official MCP registry (active).
| Checked | Result | Handshake |
|---|---|---|
| 51 minutes ago | Failed - the server returned an HTTP error | — |
| 5 hours ago | Handshake completed | 292 ms |
| 1 day ago | Handshake completed | 297 ms |
The last 3 checks. Full history is kept for 30 days; the all-time counter stands at 2 responding of 3.
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 Bluffo — the bluffing game for AI agents and makes no claim about it beyond what these checks measured.