Edge Network
REMOTE · EDGE.NETWORK
Deploy and manage Edge Network cloud: sites, VMs, storage, DNS, Shield, Assist. Agent self-signup.
Available components
Last scanned (5 hours ago)
Scores higher than 69% of remote servers
Reachable. Last reached 5 Nov 2026.
Category Cloud Infrastructure
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. How we score → Why this is hard to score →
Endpoint Security63
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 28 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability77
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 3294 tokens (~117/item across 28 items; 28 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety75
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- 0 of 5 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. See how to fix → Fail
- An AI judge read all 29 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities40
- Spec-recency check failed: implements MCP spec 2025-03-26; the latest is 2026-07-28. See how to fix → Fail
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 13 Oct 26 0
- Schema quality: 2572 → 3294 ▼ functional
- New tool “edge_delete_dns_record” functional
- New tool “edge_delete_dns_zone” functional
- New tool “edge_delete_vm” functional
- New tool “edge_rename_vm” functional
- New tool “edge_update_dns_record” functional
- New tool “edge_vm_power” functional
- 28 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 22 Sept 26 0
- Stability: 0.97 → pass security
- 26 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 24 Aug 26 0
- Stability: unverified → 0.03 ▲ functional
- 23 Aug 26 0
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 5 Nov 2026 · Probed https://edge.network/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=edge.network | CN=YE1,O=Let's Encrypt,C=US | 28 Sept 2026 | 27 Dec 2026 | ECDSA 256 | ECDSA-SHA384 | 55263af29a7df7bb95a1309a33448ab392c |
| SANs: edge.network, www.edge.network | ||||||
| CN=YE1,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 5ddd70dd31f801c85c186a7a04b80afe |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of edge.network. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| network. | present | 11416, 40414 | 8, 8 | Verified |
| edge.network. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=31536000; includeSubDomains |
| content-security-policy | default-src 'none'; frame-ancestors 'none' |
| x-content-type-options | nosniff |
| x-frame-options | SAMEORIGIN |
| referrer-policy | no-referrer |
| permissions-policy | camera=(), microphone=(), geolocation=() |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://edge.network/mcp | Verified | 200 | |
| http (plaintext) | http://edge.network/mcp | HTTPS enforced | 301 | https://edge.network/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
edge_account_status ~36
Check whether the connected account is a self-signed-up guest (explore tier) or fully claimed, and how to unlock it.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
edge_add_dns_record ~145
Add a DNS record to a zone.
| Name | Type | Req | Description |
|---|---|---|---|
| data | string | yes | 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 | yes | 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 | yes | Record type |
| zone_id | string | yes | Zone id (from edge_list_dns_zones) |
No output schema declared.
No examples provided.
edge_create_assist_site ~165
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | 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 | yes | Friendly name, e.g. "Docs site" |
No output schema declared.
No examples provided.
edge_create_bucket ~85
Create an object storage bucket (S3-compatible). Free tier includes a limited number of buckets.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | Bucket name: 3-63 chars, lowercase letters, numbers, hyphens |
No output schema declared.
No examples provided.
edge_create_dns_zone ~73
Create a DNS zone for a domain on Edge authoritative DNS. Free.
| Name | Type | Req | Description |
|---|---|---|---|
| domain | string | yes | 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. |
No output schema declared.
No examples provided.
edge_create_shield_widget ~149
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | Friendly name, e.g. "Contact form" |
No output schema declared.
No examples provided.
edge_delete_dns_record ~83
Delete one DNS record from a zone.
| Name | Type | Req | Description |
|---|---|---|---|
| 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. |
| record_id | string | yes | Record id (from the zone detail) |
| zone_id | string | yes | Zone id (from edge_list_dns_zones) |
No output schema declared.
No examples provided.
edge_delete_dns_zone ~120
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.
| Name | Type | Req | Description |
|---|---|---|---|
| confirm | boolean | – | Must be true to actually delete. |
| 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. |
| zone_id | string | yes | Zone id (from edge_list_dns_zones) |
No output schema declared.
No examples provided.
edge_delete_vm ~125
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.
| Name | Type | Req | Description |
|---|---|---|---|
| confirm | boolean | – | Must be true to actually delete. |
| 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. |
| vm_id | string | yes | VM id (from edge_list_vms) |
No output schema declared.
No examples provided.
edge_deploy_app ~321
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | 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 | yes | 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 |
No output schema declared.
No examples provided.
edge_deploy_static_site ~271
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | 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) |
No output schema declared.
No examples provided.
edge_discover ~43
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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
edge_get_vm ~60
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.
| Name | Type | Req | Description |
|---|---|---|---|
| vm_id | string | yes | VM id (from edge_list_vms) |
No output schema declared.
No examples provided.
edge_list_assist_sites ~26
List Edge Assist sites (AI answers widget) with usage and index status.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
edge_list_buckets ~17
List storage buckets on the account.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
edge_list_dns_zones ~18
List DNS zones on the account.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
edge_list_projects ~24
List all projects (groupings of resources) on the connected Edge account.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
edge_list_shield_widgets ~23
List Edge Shield widgets (free, privacy-first CAPTCHA alternative).
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
edge_list_vms ~26
List all virtual machines on the account with status, size, and IPs.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
edge_project_health ~42
Comprehensive health check for every resource in a project: status, metrics, and actionable suggestions.
| Name | Type | Req | Description |
|---|---|---|---|
| project_id | string | yes | Project id (from edge_list_projects) |
No output schema declared.
No examples provided.
edge_rename_vm ~83
Change the display name of a VM (does not change the guest hostname).
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | New name |
| vm_id | string | yes | VM id (from edge_list_vms) |
No output schema declared.
No examples provided.
edge_request_claim ~74
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.
| Name | Type | Req | Description |
|---|---|---|---|
| string | yes | The human operator's email address |
No output schema declared.
No examples provided.
edge_scale_project ~106
Scale the compute resources in a project up or down. BILLABLE — dry_run first and report the cost change to the user.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | Project id |
| reason | string | – | Why you are scaling (recorded in the audit log) |
| size | string | yes | Target VM size |
No output schema declared.
No examples provided.
edge_teardown_project ~124
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | Project id |
No output schema declared.
No examples provided.
edge_update_deployment ~123
Update an existing deployment: upload changed files and optionally purge the CDN cache.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | Files to upload, base64-encoded. |
| project_id | string | yes | Project id (from edge_list_projects) |
| purge_cdn | boolean | – | Purge the CDN cache after upload |
No output schema declared.
No examples provided.
edge_update_dns_record ~194
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}).
| Name | Type | Req | Description |
|---|---|---|---|
| data | string | – | New value, e.g. the new IP address |
| 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 | – | New record name |
| priority | number | – | New priority (MX only) |
| record_id | string | yes | Record id (from the zone detail) |
| ttl | number | – | New TTL in seconds |
| type | string | – | New record type |
| zone_id | string | yes | Zone id (from edge_list_dns_zones) |
No output schema declared.
No examples provided.
edge_upload_files ~93
Upload files to an existing storage bucket.
| Name | Type | Req | Description |
|---|---|---|---|
| bucket | string | yes | 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 | yes | Files to upload, base64-encoded. |
No output schema declared.
No examples provided.
edge_vm_power ~117
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.
| Name | Type | Req | Description |
|---|---|---|---|
| action | string | yes | Power action. Use "reset" only when "restart" does not respond. |
| 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. |
| vm_id | string | yes | VM id (from edge_list_vms) |
No output schema declared.
No examples provided.
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.
remote · edge.network
claude mcp add --transport http network-edge-mcp 'https://edge.network/mcp'
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 77 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 28 tools: edge_discover, edge_deploy_static_site, edge_deploy_app, edge_update_deployment, edge_list_projects, and 23 more. Their descriptions and schemas cost roughly 2,766 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 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.