mcpbeat

Edge-Latency-Guard MCP Server

io.github.Evozim/edge-latency-guard
answering

Edge-Latency-Guard is answering right now. Last checked 10 min ago.

CDN and edge computing latency monitor analyzing network hops.

Uptime history 45 hours of history
45 hours agonow
100.0%
Uptime 24h
91 of 91 checks
—
Tools
hidden behind auth
92 ms
Response time
average over 24h
API key or OAuth
Access
sse

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 10 min ago.

run in your terminal
claude mcp add edge-latency-guard --transport http https://edge-latency-guard-mcp.vercel.app/api/mcp
~/Library/Application Support/Claude/claude_desktop_config.json
{
  "mcpServers": {
    "edge-latency-guard": {
      "url": "https://edge-latency-guard-mcp.vercel.app/api/mcp"
    }
  }
}
~/.codex/config.toml
[mcp_servers.edge-latency-guard]
url = "https://edge-latency-guard-mcp.vercel.app/api/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "edge-latency-guard": {
      "url": "https://edge-latency-guard-mcp.vercel.app/api/mcp"
    }
  }
}
.vscode/mcp.json
{
  "mcpServers": {
    "edge-latency-guard": {
      "url": "https://edge-latency-guard-mcp.vercel.app/api/mcp"
    }
  }
}

This endpoint answered with an authorization challenge — the server is running, but you need an API key or OAuth to use it.

Endpoints

URLTransportStateLatencyChecked
https://edge-latency-guard-mcp.vercel.app/api/mcp sse needs key 111 ms 10 min ago

Edge-Latency-Guard — questions

Answers built from our own checks of this server.

Why is there no tool list for Edge-Latency-Guard?
The server answered our handshake with an authorization challenge, so it is running — but it will not describe its tools to an anonymous client. To see them you need to connect with your own credentials. We record it as alive, not as broken: 100.0% of checks in the last 24 hours got a reply.
Is Edge-Latency-Guard working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 91 of 91 checks got a reply (100.0%), average response time 92 ms. The bar chart above shows every period we have measured.
How do I connect Edge-Latency-Guard?
Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address. You will need your own key or an OAuth login: it refuses anonymous clients.
Does Edge-Latency-Guard need an API key?
Yes. Every time we knock, Edge-Latency-Guard answers with an authorization challenge instead of its tool list — that is how we know it is running and gated rather than broken. Bring your own credentials and it will talk.
How fast is Edge-Latency-Guard?
It answers our handshake in 92 ms on average, which is faster than 86% of all working MCP servers we measure. That puts it in the quick quarter of the ecosystem. The comparison comes from our own checks across the whole registry, every 15 minutes.