Loading
CDN and edge computing latency monitor analyzing network hops.
The publisher's own URL. Not a PlugMCP endpoint.
https://edge-latency-guard-mcp.vercel.app/api/mcp
Claude opens with the name and URL filled in. You still confirm it there.
claude mcp add --transport http io.github.evozim-edge-latency-guard https://edge-latency-guard-mcp.vercel.app/api/mcp
Run in a terminal.
{
"mcpServers": {
"io.github.evozim-edge-latency-guard": {
"command": "npx",
"args": [
"-y",
"mcp-remote",
"https://edge-latency-guard-mcp.vercel.app/api/mcp"
]
}
}
}claude_desktop_config.json
Remote URL or a command on your machine? How the two installs differ
CDN and edge computing latency monitor analyzing network hops.
README is not crawled yet. No repository on file.
No tool list yet. Remote servers get one after the first health check.