YouGame
REMOTE · YOUGAME.CO · SCANNED OCT 4
Publish a browser game on YouGame: the build rules, the leaderboard SDK, pre-upload checks.
Available components
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 Security94
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- The endpoint enforces authorisation, advertised via RFC 9728 protected-resource metadata. View diagnostics → Pass
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
- The authorisation server offers only Dynamic Client Registration (RFC 7591), which MCP 2026-07-28 deprecated in favour of Client ID Metadata Documents. View diagnostics → Partial
Transport & Reachability0
- Transport blocked by authentication: the endpoint requires auth we don't have to verify streamable-http. See how to fix → View diagnostics → Unverified
Schema Quality & AI Usability0
- Schema blocked by authentication: the endpoint requires auth we don't have to read it. See how to fix → Unverified
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
- Tool coverage blocked by authentication: the endpoint requires auth we don't have to read its tools.Unverified
Tool Safety0
- Tool safety blocked by authentication: the endpoint requires auth we don't have to read its tools.Unverified
Capabilities0
- Capabilities blocked by authentication: the endpoint requires auth we don't have to read them. See how to fix → Unverified
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. Claim this server and supply a read-only token to verify it and lift the score.
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.
remote · yougame.co
claude mcp add --transport http co-yougame-yougame 'https://yougame.co/mcp'
{
"mcpServers": {
"co-yougame-yougame": {
"url": "https://yougame.co/mcp"
}
}
} {
"servers": {
"co-yougame-yougame": {
"type": "http",
"url": "https://yougame.co/mcp"
}
}
} [mcp_servers.co-yougame-yougame] url = "https://yougame.co/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"co-yougame-yougame": {
"type": "remote",
"url": "https://yougame.co/mcp",
"enabled": true
}
}
} openclaw mcp add co-yougame-yougame --url 'https://yougame.co/mcp' --transport streamable-http
mcp_servers:
co-yougame-yougame:
url: "https://yougame.co/mcp" {
"McpServers": {
"co-yougame-yougame": {
"Transport": "http",
"Url": "https://yougame.co/mcp"
}
}
} assistant mcp add co-yougame-yougame -t streamable-http -u 'https://yougame.co/mcp'
{
"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.
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.
- 28 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
- 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
- 7 Sept 26 −34
- Endpoint reachability: reachable → behind authorisation ▼ security
- Stability: fail → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- Transport: pass → unverified ▼ security
- Authorization: partial → pass ▲ security
- First check of Authorization: partial security
- Capabilities: fail → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- Schema quality: 100 → unverified ▼ functional
- 6 Sept 26 −1
- 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 security
- Schema quality: 136 → 253 ▼ functional
- “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” functional
- “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 cosmetic
- 5 Sept 26 73
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 4 Oct 2026 · Probed https://yougame.co/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=yougame.co | CN=WE1,O=Google Trust Services,C=US | 3 Oct 2026 | 1 Jan 2027 | ECDSA 256 | ECDSA-SHA256 | 6cb5005befce75250e26aa45e6a0a640 |
| SANs: yougame.co, staging.yougame.co, *.staging.yougame.co | ||||||
| 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 yougame.co. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| co. | present | 7786 | 8 | Verified |
| yougame.co. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Enforced and verified
The endpoint asked for a token and published valid RFC 9728 metadata describing how to get one.
| Result | Enforced and verified |
|---|---|
| Enforced | On connection |
| HTTP status | 401 |
WWW-Authenticate challenge Bearer realm="YouGame", resource_metadata="https://yougame.co/.well-known/oauth-protected-resource/mcp"
Bearer realm="YouGame", resource_metadata="https://yougame.co/.well-known/oauth-protected-resource/mcp"| Header | Value |
|---|---|
| strict-transport-security | max-age=15552000; includeSubDomains |
| content-security-policy | frame-src 'self' https://*.yougame.co http://127.0.0.1:* https://127.0.0.1:* https://js.stripe.com https://checkout.stripe.com; report-uri /api/csp-report |
| x-content-type-options | nosniff |
| x-frame-options | SAMEORIGIN |
| referrer-policy | strict-origin-when-cross-origin |
| www-authenticate | Bearer realm="YouGame", resource_metadata="https://yougame.co/.well-known/oauth-protected-resource/mcp" |
Protected resource metadata
| Document | https://yougame.co/.well-known/oauth-protected-resource/mcp |
|---|---|
| Retrieved | Yes |
| Resource | https://yougame.co/mcp |
| Authorisation server | https://yougame.co |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://yougame.co/mcp | Auth required | 401 | |
| http (plaintext) | http://yougame.co/mcp | HTTPS enforced | 308 | https://yougame.co/mcp |
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 →
check_build ~128
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.
| Name | Type | Req | Description |
|---|---|---|---|
| files | array | yes | Every file in the build folder. |
No output schema declared.
No examples provided.
fetch ~50
Returns the full text of one YouGame documentation section by the id search returned (for example "sdk#leaderboards").
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | Section id from search, e.g. sdk#leaderboards |
No output schema declared.
No examples provided.
get_publish_guide ~61
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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_sdk_reference ~52
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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
my_games ~103
The games the API key's creator has published on YouGame: slug, URL, title, version, plays, SDK features. Needs the creator's API key.
| Name | Type | Req | Description |
|---|---|---|---|
| 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… |
No output schema declared.
No examples provided.
prepare_submission ~798
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | How the game is played. Default Keyboard. |
| description | string | yes | Up to 1000 characters: what the game is and how to play. Write it from the game. |
| genres | array | yes | Up to 3; the first is the main one. |
| mature | boolean | yes | 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 | yes | 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 | yes | 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 | yes | 1–80 characters. |
| uploadId | string | yes | From the upload reply (32 hex characters). |
No output schema declared.
No examples provided.
publish_game ~585
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | 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 | yes | From the upload reply (32 hex characters). |
No output schema declared.
No examples provided.
search ~87
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.
| Name | Type | Req | Description |
|---|---|---|---|
| query | string | yes | What to look for, e.g. "submit a score" or "Unity compression" |
No output schema declared.
No examples provided.
update_game ~441
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | 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 | yes | The new build, from the upload reply (32 hex characters). |
No output schema declared.
No examples provided.
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.