# Edgegap (remote · mcp.edgegap.dev)

Deploy and operate multiplayer game servers on Edgegap's global edge network.

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

> **Recent critical change**: Authorization (2026-09-16). See the changelog below before you install this server.

## Components

- remote · `mcp.edgegap.dev`: 65/100 (this document), [markdown](https://verifymcp.io/servers/dev-edgegap-mcp/mcp.md), [page](https://verifymcp.io/servers/dev-edgegap-mcp/mcp)
- npm · `@edgegap/mcp`: 75/100, [markdown](https://verifymcp.io/servers/dev-edgegap-mcp/edgegap-mcp.md), [page](https://verifymcp.io/servers/dev-edgegap-mcp/edgegap-mcp)

## Channel facts

- Endpoint: `https://mcp.edgegap.dev/mcp`
- Transports: `streamable-http`
- Auth: `required`
- Version: `0.1.4`

## 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-25.

- **Endpoint Security**: 46/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation check failed: no authorisation is required to call this server, and it exposes a tool marked destructive (edgegap_stop_deployment).
  - HTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - 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**: 79/100
  - AI-judged instruction clarity (excellent).
  - 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.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 30/100
  - Stability observed for 9 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 99/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 97% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.
  - An AI judge read all 10 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a current MCP spec version (2026-07-28).

## Install

### 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.

### Claude

```bash
claude mcp add --transport http dev-edgegap-mcp 'https://mcp.edgegap.dev/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "dev-edgegap-mcp": {
      "url": "https://mcp.edgegap.dev/mcp"
    }
  }
}
```

### VS Code

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

### Codex

```toml
[mcp_servers.dev-edgegap-mcp]
url = "https://mcp.edgegap.dev/mcp"
```

### opencode

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

### OpenClaw

```bash
openclaw mcp add dev-edgegap-mcp --url 'https://mcp.edgegap.dev/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  dev-edgegap-mcp:
    url: "https://mcp.edgegap.dev/mcp"
```

### Netclaw

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

### Vellum

```bash
assistant mcp add dev-edgegap-mcp -t streamable-http -u 'https://mcp.edgegap.dev/mcp'
```

### Other

```json
{
  "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.

## 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-25 (score 65, +1)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-09-23 (score 64, +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.

### 2026-09-21 (score 63, +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.

### 2026-09-18 (score 62, +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.

### 2026-09-17 (score 61, 0)

- [functional improvement] Stability: unverified → 0.03

### 2026-09-16 (score 61, +33)

- [critical] Authorization: Authorisation check failed: no authorisation is required to call this server, and it exposes a tool marked destructive (edgegap_stop_deployment).
- [security improvement] Transport: unverified → pass
- [security improvement] Injection markers: unverified → pass
- [security] First check of Judged manipulation: pass
- [functional improvement] MCP protocol: unverified → pass
- [functional improvement] 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

### 2026-09-11 (score 28)

First indexed and scored.

## MCP tools (10)

### `edgegap_list_apps` (~71 tokens)

List Edgegap applications

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.

Input parameters:

- `limit` (integer): Results per page. Default 50.
- `page` (integer)

### `edgegap_create_app` (~87 tokens)

Create an Edgegap application

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.

Input parameters:

- `is_active` (boolean): Whether deployments are allowed. Default true.
- `name` (string, required): Application name, 3-64 chars. Usually the game or project name.

### `edgegap_list_app_versions` (~67 tokens)

List versions of an application

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.

Input parameters:

- `application` (string, required): Application name, as returned by edgegap_list_apps.

### `edgegap_create_app_version` (~338 tokens)

Create an application version

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.

Input parameters:

- `application` (string, required): Existing application name.
- `cpu_units` (integer, required): vCPU units. 1024 = 1 vCPU.
- `docker_image` (string, required): Namespaced image, e.g. "mystudio/game-server".
- `docker_repository` (string, required): Registry host, e.g. "docker.io" or "registry.edgegap.com".
- `docker_tag` (string, required): 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, required): Memory in MB. At most 2x cpu_units.
- `name` (string, required): Version identifier, typically a build ID or timestamp.
- `ports` (array, required): 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.

### `edgegap_deploy` (~169 tokens)

Deploy a game server

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.

Input parameters:

- `application` (string, required): 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, required): Where the players are. Exactly one of these two is required.
- `version` (string, required): Version name within the application.

### `edgegap_get_deployment` (~75 tokens)

Get deployment status

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.

Input parameters:

- `request_id` (string, required): The request_id returned by edgegap_deploy.

### `edgegap_wait_for_deployment` (~107 tokens)

Wait for a deployment to become ready

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.

Input parameters:

- `request_id` (string, required): The request_id returned by edgegap_deploy.
- `timeout_seconds` (integer): How long to wait before giving up. Default 180.

### `edgegap_list_deployments` (~73 tokens)

List running deployments

List active deployments, optionally filtered. Use this to find deployments left running from earlier sessions before starting new ones — orphaned servers cost money.

Input parameters:

- `filter` (string): Edgegap filter expression, e.g. by tag. Omit for all deployments.
- `limit` (integer): Default 50.

### `edgegap_stop_deployment` (~69 tokens)

Stop a deployment

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.

Input parameters:

- `request_id` (string, required): The request_id of the deployment to stop.

### `edgegap_get_deployment_logs` (~105 tokens)

Get container logs for a deployment

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.

Input parameters:

- `max_characters` (integer): Truncate logs to this length, keeping the tail. Default 8000.
- `request_id` (string, required): The request_id of the deployment.

## Diagnostics

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

## Score history

- 2026-09-25: 65
- 2026-09-24: 64
- 2026-09-23: 64
- 2026-09-22: 63
- 2026-09-21: 63
- 2026-09-20: 62
- 2026-09-19: 62
- 2026-09-18: 62
- 2026-09-17: 61
- 2026-09-16: 61
- 2026-09-15: 28
- 2026-09-14: 28
- 2026-09-13: 28
- 2026-09-12: 28
- 2026-09-11: 28

## Common questions

### 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.

## Links

- Remote endpoint: https://mcp.edgegap.dev/mcp
- Authorisation metadata: https://mcp.edgegap.dev/.well-known/oauth-protected-resource/mcp
- Repository: https://github.com/edgegap/edgegap-mcp
- Website: https://edgegap.com/
- Changelog RSS feed: https://verifymcp.io/servers/dev-edgegap-mcp/mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/dev-edgegap-mcp/mcp.json
- HTML version of this page: https://verifymcp.io/servers/dev-edgegap-mcp/mcp