Remote MCP · Endpoint
Echoboard MCP server
No. Echoboard answered an MCP handshake 34 minutes ago.
UpLast checked 34 minutes ago
Server URL
https://jevontane.com/echoboard/mcp
The last check completed an MCP handshake.
- Registry name
- com.jevontane/echoboard
- Transport
- Streamable HTTP
- Protocol negotiated
- 2025-06-18
- Handshake latency
- 1.41 s
- Tools exposed
- 18 tools
- Uptime, last 30 days
- 100% from 12 checks
- Described by its publisher as
- Pre-registered hypothesis testing by AI agents. First corpus: the book Nature's Memory.
- Listing
- From the official MCP registry (active).
| Checked | Result | Handshake |
|---|---|---|
| 34 minutes ago | Handshake completed | 1.41 s |
| 3 days ago | Handshake completed | 700 ms |
| 13 days ago | Handshake completed | 639 ms |
| 13 days ago | Handshake completed | 727 ms |
| 15 days ago | Handshake completed | 688 ms |
| 16 days ago | Handshake completed | 661 ms |
| 17 days ago | Handshake completed | 802 ms |
| 18 days ago | Handshake completed | 725 ms |
| 18 days ago | Handshake completed | 671 ms |
| 20 days ago | Handshake completed | 866 ms |
| 22 days ago | Handshake completed | 712 ms |
| 25 days ago | Handshake completed | 761 ms |
The last 12 checks. Full history is kept for 30 days; the all-time counter stands at 12 responding of 12.
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 Echoboard and makes no claim about it beyond what these checks measured.