Edge-Latency-Guard

io.github.EvozimPublished by GitHub account Evozimv1.0.0Updated Oct 24, 2026

CDN and edge computing latency monitor analyzing network hops.

The publisher's own server: Edge Network

Overview

AI-generated overview

A remote MCP server that monitors CDN and edge computing latency by analyzing network hops, with a paid premium settlement option.

What you can do
Analyze CDN and edge computing latency across network hops. Report on network hop paths to help locate where delay occurs. Support a premium settlement mode that requires a payment signature. No individual tools are listed in the manifest, so exact operations are not documented.
When to use it
Useful when you want an assistant to check or discuss CDN and edge latency and hop-level network delay, and you are willing to provide a payment signature for premium settlement.
Requirements
Connects to a hosted remote endpoint over SSE; no local package or runtime is needed. Premium settlement requires a payment-signature header containing a Base64-encoded EIP-3009 TransferWithAuthorization signature. No other authentication is declared.
Before you install
The server asks for a payment-signature header, which is a cryptographic authorization that can move funds; only sign amounts and recipients you intend. It is a third-party hosted endpoint, so requests and any data you send pass through that operator. Tool behavior is undocumented in the manifest.

Installation

In SourceWeft

  1. Open Edge-Latency-Guard in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Web executable via SSE. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/io.github.Evozim%2Fedge-latency-guard/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "edge-latency-guard": {
      "type": "sse",
      "url": "https://edge-latency-guard-mcp.vercel.app/api/mcp"
    }
  }
}

Tools

0
SourceWeft has not read this server's tools yet.

Version history

1
  1. v1.0.0LatestSep 16, 2026

Score

67% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listedRequired15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.

Other Edge integrations