Edgegap
REMOTE · MCP.EDGEGAP.DEV · 2 COMPONENTS · SCANNED SEP 25
Deploy and operate multiplayer game servers on Edgegap's global edge network.
Available components
Recent critical change
Authorization (16 Sept 2026). See the changelog before you install this server.
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 Security46
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation check failed: no authorisation is required to call this server, and it exposes a tool marked destructive (edgegap_stop_deployment). See how to fix → View diagnostics → Fail
- HTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement. View diagnostics → Unverified
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- 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 Usability79
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 1161 tokens (~116/item across 10 items; 10 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 Management30
- Stability observed for 9 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage99
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 97% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
- An AI judge read all 10 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
How do I install the Edgegap MCP server?
Edgegap is a hosted endpoint at https://mcp.edgegap.dev/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 · mcp.edgegap.dev
claude mcp add --transport http dev-edgegap-mcp 'https://mcp.edgegap.dev/mcp'
{
"mcpServers": {
"dev-edgegap-mcp": {
"url": "https://mcp.edgegap.dev/mcp"
}
}
} {
"servers": {
"dev-edgegap-mcp": {
"type": "http",
"url": "https://mcp.edgegap.dev/mcp"
}
}
} [mcp_servers.dev-edgegap-mcp] url = "https://mcp.edgegap.dev/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"dev-edgegap-mcp": {
"type": "remote",
"url": "https://mcp.edgegap.dev/mcp",
"enabled": true
}
}
} openclaw mcp add dev-edgegap-mcp --url 'https://mcp.edgegap.dev/mcp' --transport streamable-http
mcp_servers:
dev-edgegap-mcp:
url: "https://mcp.edgegap.dev/mcp" {
"McpServers": {
"dev-edgegap-mcp": {
"Transport": "http",
"Url": "https://mcp.edgegap.dev/mcp"
}
}
} assistant mcp add dev-edgegap-mcp -t streamable-http -u 'https://mcp.edgegap.dev/mcp'
{
"mcpServers": {
"dev-edgegap-mcp": {
"type": "http",
"url": "https://mcp.edgegap.dev/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
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.
- 25 Sept 26 +1
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 23 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.
- 21 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.
- 18 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.
- 17 Sept 26 0
- Stability: unverified → 0.03 ▲ functional
- 16 Sept 26 +33
- Authorization: Authorisation check failed: no authorisation is required to call this server, and it exposes a tool marked destructive (edgegap_stop_deployment). critical
- Transport: unverified → pass ▲ security
- Injection markers: unverified → pass ▲ security
- First check of Judged manipulation: pass security
- MCP protocol: unverified → pass ▲ functional
- Tool coverage: unverified → 100 ▲ functional
- First check of Destructive annotations: 100 functional
- First check of Schema quality: excellent functional
- First check of Schema quality: fail functional
- First check of Schema quality: fail functional
- First check of Tool coverage: 97 functional
- 11 Sept 26 28
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 25 Sept 2026 · Probed https://mcp.edgegap.dev/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=edgegap.dev | CN=WE1,O=Google Trust Services,C=US | 11 Sept 2026 | 10 Dec 2026 | ECDSA 256 | ECDSA-SHA256 | 24b7cfb2a32fa05a13af6fa2d718f852 |
| SANs: edgegap.dev, mcp.edgegap.dev, *.mcp.edgegap.dev | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of mcp.edgegap.dev. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| dev. | present | 60074 | 8 | Verified |
| edgegap.dev. | 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 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://mcp.edgegap.dev/mcp | Verified | 200 | |
| http (plaintext) | http://mcp.edgegap.dev/mcp | Inconclusive | 405 |
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 →
edgegap_create_app Create an Edgegap application ~87
Create a new application to hold game server versions. Only call this after edgegap_list_apps confirms no suitable application exists. Creating an application does not deploy anything — follow with edgegap_create_app_version.
| Name | Type | Req | Description |
|---|---|---|---|
| is_active | boolean | – | Whether deployments are allowed. Default true. |
| name | string | yes | Application name, 3-64 chars. Usually the game or project name. |
No output schema declared.
No examples provided.
edgegap_create_app_version Create an application version ~338
Register a container image as a deployable version of an application. The image must already be pushed to a registry that Edgegap can pull from. Resource units: 1024 cpu units = 1 vCPU; memory_mb must be at least 256 and at most double the cpu units. Set verify_image true on the first version so a bad image fails here rather than at deploy time. Avoid the "latest" docker tag — use a build ID so deployments are reproducible.
| Name | Type | Req | Description |
|---|---|---|---|
| application | string | yes | Existing application name. |
| cpu_units | integer | yes | vCPU units. 1024 = 1 vCPU. |
| docker_image | string | yes | Namespaced image, e.g. "mystudio/game-server". |
| docker_repository | string | yes | Registry host, e.g. "docker.io" or "registry.edgegap.com". |
| docker_tag | string | yes | Image tag. Use a build ID, not "latest". |
| env | array | – | Environment variables injected into the container. |
| max_duration_minutes | integer | – | Auto-stop after this many minutes. Keeps test deployments from running up cost. |
| memory_mb | integer | yes | Memory in MB. At most 2x cpu_units. |
| name | string | yes | Version identifier, typically a build ID or timestamp. |
| ports | array | yes | Ports to expose. At least one is required for players to connect. |
| registry_token | string | – | Registry password or token. |
| registry_username | string | – | Registry username, for private images. |
| verify_image | boolean | – | Verify Edgegap can pull the image before accepting the version. |
No output schema declared.
No examples provided.
edgegap_deploy Deploy a game server ~169
Start one containerized instance of an application version, placed near the players you specify. Returns immediately with a request_id; the server is still starting and has no connection details yet. Follow this call with edgegap_wait_for_deployment to get the address players connect to. Always stop deployments you started for testing.
| Name | Type | Req | Description |
|---|---|---|---|
| application | string | yes | Application name. |
| cpu_units | integer | – | Override the version CPU. |
| env | array | – | Environment variables for this deployment only. |
| memory_mb | integer | – | Override the version memory. |
| tags | array | – | Tags for filtering later, e.g. ["agent-test"]. Recommended. |
| users | object | yes | Where the players are. Exactly one of these two is required. |
| version | string | yes | Version name within the application. |
No output schema declared.
No examples provided.
edgegap_get_deployment Get deployment status ~75
Read the current status of one deployment, including connection address and ports once it is ready. For a deployment you just created, prefer edgegap_wait_for_deployment — it polls for you instead of making you call this in a loop.
| Name | Type | Req | Description |
|---|---|---|---|
| request_id | string | yes | The request_id returned by edgegap_deploy. |
No output schema declared.
No examples provided.
edgegap_get_deployment_logs Get container logs for a deployment ~105
Retrieve stdout/stderr and crash output for a deployment. Call this whenever a deployment errors or a server exits unexpectedly — the crash exit code usually identifies the problem faster than redeploying does. Logs for stopped deployments are only retained if Endpoint Storage was configured on the version beforehand.
| Name | Type | Req | Description |
|---|---|---|---|
| max_characters | integer | – | Truncate logs to this length, keeping the tail. Default 8000. |
| request_id | string | yes | The request_id of the deployment. |
No output schema declared.
No examples provided.
edgegap_list_app_versions List versions of an application ~67
List the versions under an application, with their container image and resource settings. Use this to find the version name to deploy, or to copy settings from a working version when creating a new one.
| Name | Type | Req | Description |
|---|---|---|---|
| application | string | yes | Application name, as returned by edgegap_list_apps. |
No output schema declared.
No examples provided.
edgegap_list_apps List Edgegap applications ~71
List the applications in the Edgegap organization. Start here before creating or deploying anything, so you reuse an existing application instead of making a duplicate. An "application" groups versions of one game server.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Results per page. Default 50. |
| page | integer | – | – |
No output schema declared.
No examples provided.
edgegap_list_deployments List running deployments ~73
List active deployments, optionally filtered. Use this to find deployments left running from earlier sessions before starting new ones — orphaned servers cost money.
| Name | Type | Req | Description |
|---|---|---|---|
| filter | string | – | Edgegap filter expression, e.g. by tag. Omit for all deployments. |
| limit | integer | – | Default 50. |
No output schema declared.
No examples provided.
edgegap_stop_deployment Stop a deployment ~69
Gracefully stop one deployment by request_id, sending SIGTERM to the container. Stop every deployment you started for testing before ending your task. This tool stops exactly one deployment; bulk stop is deliberately not exposed.
| Name | Type | Req | Description |
|---|---|---|---|
| request_id | string | yes | The request_id of the deployment to stop. |
No output schema declared.
No examples provided.
edgegap_wait_for_deployment Wait for a deployment to become ready ~107
Poll a deployment until it is ready, errors, or the timeout expires, then return the connection details. This is the tool to call right after edgegap_deploy. Do not build your own polling loop — this handles backoff and reports the container error detail if the server fails to start.
| Name | Type | Req | Description |
|---|---|---|---|
| request_id | string | yes | The request_id returned by edgegap_deploy. |
| timeout_seconds | integer | – | How long to wait before giving up. Default 180. |
No output schema declared.
No examples provided.
What is the Edgegap MCP server?
Edgegap is an MCP server listed in the public MCP registry as dev.edgegap/mcp. Deploy and operate multiplayer game servers on Edgegap's global edge network. This page covers its hosted endpoint (https://mcp.edgegap.dev/mcp).
Is the Edgegap MCP server safe to use?
Edgegap scores 65 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 Edgegap MCP server expose?
Edgegap exposes 10 tools: edgegap_list_apps, edgegap_create_app, edgegap_list_app_versions, edgegap_create_app_version, edgegap_deploy, and 5 more. Their descriptions and schemas cost roughly 1,161 tokens of context every time the server is loaded.
Does the Edgegap MCP server require authentication?
No. We connected to Edgegap without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Edgegap MCP server still maintained?
Edgegap is still listed as active in the MCP registry. We last reached this channel on 25 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.