# YouGame (remote · yougame.co)

Publish a browser game on YouGame: the build rules, the leaderboard SDK, pre-upload checks.

- Trust score: 38/100 (low)
- Change this week: 0
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-10-04

## Components

- remote · `yougame.co`: 38/100 (this document), [markdown](https://verifymcp.io/servers/co-yougame-yougame/yougame.md), [page](https://verifymcp.io/servers/co-yougame-yougame/yougame)

## Channel facts

- Endpoint: `https://yougame.co/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.0`

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

- **Endpoint Security**: 94/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - The endpoint enforces authorisation, advertised via RFC 9728 protected-resource metadata.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
  - The authorisation server offers only Dynamic Client Registration (RFC 7591), which MCP 2026-07-28 deprecated in favour of Client ID Metadata Documents.
- **Transport & Reachability**: 0/100
  - Transport blocked by authentication: the endpoint requires auth we don't have to verify streamable-http.
- **Schema Quality & AI Usability**: 0/100
  - Schema blocked by authentication: the endpoint requires auth we don't have to read it.
- **Stability & Change Management**: 0/100
  - Stability not yet verified: not enough scan history yet (needs a 30-day window).
- **Tool Coverage**: 0/100
  - Tool coverage blocked by authentication: the endpoint requires auth we don't have to read its tools.
- **Tool Safety**: 0/100
  - Tool safety blocked by authentication: the endpoint requires auth we don't have to read its tools.
- **Capabilities**: 0/100
  - Capabilities blocked by authentication: the endpoint requires auth we don't have to read them.

**Unverified: 6 categories.** Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.

## Install

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

YouGame is a hosted endpoint at https://yougame.co/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 co-yougame-yougame 'https://yougame.co/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "co-yougame-yougame": {
      "url": "https://yougame.co/mcp"
    }
  }
}
```

### VS Code

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

### Codex

```toml
[mcp_servers.co-yougame-yougame]
url = "https://yougame.co/mcp"
```

### opencode

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

### OpenClaw

```bash
openclaw mcp add co-yougame-yougame --url 'https://yougame.co/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  co-yougame-yougame:
    url: "https://yougame.co/mcp"
```

### Netclaw

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

### Vellum

```bash
assistant mcp add co-yougame-yougame -t streamable-http -u 'https://yougame.co/mcp'
```

### Other

```json
{
  "mcpServers": {
    "co-yougame-yougame": {
      "type": "http",
      "url": "https://yougame.co/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-28 (score 38, 0)

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

### 2026-09-25 (score 38, 0)

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

### 2026-09-07 (score 38, −34)

- [security regression] Endpoint reachability: reachable → behind authorisation
- [security regression] Stability: fail → unverified
- [security regression] Tool safety: pass → unverified
- [security regression] Transport: pass → unverified
- [security improvement] Authorization: partial → pass
- [security] First check of Authorization: partial
- [functional regression] Capabilities: fail → unverified
- [functional regression] Tool coverage: 100 → unverified
- [functional regression] Schema quality: 100 → unverified

### 2026-09-06 (score 72, −1)

- [security regression] Stability: unverified → fail
- [security] The server rewrote its instructions, which are the text every model session reads
- [security] Tool “my_games” rewrote its description, which is the text the model reads
- [security] Tool “publish_game” rewrote its description, which is the text the model reads
- [functional regression] Schema quality: 136 → 253
- [functional regression] “publish_game” added a required parameter “creator_approved”, so existing callers break
- [functional] Server version: 1.1.0 → 1.2.0
- [functional] New tool “prepare_submission”
- [functional] New tool “update_game”
- [cosmetic] “publish_game” added an optional parameter “paywalls”
- [cosmetic] “publish_game” reworded the description of “controls”
- [cosmetic] “publish_game” reworded the description of “description”
- [cosmetic] “publish_game” reworded the description of “mature”
- [cosmetic] “publish_game” reworded the description of “max_score”
- [cosmetic] “publish_game” reworded the description of “thumbnail”
- [cosmetic] “publish_game” made “title” optional

### 2026-09-05 (score 73)

First indexed and scored.

## MCP tools (9)

### `get_publish_guide` (~61 tokens)

The rules a browser game must follow to run on YouGame (build layout, paths, limits, the runtime sandbox, what usually breaks and how to fix it) plus how to verify and upload. Read this first when making a game YouGame-ready.

### `get_sdk_reference` (~52 tokens)

The complete YouGame SDK reference: leaderboards (gameOver / submitScore), beat-my-score links, online multiplayer with matchmaking, friend invites, skill ratings, and coins. One script tag, no account needed.

### `check_build` (~128 tokens)

Runs YouGame's pre-upload checks on a build folder and returns a verdict: ready, risky (warnings), or broken (the game will not start). Pass every file path in the folder (relative to the folder, forward slashes) and the text of index.html; also pass the text of .html/.css/.js files worth scanning (8 MB of text in total). Fix what it reports and run it again until the verdict is ready, then zip the folder's contents for upload at https://yougame.co/upload.

Input parameters:

- `files` (array, required): Every file in the build folder.

### `search` (~87 tokens)

Searches the YouGame documentation (the publish guide and the SDK reference) and returns matching sections with ids. Use it to answer a specific question — how scores are posted, what multiplayer guarantees, what breaks a build — without reading a whole document, then call fetch with an id.

Input parameters:

- `query` (string, required): What to look for, e.g. "submit a score" or "Unity compression"

### `fetch` (~50 tokens)

Returns the full text of one YouGame documentation section by the id search returned (for example "sdk#leaderboards").

Input parameters:

- `id` (string, required): Section id from search, e.g. sdk#leaderboards

### `prepare_submission` (~798 tokens)

Fills in the whole YouGame listing of a staged build and saves it as a draft for the creator to review. Needs the creator's API key. First stage the build: zip the build folder's contents and POST the zip as the raw body to https://yougame.co/api/agent/upload with header "Authorization: Bearer $YOUGAME_API_KEY" (for example: curl -sS -X POST https://yougame.co/api/agent/upload -H "Authorization: Bearer $YOUGAME_API_KEY" -H "Content-Type: application/zip" --data-binary @build.zip). The reply has the uploadId, a testUrl where the build already runs, and the check report; if the verdict is broken, fix it and upload again. Then call this tool with the uploadId and every listing field, decided from what you know about the game: title, description, genres, controls, play mode, phones, mature, a maximum score if the game has a natural one, the paywalls it charges, and a thumbnail. Ask the creator first about anything you cannot decide from the game itself (a thumbnail when the build has no 16:9 image: offer to make one or to use theirs; whether it is for adults; paywall prices), and again about anything the reply lists under questions, then call this tool again with the answers. The reply has the review link: give it to the creator. They see every field filled in, change what they want, and press Publish; nothing is live until they do. Never call publish_game instead of handing over the link unless the creator explicitly asked you to publish without reviewing.

Input parameters:

- `api_key` (string): Only when the key could not be set as the Authorization header of the MCP connection: the creator's API key (yg_…). Prefer the header (or the YOUGAME_API_KEY environment variable): a key passed here…
- `controls` (string, required): How the game is played. Default Keyboard.
- `description` (string, required): Up to 1000 characters: what the game is and how to play. Write it from the game.
- `genres` (array, required): Up to 3; the first is the main one.
- `mature` (boolean, required): True when the game is for adults only (blood and gore, strong language, mature themes). Ask the creator if the game's content leaves it unclear.
- `max_score` (number): Optional: the highest score the game can produce. Scores above it are held for review. Work it out from the game's scoring, or leave it out.
- `mobile` (boolean, required): True only when the game plays with touch (pointer events, on-screen controls, 44 px targets, fills the screen). Lists it for phones.
- `notes` (string): Up to 2000 characters, shown to the creator above the form: what you chose and why, and what you assumed (the genres, the max score, why mobile is off).
- `paywalls` (array): The paywalls the build charges with YouGame.coins.charge(key), each priced by the creator: ask them for the price and kind. Leave it out when the game charges nothing.
- `play_mode` (string, required): single (solo only), multiplayer (online only), or both. Default: multiplayer when the build calls findMatch, else single.
- `screenshots` (array): Optional: up to 8 image paths inside the build.
- `thumbnail` (string): The path, inside the build, of a 16:9 PNG/JPG/WebP/GIF under 8 MB for the game's card. Not needed again once one was sent with PUT /api/agent/media.
- `title` (string, required): 1–80 characters.
- `uploadId` (string, required): From the upload reply (32 hex characters).

### `publish_game` (~585 tokens)

Publishes a staged build as a game on YouGame, live at once, skipping the creator's review. Needs the creator's API key and their explicit instruction: the normal path is prepare_submission, which hands the creator a review link where they press Publish themselves. Call this only when the creator explicitly told you, in their own words, to publish without opening the review page ("looks good" about a draft is not that); never because it is faster. After prepare_submission the uploadId alone is enough (every other field keeps the draft's value); otherwise pass the listing fields.

Input parameters:

- `api_key` (string): Only when the key could not be set as the Authorization header of the MCP connection: the creator's API key (yg_…). Prefer the header (or the YOUGAME_API_KEY environment variable): a key passed here…
- `controls` (string): How the game is played. Default Keyboard.
- `creator_approved` (boolean, required): True only when the creator explicitly told you, in their own words, to publish this game without opening the review page. Approval of a draft summary in chat does not count. Never assume it; the tool…
- `description` (string): Up to 1000 characters: what the game is and how to play. Write it from the game.
- `genres` (array): Up to 3; the first is the main one.
- `mature` (boolean): True when the game is for adults only (blood and gore, strong language, mature themes). Ask the creator if the game's content leaves it unclear.
- `max_score` (number): Optional: the highest score the game can produce. Scores above it are held for review. Work it out from the game's scoring, or leave it out.
- `mobile` (boolean): True only when the game plays with touch (pointer events, on-screen controls, 44 px targets, fills the screen). Lists it for phones.
- `paywalls` (array): The paywalls the build charges with YouGame.coins.charge(key), each priced by the creator: ask them for the price and kind. Leave it out when the game charges nothing.
- `play_mode` (string): single (solo only), multiplayer (online only), or both. Default: multiplayer when the build calls findMatch, else single.
- `screenshots` (array): Optional: up to 8 image paths inside the build.
- `thumbnail` (string): The path, inside the build, of a 16:9 PNG/JPG/WebP/GIF under 8 MB for the game's card. Not needed again once one was sent with PUT /api/agent/media.
- `title` (string): 1–80 characters.
- `uploadId` (string, required): From the upload reply (32 hex characters).

### `update_game` (~441 tokens)

Ships a new build of a game the creator already published, as its next version: same link, same origin, scores and comments kept. Needs the creator's API key. Stage the new build exactly as for publish_game (zip, POST to https://yougame.co/api/agent/upload, fix what the report calls broken), then call this tool (or POST the same fields to https://yougame.co/api/agent/update) with the game's slug (from my_games or its URL), the new uploadId, the kind of update, and patch notes. kind "major" (2.0) is for a big change: everyone who saved or liked the game is notified with the notes, and the home feed features the game for a week. kind "minor" (1.1) is for fixes and small changes: listed in the version history, nobody is pinged. Default to minor unless the creator says the update is big.

Input parameters:

- `api_key` (string): Only when the key could not be set as the Authorization header of the MCP connection: the creator's API key (yg_…). Prefer the header (or the YOUGAME_API_KEY environment variable): a key passed here…
- `kind` (string): major (big change, players are notified) or minor (fixes, silent). Default minor.
- `notes` (string): Patch notes, up to 2000 characters: what changed, for players. Shown on the game page and, for a major update, in the notification.
- `screenshots` (array): Optional: new screenshots, as paths inside the new build. Omit to keep the current ones.
- `slug` (string, required): The game's slug: the last part of its URL, https://yougame.co/g/<slug>.
- `thumbnail` (string): Optional: a new thumbnail, as a path inside the new build (16:9 PNG/JPG/WebP/GIF under 8 MB). Omit to keep the current one.
- `uploadId` (string, required): The new build, from the upload reply (32 hex characters).

### `my_games` (~103 tokens)

The games the API key's creator has published on YouGame: slug, URL, title, version, plays, SDK features. Needs the creator's API key.

Input parameters:

- `api_key` (string): Only when the key could not be set as the Authorization header of the MCP connection: the creator's API key (yg_…). Prefer the header (or the YOUGAME_API_KEY environment variable): a key passed here…

## Diagnostics

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

## Score history

- 2026-10-04: 38
- 2026-10-03: 38
- 2026-10-02: 38
- 2026-10-01: 38
- 2026-09-30: 38
- 2026-09-29: 38
- 2026-09-28: 38
- 2026-09-27: 38
- 2026-09-26: 38
- 2026-09-25: 38
- 2026-09-24: 38
- 2026-09-23: 38
- 2026-09-22: 38
- 2026-09-21: 38
- 2026-09-20: 38
- 2026-09-19: 38
- 2026-09-18: 38
- 2026-09-17: 38
- 2026-09-16: 38
- 2026-09-15: 38
- 2026-09-14: 38
- 2026-09-13: 38
- 2026-09-12: 38
- 2026-09-11: 38
- 2026-09-10: 38
- 2026-09-09: 38
- 2026-09-08: 38
- 2026-09-07: 38
- 2026-09-06: 72
- 2026-09-05: 73

## Common questions

### What is the YouGame MCP server?

YouGame is an MCP server listed in the public MCP registry as co.yougame/yougame. Publish a browser game on YouGame: the build rules, the leaderboard SDK, pre-upload checks. This page covers its hosted endpoint (https://yougame.co/mcp).

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

YouGame scores 38 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 YouGame MCP server expose?

YouGame exposes 9 tools: get_publish_guide, get_sdk_reference, check_build, search, fetch, and 4 more. Their descriptions and schemas cost roughly 2,305 tokens of context every time the server is loaded.

### Does the YouGame MCP server require authentication?

Yes. YouGame asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.

### Is the YouGame MCP server still maintained?

YouGame is still listed as active in the MCP registry. We last reached this channel on 4 October 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://yougame.co/mcp
- Website: https://yougame.co/plugin
- Changelog RSS feed: https://verifymcp.io/servers/co-yougame-yougame/yougame.xml
- Changelog JSON feed: https://verifymcp.io/servers/co-yougame-yougame/yougame.json
- HTML version of this page: https://verifymcp.io/servers/co-yougame-yougame/yougame