games.playfrog/publish
REMOTE · MCP.PLAYFROG.GAMES · SCANNED AUG 3
Publish browser games to Playfrog and get a shareable play link. Free, no account needed.
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 →
Endpoint Security46
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation check failed: no authorisation is required to call this server, and it exposes a tool marked destructive (publish_game). See how to fix → View diagnostics → Fail
- HTTPS not yet verified: we couldn't determine whether a plaintext access path exists. View diagnostics → Unverified
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability62
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 662 tokens (~331/item across 2 items; 2 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management27
- Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage97
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 88% of tool parameters carry a description.Partial
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.
remote · mcp.playfrog.games
claude mcp add --transport http games-playfrog-publish https://mcp.playfrog.games/mcp
[mcp_servers.games-playfrog-publish] url = "https://mcp.playfrog.games/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"games-playfrog-publish": {
"type": "remote",
"url": "https://mcp.playfrog.games/mcp",
"enabled": true
}
}
} openclaw mcp add games-playfrog-publish --url https://mcp.playfrog.games/mcp --transport streamable-http
mcp_servers:
games-playfrog-publish:
url: "https://mcp.playfrog.games/mcp" {
"mcpServers": {
"games-playfrog-publish": {
"type": "http",
"url": "https://mcp.playfrog.games/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.
- 3 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.
- 1 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.
- 31 Jul 26 −1
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 30 Jul 26 −2
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 29 Jul 26 +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.
- 28 Jul 26 +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.
- 27 Jul 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
- 26 Jul 26 57
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 3 Aug 2026 · Probed https://mcp.playfrog.games/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=playfrog.games | CN=WE1,O=Google Trust Services,C=US | 21 Jul 2026 | 19 Oct 2026 | ECDSA 256 | ECDSA-SHA256 | 89a9072d1891f8071393dbb1dae9d444 |
| SANs: playfrog.games, mcp.playfrog.games, *.mcp.playfrog.games | ||||||
| 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 |
DNSSEC insecure
Validation of mcp.playfrog.games. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| games. | present | 54412 | 8 | Verified |
| playfrog.games. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://mcp.playfrog.games/mcp | Verified | 200 | |
| http (plaintext) | http://mcp.playfrog.games/mcp | Inconclusive | 406 |
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.
publish_game ~354
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, 8 MB total maximum. 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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | — |
| 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. |
| Name | Type | Req | Description |
|---|---|---|---|
| action_required | string | — | — |
| claim_url | — | yes | — |
| expires_at | — | yes | — |
| game_id | string | yes | — |
| game_url | string | yes | — |
| manage_token | string | yes | — |
| metadata_hint | string | — | — |
| play_url | string | yes | — |
| slug | string | yes | — |
| status | string | yes | — |
| version_id | string | yes | — |
No examples provided.
update_game ~308
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | — |
| game_id | string | yes | 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 | yes | 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. |
| Name | Type | Req | Description |
|---|---|---|---|
| action_required | string | — | — |
| claim_url | — | yes | — |
| expires_at | — | yes | — |
| game_id | string | yes | — |
| game_url | string | yes | — |
| manage_token | string | yes | — |
| metadata_hint | string | — | — |
| play_url | string | yes | — |
| slug | string | yes | — |
| status | string | yes | — |
| version_id | string | yes | — |
No examples provided.