# games.playfrog/publish (remote · mcp-open.playfrog.games)

Publish browser games to Playfrog and get a shareable play link. Static HTML5, files sent inline.

- Trust score: 57/100 (low)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-08-22

## Components

- remote · `mcp-open.playfrog.games`: 57/100 (this document), [markdown](https://verifymcp.io/servers/games-playfrog-publish/mcp-open.md), [page](https://verifymcp.io/servers/games-playfrog-publish/mcp-open)

## Channel facts

- Endpoint: `https://mcp-open.playfrog.games/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `0.2.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-08-22.

- **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 (publish_game).
  - HTTPS enforcement could not be verified: the plaintext port answered with HTTP 406, 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**: 55/100
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 720 tokens (~360/item across 2 items; 2 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 33/100
  - Stability observed for 10 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 97/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 88% of tool parameters carry a description.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **Capabilities**: 60/100
  - Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28.

## Install

### Claude

```bash
claude mcp add --transport http games-playfrog-publish https://mcp-open.playfrog.games/mcp
```

### Codex

```toml
[mcp_servers.games-playfrog-publish]
url = "https://mcp-open.playfrog.games/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "games-playfrog-publish": {
      "type": "remote",
      "url": "https://mcp-open.playfrog.games/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add games-playfrog-publish --url https://mcp-open.playfrog.games/mcp --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  games-playfrog-publish:
    url: "https://mcp-open.playfrog.games/mcp"
```

### Other

```json
{
  "mcpServers": {
    "games-playfrog-publish": {
      "type": "http",
      "url": "https://mcp-open.playfrog.games/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-08-21 (score 57, +1)

No change was recorded against any check on this day. Stability & Change Management went from 27 to 30. That category is still filling its 30-day observation window: 8 days of observed history at the previous scan, 9 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-08-19 (score 56, +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-08-17 (score 55, +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-08-15 (score 54, +1)

No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-08-13 (score 53, +1)

- [functional improvement] Stability: unverified → 0.03

### 2026-08-12 (score 52)

First indexed and scored.

## MCP tools (2)

### `publish_game` (~412 tokens)

Publish a game to Playfrog

Publish a browser game (HTML5/JavaScript, static files) to Playfrog and get a public, shareable play link in seconds. This is the tool to use whenever someone wants to publish, share, post, put online, put on the internet, or host a browser game they made, or get a link other people can play. Free, no account and no API key. Send the game files; an index.html at the top level is required, 2.5 MB of files in total. An optional cover image improves the game page and social share card. Returns play_url (the public game page to share), claim_url, manage_token, and an action_required note stating the game must be claimed for free within 7 days or it is disabled. Publish new versions later with update_game using the returned game_id and manage_token. Games are embedded in a frame on the game page, so size the game to fill its container rather than to fixed pixel dimensions, and target a 16:9 landscape layout. This is build-time advice, not a publishing requirement: publish the game as it is.

Input parameters:

- `controls` (string): E.g. "WASD to move, space to shoot".
- `cover` (object): Optional cover image for the game page and social share card. 1200x630 pixels, PNG/JPEG/WebP, max 3 MB, base64-encoded. Without a cover, a gameplay screenshot is captured automatically.
- `description` (string): 2 to 4 real sentences: what the game is, how to play, what makes it fun. Players read this before playing.
- `files` (array, required)
- `genre` (string): The gallery category the game is filed under (e.g. arcade, puzzle, platformer). Improves discoverability.
- `orientation` (string): Only if the game works one way; phones held wrong get a rotate overlay.
- `title` (string): The game title players will see.

Output parameters:

- `action_required` (string)
- `claim_url`
- `dropped_files` (array)
- `expires_at`
- `game_id` (string)
- `game_url` (string)
- `manage_token` (string)
- `metadata_hint` (string)
- `play_url` (string)
- `slug` (string)
- `status` (string)
- `version_id` (string)

### `update_game` (~308 tokens)

Update a Playfrog game

Publish a new version of an existing Playfrog game at the same play link. Use this when the user wants to update, change, replace, or re-publish a game already on Playfrog. Requires the game_id and manage_token returned by publish_game. Send the complete set of files again, not a diff. Returns the new version_id and the same play_url.

Input parameters:

- `controls` (string): E.g. "WASD to move, space to shoot".
- `cover` (object): Optional cover image for the game page and social share card. 1200x630 pixels, PNG/JPEG/WebP, max 3 MB, base64-encoded. Without a cover, a gameplay screenshot is captured automatically.
- `description` (string): 2 to 4 real sentences: what the game is, how to play, what makes it fun. Players read this before playing.
- `files` (array, required)
- `game_id` (string, required): From the publish_game response.
- `genre` (string): The gallery category the game is filed under (e.g. arcade, puzzle, platformer). Improves discoverability.
- `manage_token` (string, required): From the publish_game response (starts with pfm_).
- `notes` (string): One line about what changed in this version.
- `orientation` (string): Only if the game works one way; phones held wrong get a rotate overlay.
- `title` (string): The game title players will see.

Output parameters:

- `action_required` (string)
- `claim_url`
- `dropped_files` (array)
- `expires_at`
- `game_id` (string)
- `game_url` (string)
- `manage_token` (string)
- `metadata_hint` (string)
- `play_url` (string)
- `slug` (string)
- `status` (string)
- `version_id` (string)

## Diagnostics

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

## Score history

- 2026-08-22: 57
- 2026-08-21: 57
- 2026-08-20: 56
- 2026-08-19: 56
- 2026-08-18: 55
- 2026-08-17: 55
- 2026-08-16: 54
- 2026-08-15: 54
- 2026-08-14: 53
- 2026-08-13: 53
- 2026-08-12: 52

## Links

- Remote endpoint: https://mcp-open.playfrog.games/mcp
- Website: https://playfrog.gg/docs
- Changelog RSS feed: https://verifymcp.io/servers/games-playfrog-publish/mcp-open.xml
- Changelog JSON feed: https://verifymcp.io/servers/games-playfrog-publish/mcp-open.json
- HTML version of this page: https://verifymcp.io/servers/games-playfrog-publish/mcp-open