Edgegap
NPM · @EDGEGAP/MCP · 2 COMPONENTS · SCANNED SEP 25
Deploy and operate multiplayer game servers on Edgegap's global edge network.
Available components
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security99
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- 34 of 169 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (Apache-2.0).Pass
- Actively maintained (last published 8 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability75
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 1393 tokens (~139/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 Management37
- Stability observed for 11 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 11 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
How do I install the Edgegap MCP server?
Edgegap runs locally as an npm package, launched with npx -y @edgegap/mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · @edgegap/mcp
claude mcp add dev-edgegap-mcp -- npx -y @edgegap/mcp
{
"mcpServers": {
"dev-edgegap-mcp": {
"command": "npx",
"args": [
"-y",
"@edgegap/mcp"
]
}
}
} {
"servers": {
"dev-edgegap-mcp": {
"command": "npx",
"args": [
"-y",
"@edgegap/mcp"
]
}
}
} codex mcp add dev-edgegap-mcp -- npx -y @edgegap/mcp
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"dev-edgegap-mcp": {
"type": "local",
"command": [
"npx",
"-y",
"@edgegap/mcp"
],
"enabled": true
}
}
} openclaw mcp add dev-edgegap-mcp --command npx --arg -y --arg @edgegap/mcp
mcp_servers:
dev-edgegap-mcp:
command: "npx"
args: ["-y", "@edgegap/mcp"] {
"McpServers": {
"dev-edgegap-mcp": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"@edgegap/mcp"
]
}
}
} assistant mcp add dev-edgegap-mcp -t stdio -c npx -a -y @edgegap/mcp
{
"mcpServers": {
"dev-edgegap-mcp": {
"command": "npx",
"args": [
"-y",
"@edgegap/mcp"
]
}
}
} 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 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 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 30 to 33. That category is still filling its 30-day observation window: 9 days of observed history at the previous scan, 10 at this one. The score rises as the window fills, whether or not the server changes.
- 22 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.
- 21 Sept 26 0
- Security disclosure: unverified → fail ▼ functional
- 20 Sept 26 0
- Security disclosure: fail → unverified ▼ functional
- 19 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.
- 17 Sept 26 +33
- Injection markers: unverified → pass ▲ security
- Stability: unverified → 0.10 ▲ functional
- Tool coverage: unverified → 100 ▲ functional
- MCP protocol: unverified → pass ▲ functional
- Destructive annotations: All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation. functional
- 16 Sept 26 −30
- Tool safety: pass → unverified ▼ security
- Stability: Stability not yet verified: we do not have a sandbox capture of the MCP schema this version of the package serves yet. security
- Tool coverage: 100 → unverified ▼ functional
- Capabilities: pass → unverified ▼ functional
- First check of Schema quality: unverified functional
- Package version: 0.1.1 → 0.1.4 functional
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 · Analysed npm/@edgegap/mcp@0.1.4
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Background: How many MCP packages publish verified provenance →
Dependencies 169 packages
| Packages resolved | 169 |
|---|---|
| Stale | 34 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
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 npm package (@edgegap/mcp).
Is the Edgegap MCP server safe to use?
Edgegap scores 75 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 25 September 2026. It declares no install or post-install scripts. 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.
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.
What licence is the Edgegap MCP server under?
Edgegap declares the Apache-2.0 licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.