Edge MCP server
28 tools · Last check that passed 27 Oct 2026, 01:50 UTC
Edge Network's own remote MCP server gives an agent Edge's cloud for the account its access code belongs to: static site deploys, virtual machines, S3-compatible storage, DNS zones, Shield bot protection and Assist AI answer sites. Once a day, Stackduke connects to it the way any MCP client would, with no account and no sign-in, and lists its tools. It never runs them.
All 28 tools
| Tool | Counted as |
|---|---|
edge_delete_dns_record | Deletes |
edge_delete_dns_zone | Deletes |
edge_delete_vm | Deletes |
edge_teardown_project | Deletes |
edge_update_deployment | Deletes |
edge_vm_power | Deletes |
edge_add_dns_record | Changes things |
edge_create_assist_site | Changes things |
edge_create_bucket | Changes things |
edge_create_dns_zone | Changes things |
edge_create_shield_widget | Changes things |
edge_deploy_app | Changes things |
edge_deploy_static_site | Changes things |
edge_rename_vm | Changes things |
edge_scale_project | Changes things |
edge_update_dns_record | Changes things |
edge_upload_files | Changes things |
edge_account_status | Use not clear |
edge_project_health | Use not clear |
edge_request_claim | Use not clear |
edge_discover | Said to only read |
edge_get_vm | Said to only read |
edge_list_assist_sites | Said to only read |
edge_list_buckets | Said to only read |
edge_list_dns_zones | Said to only read |
edge_list_projects | Said to only read |
edge_list_shield_widgets | Said to only read |
edge_list_vms | Said to only read |
The tools the server listed at the last check that passed, at its default address and settings, with no sign-in; an account that signs in, or other settings, may see other tools. What a tool is counted as doing is Stackduke's cautious reading of the server's labels, the tool's name and its description: where they disagree it takes whichever says the tool can do most, so it overcounts on purpose. It does not say the server is safe, and it does not list what a tool cannot do. Descriptions are not shown, because they are written for models and may try to steer them.
Recent checks
11 of the last 11 checks passed
A check passes when the server lists its tools. Checked at https://edge.network/mcp.
Recent changes
No change seen across the last 11 checks that passed.
From the scan of 27 Oct 2026, 01:52 UTC. "Changed" and "Can do more" count changes from the last 30 days; older ones stay listed here. A change made and undone between two checks is not seen. Every check is in the scanner's public data.
Know when Edge's tools change.
One email when Edge's official MCP server adds, removes or changes tools, with what changed. Nothing else.
What to watch for
- Its tools deploy sites and apps, scale compute, and tear down a whole project with every VM, bucket, CDN deployment and DNS zone in it. Edge's MCP tool reference
- Edge marks some tools as billable, such as edge_deploy_app and edge_scale_project, and says they spend real money. Edge's MCP tool reference
- An agent can sign itself up for a free explore-tier account, and edge_request_claim emails a person a link to claim it, which unlocks billable resources. Edge's MCP server documentation
How to limit it
With Edge's own settings, as its documentation describes them. Stackduke has not tested them.
- Give each agent its own access code with only the products and permissions it needs, as Edge advises. Edge's Delete permission is the one that allows deleting resources and tearing down projects, so we recommend leaving it off unless the agent must remove things. Edge's agent access code documentation
- Set a hard budget cap on the code. Edge says a hard cap blocks the agent from creating new resources once the limit is reached. Edge's agent access code documentation
- Have the agent run billable tools with dry_run first, which Edge says previews the action and its cost without executing it. Edge's MCP tool reference
What Stackduke is designed to do
Stackduke is designed to sit between your agents and their MCP servers: to check each tool call against your rules before it runs, hold the risky ones for a person to approve, and keep a record of what was decided.
It does not yet forward or block tool calls for customers. Today it reads what this server offers and publishes what changes.