Remote MCP · Endpoint

Edgepedia MCP server

No. Edgepedia answered an MCP handshake 10 hours ago.

UpLast checked 10 hours ago

Server URL

https://www.edgechat.ai/mcp

The last check completed an MCP handshake.

Registry name
ai.edgechat/edgepedia
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
93 ms
Tools exposed
5 tools
Uptime, last 30 days
100% from 17 checks
Described by its publisher as
Search and read Edgepedia, a free and growing encyclopedia with citations. No key.
Listing
From the official MCP registry (active).
Recent checks of Edgepedia
CheckedResultHandshake
10 hours agoHandshake completed93 ms
2 days agoHandshake completed95 ms
4 days agoHandshake completed61 ms
5 days agoHandshake completed67 ms
7 days agoHandshake completed54 ms
8 days agoHandshake completed52 ms
9 days agoHandshake completed56 ms
12 days agoHandshake completed56 ms
13 days agoHandshake completed52 ms
15 days agoHandshake completed64 ms
16 days agoHandshake completed49 ms
17 days agoHandshake completed61 ms
18 days agoHandshake completed51 ms
19 days agoHandshake completed103 ms
20 days agoHandshake completed47 ms
21 days agoHandshake completed90 ms
23 days agoHandshake completed59 ms

The last 17 checks. Full history is kept for 30 days; the all-time counter stands at 17 responding of 17.

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 Edgepedia and makes no claim about it beyond what these checks measured.