Edge-Latency-Guard MCP Server

by evozim Your server? Claim it

answering

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

CDN and edge computing latency monitor analyzing network hops.

Uptime history 52 days of history · worst day 99%

52 days agonow

100.0%

Uptime 24h

91 of 91 checks

—

Tools

hidden behind auth

91 ms

Response time

average over 24h

authentication required

Access

sse

Nothing serious here today

Today is the operative word: we check Edge-Latency-Guard every 15 minutes and re-read its code on every release. Watch it and you find out the day that stops being true.

Connect this server

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

Claude Code Claude Desktop Codex Cursor VS Code

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 it did not say what kind of credentials it expects.

Endpoints

URL	Transport	State	Latency	Checked
https://edge-latency-guard-mcp.vercel.app/api/mcp	sse	needs auth	95 ms	5 min ago

Alternatives to Edge-Latency-Guard

same job, measured the same way

CLIO Node Hardware

by iowarp

Node Hardware MCP - Comprehensive Hardware Monitoring and System Analysis for LLMs with...

local only

Domotz

by wyre-ai

MCP server for Domotz network monitoring — agents, devices, alerts, and network discovery.

local only

Domotz

by wyre-technology

MCP server for Domotz network monitoring — agents, devices, alerts, and network discovery.

local only

LibreNMS MCP

by mhajder

MCP server for LibreNMS network monitoring - query devices, ports, alerts, and manage infrastructure

837 installs/wk local only

MCP Kubernetes

by dockndevai

Kubernetes monitoring & ops for AI agents — safe-by-default access modes and guards.

58 installs/wk local only

Thunder Compute

by thunder-compute

GPU cloud platform — create, manage, and monitor instances, snapshots, SSH keys, and billing.

answering

PeppolStatus

by peppolstatus

Peppol market intelligence and network monitoring: migrations, provider churn, leads, and uptime.

62 tools answering

SiteGuardian

by gweber

EU-hosted website monitoring + 17-framework compliance MCP. One anonymous tool, four authenticated.

5 tools answering

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 91 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 credentials: 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 91 ms on average, which is faster than 90% 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.