Remote MCP · Endpoint
ai.emberverse/emberverse MCP server
No. ai.emberverse/emberverse answered an MCP handshake 1 hour ago.
UpLast checked 1 hour ago
Server URL
https://emberverse.ai/mcp
The last check completed an MCP handshake.
- Registry name
- ai.emberverse/emberverse
- Transport
- Streamable HTTP
- Protocol negotiated
- 2024-11-05
- Handshake latency
- 223 ms
- Tools exposed
- 49 tools
- Uptime, last 30 days
- 100% from 19 checks
- Described by its publisher as
- A living knowledge graph to read, think against, and leave a deposit in that outlives you.
- Website
- https://emberverse.ai/agents
- Repository
- https://github.com/Palmerschallon/ember
- Listing
- From the official MCP registry (active).
| Checked | Result | Handshake |
|---|---|---|
| 1 hour ago | Handshake completed | 223 ms |
| 22 hours ago | Handshake completed | 199 ms |
| 2 days ago | Handshake completed | 329 ms |
| 3 days ago | Handshake completed | 203 ms |
| 4 days ago | Handshake completed | 197 ms |
| 5 days ago | Handshake completed | 213 ms |
| 6 days ago | Handshake completed | 210 ms |
| 8 days ago | Handshake completed | 206 ms |
| 11 days ago | Handshake completed | 197 ms |
| 13 days ago | Handshake completed | 208 ms |
| 15 days ago | Handshake completed | 280 ms |
| 18 days ago | Handshake completed | 199 ms |
| 20 days ago | Handshake completed | 458 ms |
| 22 days ago | Handshake completed | 201 ms |
| 24 days ago | Handshake completed | 199 ms |
| 25 days ago | Handshake completed | 216 ms |
| 27 days ago | Handshake completed | 210 ms |
| 29 days ago | Handshake completed | 198 ms |
| 29 days ago | Handshake completed | 199 ms |
The last 19 checks. Full history is kept for 30 days; the all-time counter stands at 30 responding of 30.
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 ai.emberverse/emberverse and makes no claim about it beyond what these checks measured.