# Edge Network

> Deploy and manage Edge Network cloud: sites, VMs, storage, DNS, Shield, Assist. Agent self-signup.

- name: network.edge/mcp
- version: 1.0.0
- connection class: R0 (autonomous)
- trust: 80/100 flags: no-repository
- quality: 73/100 (needs work)
- owner: not claimed
- descriptor: https://api.protogrid.dev/v1/servers/network.edge%2Fmcp
- tools: https://api.protogrid.dev/v1/servers/network.edge%2Fmcp/tools

**An agent can connect right now, no human step.** Remote endpoint, no authentication, reachable on the last probe.

## Connection (mcpServers)

```json
{
  "mcpServers": {
    "edge": {
      "type": "http",
      "url": "https://edge.network/mcp",
      "headers": {
        "Authorization": "Bearer ${EDGE_TOKEN}"
      }
    }
  }
}
```

Placeholders to fill: `${EDGE_TOKEN}`.

## Trust

- hygiene: 80
- liveness: 100
- freshness: 85
- provenance: 55
- drivers: +dns-namespace +website +reachable +uptime-100% ~updated-59d-ago -no-repository
- Derived from observable signals (official registry feed and our own credential-free probes); no code audit performed.

## Quality 73/100 (needs work)

### protocol: 75 (weight 25)

- warn `protocol.modern`: newest supported version is 2025-03-26; 2026-07-28 not supported, older versions are deprecated until 2027-07-28
- n/a `protocol.stateless`: only applies to 2026-07-28 servers
- pass `protocol.transport`: streamable HTTP
- n/a `protocol.list_ttl`: only applies to 2026-07-28 servers

### authorization: n/a (weight 15)

- n/a `auth.prm`, `auth.as_metadata`, `auth.cimd`: no remote uses OAuth
- n/a `auth.secret_in_url`: no templated URL

### tool hygiene: 71 (weight 30)

- pass `tools.descriptions`: every tool has a description
- pass `tools.description_length`: descriptions are concise
- pass `tools.schemas`: every tool has an object input schema
- fail `tools.annotations`: no tool declares readOnlyHint or destructiveHint, so clients cannot tell safe calls from risky ones
- fail `tools.directory_hints`: no tool declares all four of readOnlyHint, destructiveHint, idempotentHint and openWorldHint; missing: edge_discover (readOnlyHint, destructiveHint, idempotentHint, openWorldHint); edge_get_vm (readOnlyHint, destructiveHint, idempotentHint, openWorldHint); edge_scale_project (readOnlyHint, destructiveHint, idempotentHint, openWorldHint); …
- pass `tools.token_cost`: about 3,939 tokens to load every tool
- pass `tools.api_dump`: tools are not a one-to-one API dump

### stability: 75 (weight 15)

- warn `stability.changes`: 6 tool changes in 30 days
- pass `stability.rug_pull`: no tool changed its meaning under the same name

### dependencies: n/a (weight 15)

- n/a `deps.known_vulns`, `deps.mcp_sdk_version`, `deps.resolvable`: no npm or PyPI package

- tools: 28, about 3,939 tokens to load them all
- tool set hash: d339e1df7f45df7640ca50313a84f130
- tools last changed: 2026-10-12T14:11:09.024Z
- badge: [![protogrid quality](https://protogrid.dev/badge/network.edge/mcp.svg)](https://protogrid.dev/servers/network.edge/mcp)
- Checks run on what our credential-free, read-only probes observe; tools are never called and no code audit is performed.

### Tool changes

- 2026-10-12 `edge_delete_dns_zone` added
  - PERMANENTLY delete a DNS zone and all its records; the domain stops resolving via Edge. Irreversible — only use when the user has clearly asked. Set confirm to true to execute. Requires the "delete" permission.
- 2026-10-12 `edge_delete_dns_record` added
  - Delete one DNS record from a zone.
- 2026-10-12 `edge_update_dns_record` added
  - Change an existing DNS record in place — e.g. repoint an A record when a VM gets a new IP. Prefer this over adding a second record. Only the fields you pass are changed. Record ids come from the zone detail (GET /agent/dns/zones/{id}).
- 2026-10-12 `edge_delete_vm` added
  - PERMANENTLY delete one VM, its disk and its IP. Irreversible — only use when the user has clearly asked. Set confirm to true to execute; without it the call returns a summary of what would be deleted. Requires the "delete" permission.
- 2026-10-12 `edge_rename_vm` added
  - Change the display name of a VM (does not change the guest hostname).
- 2026-10-12 `edge_vm_power` added
  - Start, stop, restart, suspend, resume or hard-reset a VM. Stopped VMs keep their disk and IP and are still billed. Returns the VM with its new status.

Full history: https://api.protogrid.dev/v1/servers/network.edge%2Fmcp/changes

## Remotes

- https://edge.network/mcp (streamable-http, auth none, reachable true, uptime30d 1)

## Packages

_none_

## Tools (28)

- `edge_account_status`: Check whether the connected account is a self-signed-up guest (explore tier) or fully claimed, and how to unlock it.
- `edge_add_dns_record`: Add a DNS record to a zone.
- `edge_create_assist_site`: Create an Edge Assist site: AI answers for a website, grounded in its own content. Free tier: 1 site, 250 answered questions/month. Returns the sitekey and a one-line embed snippet.
- `edge_create_bucket`: Create an object storage bucket (S3-compatible). Free tier includes a limited number of buckets.
- `edge_create_dns_zone`: Create a DNS zone for a domain on Edge authoritative DNS. Free.
- `edge_create_shield_widget`: Create an Edge Shield widget to protect a form or page from bots. Free. Returns the sitekey, the secret (shown once — store it server-side), and a ready-to-paste embed snippet.
- `edge_delete_dns_record`: Delete one DNS record from a zone.
- `edge_delete_dns_zone`: PERMANENTLY delete a DNS zone and all its records; the domain stops resolving via Edge. Irreversible — only use when the user has clearly asked. Set confirm to true to execute. Requires the "delete" permission.
- `edge_delete_vm`: PERMANENTLY delete one VM, its disk and its IP. Irreversible — only use when the user has clearly asked. Set confirm to true to execute; without it the call returns a summary of what would be deleted. Requires the "delete" permission.
- `edge_deploy_app`: Deploy a full application on a VM: provisions compute, runs a setup script, and optionally adds CDN and DNS. This is BILLABLE — always dry_run first and report the monthly cost to the user. Pass ssh_key (a public key string) to enable SSH access.
- `edge_deploy_static_site`: Deploy a static website to Edge in one call: creates a storage bucket, uploads files (or clones a git repo), configures the global CDN with SSL, and wires DNS if the zone is on Edge. Free tier covers it. Provide either files (base64) or a git repo.
- `edge_discover`: Get everything about the connected Edge account: plan, budget, enabled products with limits and regions, current projects, and full API documentation. Call this first in every session.
- `edge_get_vm`: Get one VM: live status, metrics, IPs, attached SSH keys, and the ready-to-use SSH command. Poll until status is "running" before attempting SSH.
- `edge_list_assist_sites`: List Edge Assist sites (AI answers widget) with usage and index status.
- `edge_list_buckets`: List storage buckets on the account.
- `edge_list_dns_zones`: List DNS zones on the account.
- `edge_list_projects`: List all projects (groupings of resources) on the connected Edge account.
- `edge_list_shield_widgets`: List Edge Shield widgets (free, privacy-first CAPTCHA alternative).
- `edge_list_vms`: List all virtual machines on the account with status, size, and IPs.
- `edge_project_health`: Comprehensive health check for every resource in a project: status, metrics, and actionable suggestions.
- `edge_rename_vm`: Change the display name of a VM (does not change the guest hostname).
- `edge_request_claim`: Nominate the human operator of a self-signed-up (explore tier) account. They receive an email with a claim link; claiming unlocks billable resources and stops the ~7 day auto-purge. Ask the user for their email address first.
- `edge_scale_project`: Scale the compute resources in a project up or down. BILLABLE — dry_run first and report the cost change to the user.
- `edge_teardown_project`: PERMANENTLY delete a project and every resource in it (VMs, buckets, CDN deployments, DNS zones). Irreversible — only use when the user has clearly asked. Set confirm to true to execute.
- `edge_update_deployment`: Update an existing deployment: upload changed files and optionally purge the CDN cache.
- `edge_update_dns_record`: Change an existing DNS record in place — e.g. repoint an A record when a VM gets a new IP. Prefer this over adding a second record. Only the fields you pass are changed. Record ids come from the zone detail (GET /agent/dns/zones/{id}).
- `edge_upload_files`: Upload files to an existing storage bucket.
- `edge_vm_power`: Start, stop, restart, suspend, resume or hard-reset a VM. Stopped VMs keep their disk and IP and are still billed. Returns the VM with its new status.