# Edge Network (remote · edge.network)

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

- Trust score: 76/100 (medium)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-20

## Components

- remote · `edge.network`: 76/100 (this document), [markdown](https://verifymcp.io/servers/network-edge-mcp/edge.md), [page](https://verifymcp.io/servers/network-edge-mcp/edge)

## Channel facts

- Endpoint: `https://edge.network/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.0`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-09-20.

- **Endpoint Security**: 63/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation not fully verified: no authorisation is required to call this server, and 22 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 77/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 2572 tokens (~116/item across 22 items; 22 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 93/100
  - Stability observed for 28 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 75/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - 0 of 2 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "edge_deploy_static_site" implies "deploy" and declares no destructiveHint at all, which the MCP spec reads as destructive by default.
  - An AI judge read all 23 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 40/100
  - Spec-recency check failed: implements MCP spec 2025-03-26; the latest is 2026-07-28.

## Install

### How do I install the Edge Network MCP server?

Edge Network is a hosted endpoint at https://edge.network/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add --transport http network-edge-mcp 'https://edge.network/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "network-edge-mcp": {
      "url": "https://edge.network/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "network-edge-mcp": {
      "type": "http",
      "url": "https://edge.network/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.network-edge-mcp]
url = "https://edge.network/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "network-edge-mcp": {
      "type": "remote",
      "url": "https://edge.network/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add network-edge-mcp --url 'https://edge.network/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  network-edge-mcp:
    url: "https://edge.network/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "network-edge-mcp": {
      "Transport": "http",
      "Url": "https://edge.network/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add network-edge-mcp -t streamable-http -u 'https://edge.network/mcp'
```

### Other

```json
{
  "mcpServers": {
    "network-edge-mcp": {
      "type": "http",
      "url": "https://edge.network/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-09-19 (score 76, +1)

No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-17 (score 75, +1)

No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-15 (score 74, +1)

No change was recorded against any check on this day. Stability & Change Management went from 73 to 77. That category is still filling its 30-day observation window: 22 days of observed history at the previous scan, 23 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-12 (score 73, +1)

No change was recorded against any check on this day. Stability & Change Management went from 63 to 67. That category is still filling its 30-day observation window: 19 days of observed history at the previous scan, 20 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-10 (score 72, +1)

No change was recorded against any check on this day. Stability & Change Management went from 57 to 60. That category is still filling its 30-day observation window: 17 days of observed history at the previous scan, 18 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-08 (score 71, +1)

No change was recorded against any check on this day. Stability & Change Management went from 50 to 53. That category is still filling its 30-day observation window: 15 days of observed history at the previous scan, 16 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-06 (score 70, +1)

No change was recorded against any check on this day. Stability & Change Management went from 43 to 47. That category is still filling its 30-day observation window: 13 days of observed history at the previous scan, 14 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-04 (score 69, +1)

No change was recorded against any check on this day. Stability & Change Management went from 37 to 40. That category is still filling its 30-day observation window: 11 days of observed history at the previous scan, 12 at this one. The score rises as the window fills, whether or not the server changes.

## MCP tools (22)

### `edge_discover` (~43 tokens)

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_deploy_static_site` (~271 tokens)

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.

Input parameters:

- `branch` (string): Git branch or tag (default: main)
- `domain` (string): Custom domain to serve from, e.g. "app.example.com". SSL is auto-provisioned.
- `dry_run` (boolean): Preview the action without executing it. Returns what would happen, including cost estimates. Always dry-run first for anything that costs money.
- `files` (array): Files to upload, base64-encoded.
- `git_token` (string): Personal access token for private repositories
- `project` (string, required): Project name (created if it does not exist), e.g. "my-portfolio"
- `repo` (string): Git repository to deploy instead of files: "user/repo" or a full GitHub/GitLab URL
- `source_path` (string): Subdirectory of the repo to deploy, e.g. "dist" or "build"
- `spa_mode` (boolean): Enable single-page-app mode (all routes serve index.html)

### `edge_deploy_app` (~321 tokens)

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.

Input parameters:

- `cdn` (boolean): Put the Edge CDN in front of the VM
- `domain` (string): Domain for the app
- `dry_run` (boolean): Preview the action without executing it. Returns what would happen, including cost estimates. Always dry-run first for anything that costs money.
- `os` (string): Operating system template id (default ubuntu-24.04)
- `project` (string, required): Project name
- `region` (string): Deployment region (default london) — list regions via edge_discover
- `script` (string): Startup script id from the Edge library (e.g. "docker", "nodejs") — preferred over setup_script
- `script_params` (object): Parameters for the chosen library script
- `setup_script` (string): Inline bash script to run on first boot (use script instead when a library script exists)
- `size` (string, required): nano: 1vCPU/1GB, small: 1/2GB, medium: 2/4GB, large: 4/8GB, xlarge: 8/16GB
- `ssh_key` (string): SSH public key string (e.g. "ssh-ed25519 AAAA...") to bake into the VM

### `edge_update_deployment` (~123 tokens)

Update an existing deployment: upload changed files and optionally purge the CDN cache.

Input parameters:

- `changed_only` (boolean): Skip files whose content has not changed (MD5 comparison)
- `dry_run` (boolean): Preview the action without executing it. Returns what would happen, including cost estimates. Always dry-run first for anything that costs money.
- `files` (array, required): Files to upload, base64-encoded.
- `project_id` (string, required): Project id (from edge_list_projects)
- `purge_cdn` (boolean): Purge the CDN cache after upload

### `edge_list_projects` (~24 tokens)

List all projects (groupings of resources) on the connected Edge account.

### `edge_project_health` (~42 tokens)

Comprehensive health check for every resource in a project: status, metrics, and actionable suggestions.

Input parameters:

- `project_id` (string, required): Project id (from edge_list_projects)

### `edge_scale_project` (~106 tokens)

Scale the compute resources in a project up or down. BILLABLE — dry_run first and report the cost change to the user.

Input parameters:

- `dry_run` (boolean): Preview the action without executing it. Returns what would happen, including cost estimates. Always dry-run first for anything that costs money.
- `project_id` (string, required): Project id
- `reason` (string): Why you are scaling (recorded in the audit log)
- `size` (string, required): Target VM size

### `edge_teardown_project` (~124 tokens)

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.

Input parameters:

- `confirm` (boolean): Must be true to actually delete. Without it the call fails with a summary of what would be deleted.
- `dry_run` (boolean): Preview the action without executing it. Returns what would happen, including cost estimates. Always dry-run first for anything that costs money.
- `project_id` (string, required): Project id

### `edge_list_vms` (~26 tokens)

List all virtual machines on the account with status, size, and IPs.

### `edge_get_vm` (~60 tokens)

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.

Input parameters:

- `vm_id` (string, required): VM id (from edge_list_vms)

### `edge_list_buckets` (~17 tokens)

List storage buckets on the account.

### `edge_create_bucket` (~85 tokens)

Create an object storage bucket (S3-compatible). Free tier includes a limited number of buckets.

Input parameters:

- `dry_run` (boolean): Preview the action without executing it. Returns what would happen, including cost estimates. Always dry-run first for anything that costs money.
- `name` (string, required): Bucket name: 3-63 chars, lowercase letters, numbers, hyphens

### `edge_upload_files` (~93 tokens)

Upload files to an existing storage bucket.

Input parameters:

- `bucket` (string, required): Bucket name
- `changed_only` (boolean): Skip files whose content has not changed (MD5 comparison)
- `dry_run` (boolean): Preview the action without executing it. Returns what would happen, including cost estimates. Always dry-run first for anything that costs money.
- `files` (array, required): Files to upload, base64-encoded.

### `edge_list_dns_zones` (~18 tokens)

List DNS zones on the account.

### `edge_create_dns_zone` (~73 tokens)

Create a DNS zone for a domain on Edge authoritative DNS. Free.

Input parameters:

- `domain` (string, required): Domain name, e.g. "example.com"
- `dry_run` (boolean): Preview the action without executing it. Returns what would happen, including cost estimates. Always dry-run first for anything that costs money.

### `edge_add_dns_record` (~145 tokens)

Add a DNS record to a zone.

Input parameters:

- `data` (string, required): Record value, e.g. an IP address or target domain
- `dry_run` (boolean): Preview the action without executing it. Returns what would happen, including cost estimates. Always dry-run first for anything that costs money.
- `name` (string, required): Record name, e.g. "www" or "@" for the root
- `priority` (number): Priority — required for MX records
- `ttl` (number): TTL in seconds (default 300)
- `type` (string, required): Record type
- `zone_id` (string, required): Zone id (from edge_list_dns_zones)

### `edge_list_shield_widgets` (~23 tokens)

List Edge Shield widgets (free, privacy-first CAPTCHA alternative).

### `edge_create_shield_widget` (~149 tokens)

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.

Input parameters:

- `dry_run` (boolean): Preview the action without executing it. Returns what would happen, including cost estimates. Always dry-run first for anything that costs money.
- `hostnames` (array): Hostnames allowed to use this widget, e.g. ["example.com"]. Empty = any hostname.
- `mode` (string): managed: invisible for humans, one-click check for suspicious traffic (default)
- `name` (string, required): Friendly name, e.g. "Contact form"

### `edge_list_assist_sites` (~26 tokens)

List Edge Assist sites (AI answers widget) with usage and index status.

### `edge_create_assist_site` (~165 tokens)

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.

Input parameters:

- `dry_run` (boolean): Preview the action without executing it. Returns what would happen, including cost estimates. Always dry-run first for anything that costs money.
- `hostname` (string, required): Hostname the widget will run on, e.g. "docs.example.com" (origin-enforced)
- `index_url` (string): Public URL of the content index JSON: { "pages": [{ "url", "title", "text" }] }. Can be set later.
- `name` (string, required): Friendly name, e.g. "Docs site"

### `edge_account_status` (~36 tokens)

Check whether the connected account is a self-signed-up guest (explore tier) or fully claimed, and how to unlock it.

### `edge_request_claim` (~74 tokens)

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.

Input parameters:

- `email` (string, required): The human operator's email address

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/network-edge-mcp/edge#diagnostics

## Score history

- 2026-09-20: 76
- 2026-09-19: 76
- 2026-09-18: 75
- 2026-09-17: 75
- 2026-09-16: 74
- 2026-09-15: 74
- 2026-09-14: 73
- 2026-09-13: 73
- 2026-09-12: 73
- 2026-09-11: 72
- 2026-09-10: 72
- 2026-09-09: 71
- 2026-09-08: 71
- 2026-09-07: 70
- 2026-09-06: 70
- 2026-09-05: 69
- 2026-09-04: 69
- 2026-09-03: 68
- 2026-09-02: 68
- 2026-09-01: 67
- 2026-08-31: 67
- 2026-08-30: 66
- 2026-08-29: 66
- 2026-08-28: 66
- 2026-08-27: 65
- 2026-08-26: 65
- 2026-08-25: 64
- 2026-08-24: 63
- 2026-08-23: 63

## Common questions

### What is the Edge Network MCP server?

Edge Network is an MCP server listed in the public MCP registry as network.edge/mcp. Deploy and manage Edge Network cloud: sites, VMs, storage, DNS, Shield, Assist. Agent self-signup. This page covers its hosted endpoint (https://edge.network/mcp).

### Is the Edge Network MCP server safe to use?

Edge Network scores 76 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

### What tools does the Edge Network MCP server expose?

Edge Network exposes 22 tools: edge_discover, edge_deploy_static_site, edge_deploy_app, edge_update_deployment, edge_list_projects, and 17 more. Their descriptions and schemas cost roughly 2,044 tokens of context every time the server is loaded.

### Does the Edge Network MCP server require authentication?

No. We connected to Edge Network without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the Edge Network MCP server still maintained?

Edge Network is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://edge.network/mcp
- Website: https://edge.network/docs/agent/mcp
- Changelog RSS feed: https://verifymcp.io/servers/network-edge-mcp/edge.xml
- Changelog JSON feed: https://verifymcp.io/servers/network-edge-mcp/edge.json
- HTML version of this page: https://verifymcp.io/servers/network-edge-mcp/edge