Remote MCP · Endpoint

Edge MCP server

No. Edge answered an MCP handshake 56 minutes ago.

UpLast checked 56 minutes ago

Server URL

https://getedge.cc/mcp

The last check completed an MCP handshake.

Registry name
io.github.getedgehq/edge
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
342 ms
Tools exposed
16 tools
Uptime, last 30 days
100% from 13 checks
Described by its publisher as
Gives your agent the right public skill for each task and loads it on demand.
Website
https://getedge.cc/
Listing
From the official MCP registry (active).
Recent checks of Edge
CheckedResultHandshake
56 minutes agoHandshake completed342 ms
1 day agoHandshake completed342 ms
2 days agoHandshake completed452 ms
5 days agoHandshake completed360 ms
8 days agoHandshake completed344 ms
10 days agoHandshake completed149 ms
12 days agoHandshake completed361 ms
14 days agoHandshake completed435 ms
16 days agoHandshake completed367 ms
18 days agoHandshake completed339 ms
20 days agoHandshake completed336 ms
22 days agoHandshake completed356 ms
23 days agoHandshake completed138 ms

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

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.

Related

All hosted MCP serversGlide connector for AI assistantsGlide for AI agents

Listing data comes from the official MCP registry. Glide is not affiliated with Edge and makes no claim about it beyond what these checks measured.