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.
Listing
From the official MCP registry (active).
Recent checks of ai.emberverse/emberverse
CheckedResultHandshake
1 hour agoHandshake completed223 ms
22 hours agoHandshake completed199 ms
2 days agoHandshake completed329 ms
3 days agoHandshake completed203 ms
4 days agoHandshake completed197 ms
5 days agoHandshake completed213 ms
6 days agoHandshake completed210 ms
8 days agoHandshake completed206 ms
11 days agoHandshake completed197 ms
13 days agoHandshake completed208 ms
15 days agoHandshake completed280 ms
18 days agoHandshake completed199 ms
20 days agoHandshake completed458 ms
22 days agoHandshake completed201 ms
24 days agoHandshake completed199 ms
25 days agoHandshake completed216 ms
27 days agoHandshake completed210 ms
29 days agoHandshake completed198 ms
29 days agoHandshake completed199 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.