# Glitchless (npm · glitchless-mcp)

Game observability for coding agents: stutter, crashes, where players quit, and playtest bots.

- Trust score: 68/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-10-23

## Components

- npm · `glitchless-mcp`: 68/100 (this document), [markdown](https://verifymcp.io/servers/glitchless-gg-glitchless/glitchless-mcp.md), [page](https://verifymcp.io/servers/glitchless-gg-glitchless/glitchless-mcp)

## Channel facts

- Registry: `npm`
- Package: `glitchless-mcp`
- Version: `0.2.0`
- Transport: `stdio`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-10-23.

- **Supply Chain Security**: 98/100
  - No malware found by supply-chain analysis.
  - No known CVEs affecting this package version or its production dependencies.
  - No install/post-install scripts declared.
  - 30 of 93 dependencies flagged as unhealthy.
- **Provenance & Transparency**: 45/100
  - Source repository is publicly reachable at the declared URL.
  - Provenance check failed: no build-provenance attestation is published.
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 1 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 62/100
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 2718 tokens (~209/item across 13 items; 13 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 7/100
  - Stability observed for 2 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).
  - 98% 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.
  - We read all 13 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 14 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### How do I install the Glitchless MCP server?

Glitchless runs locally as an npm package, launched with npx -y glitchless-mcp. 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 glitchless-gg-glitchless -- npx -y glitchless-mcp
```

### Cursor

```json
{
  "mcpServers": {
    "glitchless-gg-glitchless": {
      "command": "npx",
      "args": [
        "-y",
        "glitchless-mcp"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "glitchless-gg-glitchless": {
      "command": "npx",
      "args": [
        "-y",
        "glitchless-mcp"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add glitchless-gg-glitchless -- npx -y glitchless-mcp
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "glitchless-gg-glitchless": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "glitchless-mcp"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add glitchless-gg-glitchless --command npx --arg -y --arg glitchless-mcp
```

### Hermes

```yaml
mcp_servers:
  glitchless-gg-glitchless:
    command: "npx"
    args: ["-y", "glitchless-mcp"]
```

### Netclaw

```json
{
  "McpServers": {
    "glitchless-gg-glitchless": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "glitchless-mcp"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add glitchless-gg-glitchless -t stdio -c npx -a -y glitchless-mcp
```

### Other

```json
{
  "mcpServers": {
    "glitchless-gg-glitchless": {
      "command": "npx",
      "args": [
        "-y",
        "glitchless-mcp"
      ]
    }
  }
}
```

## 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-10-23 (score 68, +26)

- [security improvement] Malware scan: unverified → pass
- [security improvement] Known CVEs: unverified → pass
- [functional improvement] Dependency health: unverified → 0.86

### 2026-10-22 (score 42, −12)

- [security regression] Known CVEs: pass → unverified
- [security regression] Tool safety: pass → unverified
- [security improvement] Malware scan: unverified → pass
- [security] Stability: Stability not yet verified: we do not have a sandbox capture of the MCP schema this version of the package serves yet.
- [functional regression] Schema quality: 144 → 209
- [functional regression] Dependency health: 0.85 → unverified
- [functional regression] Capabilities: pass → unverified
- [functional regression] Tool coverage: 100 → unverified
- [functional improvement] Stability: unverified → 0.03
- [functional] First check of Schema quality: unverified
- [functional] Package version: 0.1.1 → 0.2.0
- [functional] Package version: 0.1.1 → 0.1.2

### 2026-10-21 (score 54)

First indexed and scored.

## MCP tools (13)

### `glitchless_list_games` (~31 tokens)

List the games reporting to Glitchless, with their versions, environments and when they were last seen.

### `glitchless_triage` (~177 tokens)

Ranked findings for a game: performance spikes per level (with the gauges and events they correlate with), memory leaks, top errors, difficulty spikes / rage-quit hotspots and version regressions — ranked by severity and player impact, each with evidence and a suggested fix. Start here when asked 'what's wrong with my game?'.

Input parameters:

- `hours` (number): Look-back window in hours (default 24). Up to the plan's retention on Glitchless Cloud: 336 (14 days) on Free, 2160 (90 days) on Indie, 9600 (400 days) on Studio. Past 744 (31 days) answers are by da…
- `service` (string): Game service name (defaults to the most recently active game)
- `version` (string): Only include sessions from this game version

### `glitchless_overview` (~156 tokens)

Headline KPIs for a game: sessions, players, crash-free and error-free sessions, frame-time p50/p95/p99 vs budget, hitches per minute, rage quits, top errors and the level funnel.

Input parameters:

- `hours` (number): Look-back window in hours (default 24). Up to the plan's retention on Glitchless Cloud: 336 (14 days) on Free, 2160 (90 days) on Indie, 9600 (400 days) on Studio. Past 744 (31 days) answers are by da…
- `service` (string): Game service name (defaults to the most recently active game)
- `version` (string): Only include sessions from this game version

### `glitchless_performance` (~219 tokens)

Frame-time breakdown for a game: global percentiles vs the frame budget, per-level p50/p95/p99 with draw calls / triangles / geometry counts / game-context gauges, hitch causes (script, shader compile, GC, asset load), what is on screen during hitches, which events precede hitches, per GPU tier / browser / version, memory growth per level load and the slowest recent hitches with script attribution.

Input parameters:

- `hours` (number): Look-back window in hours (default 24). Up to the plan's retention on Glitchless Cloud: 336 (14 days) on Free, 2160 (90 days) on Indie, 9600 (400 days) on Studio. Past 744 (31 days) answers are by da…
- `level` (string): Focus on one level id, e.g. "level-2"
- `service` (string): Game service name (defaults to the most recently active game)
- `version` (string): Only include sessions from this game version

### `glitchless_get_error` (~182 tokens)

Error Tracking for a game. Without a fingerprint: the list of error issues ranked by sessions affected. With a fingerprint: the full issue — message, location, stack trace, affected levels/versions, occurrence counts and breadcrumbs (the game events right before it fired).

Input parameters:

- `fingerprint` (string): Issue fingerprint from the list or from glitchless_triage
- `hours` (number): Look-back window in hours (default 24). Up to the plan's retention on Glitchless Cloud: 336 (14 days) on Free, 2160 (90 days) on Indie, 9600 (400 days) on Studio. Past 744 (31 days) answers are by da…
- `service` (string): Game service name (defaults to the most recently active game)
- `version` (string): Only include sessions from this game version

### `glitchless_player_funnel` (~158 tokens)

Player experience per level: sessions that started vs completed each level, attempts, deaths per session and their causes, average clear time, rage quits (quit ≤20s after dying), session length distribution and recent rage quits with positions.

Input parameters:

- `hours` (number): Look-back window in hours (default 24). Up to the plan's retention on Glitchless Cloud: 336 (14 days) on Free, 2160 (90 days) on Indie, 9600 (400 days) on Studio. Past 744 (31 days) answers are by da…
- `service` (string): Game service name (defaults to the most recently active game)
- `version` (string): Only include sessions from this game version

### `glitchless_events` (~249 tokens)

The game's own metrics, from the custom events it sends with track(): each event's count in the window, the sessions and players that sent it, and how its attribute values break down (for example plays by mode, paywall views by placement, purchases started vs done). Give `funnel` to count the sessions that went from one event to the next, in that order.

Input parameters:

- `funnel` (string): Steps in order, comma-separated: "open,paywall,buy". A step can require a value: "buy=done" (any attribute) or "buy:step=done"
- `hours` (number): Look-back window in hours (default 24). Up to the plan's retention on Glitchless Cloud: 336 (14 days) on Free, 2160 (90 days) on Indie, 9600 (400 days) on Studio. Past 744 (31 days) answers are by da…
- `name` (string): Only this event, e.g. "paywall"
- `service` (string): Game service name (defaults to the most recently active game)
- `version` (string): Only include sessions from this game version

### `glitchless_dashboard` (~240 tokens)

The game's dashboard: its pages in order, each a board (panels in the game's own terms) or a built-in view (events, performance, errors, players, heatmaps, sessions, versions, live), and one board's panels with their numbers for the window. `page` picks the board (default: the first). `source` says whether the dashboard was saved (by an agent or a person) or made automatically from what the game sends; `spec` is what to edit and send back to glitchless_set_dashboard.

Input parameters:

- `hours` (number): Look-back window in hours (default 24). Up to the plan's retention on Glitchless Cloud: 336 (14 days) on Free, 2160 (90 days) on Indie, 9600 (400 days) on Studio. Past 744 (31 days) answers are by da…
- `page` (string): Id of the board page to evaluate (default: the first board)
- `service` (string): Game service name (defaults to the most recently active game)
- `version` (string): Only include sessions from this game version

### `glitchless_set_dashboard` (~271 tokens)

Save the game's dashboard: its pages, in the order the sidebar shows them. Each page is a board of panels in the game's own words, or a built-in view (events, performance, errors, players, heatmaps, sessions, versions, live) the game keeps, renames or drops. Design it for this game, not for a genre it isn't: a puzzle game cares about solve time and hints, a mobile game about opens, modes, the paywall and purchases, a platformer about deaths per level. The first page opens first. Use the events the game sends (glitchless_events lists them, with their attributes); on a board, stats first, then the game's own events and funnels, then levels, frame_time and errors. Leave out what the game has no data for (no Heatmaps page for a game without positions). Send every page: read the current ones with glitchless_dashboard (its spec), change them, send them all back. Pass reset: true to go back to the automatic dashboard. Needs a secret key with the dashboard scope.

Input parameters:

- `pages` (array)
- `reset` (boolean): Delete the saved dashboard and go back to the automatic one
- `service` (string): Game service name (defaults to the most recently active game)

### `glitchless_death_hotspots` (~188 tokens)

Where players die on a level: clustered death positions in world coordinates (x range, share of the level’s deaths, top cause, rage quits at that spot), plus the level bounds and completion stats. Use it to find difficulty spikes, then look up the level data around those coordinates.

Input parameters:

- `hours` (number): Look-back window in hours (default 24). Up to the plan's retention on Glitchless Cloud: 336 (14 days) on Free, 2160 (90 days) on Indie, 9600 (400 days) on Studio. Past 744 (31 days) answers are by da…
- `level` (string, required): Level id, e.g. "level-3"
- `service` (string): Game service name (defaults to the most recently active game)
- `version` (string): Only include sessions from this game version

### `glitchless_compare_versions` (~218 tokens)

Compare game versions side by side, in the game's own terms first: the stats on its boards (glitchless_dashboard) and its own events per session, then the built-in measures it reports (frame time overall and per level, hitches/min, crash-free and error-free sessions, errors per session, level completion, rage-quit rate, deaths per session, geometry growth). Use it to confirm a fix or a design change after shipping a new version.

Input parameters:

- `a` (string): Baseline version (default: second newest)
- `b` (string): New version (default: newest)
- `hours` (number): Look-back window in hours (default 24). Up to the plan's retention on Glitchless Cloud: 336 (14 days) on Free, 2160 (90 days) on Indie, 9600 (400 days) on Studio. Past 744 (31 days) answers are by da…
- `service` (string): Game service name (defaults to the most recently active game)

### `glitchless_session` (~102 tokens)

One play session in detail: device/GPU, outcome (crashed, rage quit), and the full event timeline (levels, deaths with positions, errors, hitches with causes, agent annotations) plus per-5s frame stats. Use with session ids from errors, hitches or rage quits.

Input parameters:

- `service` (string): Game service name (defaults to the most recently active game)
- `session_id` (string, required): Session id (s_…)

### `glitchless_playtest` (~237 tokens)

Playtest the game with its autoplay bots and compare against a saved baseline. Bots play fixed-seed scenarios in real Chrome, one at a time, against the running game; Glitchless then compares frame time (overall and per level), render CPU, draw calls, errors, crashes, completion and deaths with the baseline. Regressions fail; warnings and improvements are listed. Call with save_as "baseline" BEFORE changing code, then without arguments AFTER the change. Takes 1–5 minutes (quick: about 1). Needs the game and the Glitchless server running and Playwright installed in the project.

Input parameters:

- `compare_to` (string): Saved run to compare with (default "baseline" when saved)
- `game_url` (string): Game URL to play (default http://localhost:5173/ or glitchless.playtest.json)
- `max_seconds` (number): Cap each run at this many seconds
- `quick` (boolean): Play only the first scenario (about a minute)
- `save_as` (string): Save this run under a name, e.g. "baseline" before a change

## Diagnostics

Captured diagnostic sections: Provenance, Dependencies. The full working is on the page: https://verifymcp.io/servers/glitchless-gg-glitchless/glitchless-mcp#diagnostics

## Score history

- 2026-10-23: 68
- 2026-10-22: 42
- 2026-10-21: 54

## Common questions

### What is the Glitchless MCP server?

Glitchless is an MCP server listed in the public MCP registry as io.github.glitchless-gg/glitchless. Game observability for coding agents: stutter, crashes, where players quit, and playtest bots. This page covers its npm package (glitchless-mcp).

### Is the Glitchless MCP server safe to use?

Glitchless scores 68 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 23 October 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 Glitchless MCP server expose?

Glitchless exposes 13 tools: glitchless_list_games, glitchless_triage, glitchless_overview, glitchless_performance, glitchless_get_error, and 8 more. Their descriptions and schemas cost roughly 2,428 tokens of context every time the server is loaded.

### Is the Glitchless MCP server still maintained?

Glitchless is still listed as active in the MCP registry. We last reached this channel on 23 October 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 Glitchless MCP server under?

Glitchless declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.

## Links

- npm package: https://www.npmjs.com/package/glitchless-mcp
- Socket report: https://socket.dev/npm/package/glitchless-mcp
- Repository: https://github.com/glitchless-gg/glitchless
- Website: https://www.glitchless.gg/
- Changelog RSS feed: https://verifymcp.io/servers/glitchless-gg-glitchless/glitchless-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/glitchless-gg-glitchless/glitchless-mcp.json
- HTML version of this page: https://verifymcp.io/servers/glitchless-gg-glitchless/glitchless-mcp