Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

games.playfrog/publish

REMOTE · MCP-OPEN.PLAYFROG.GAMES

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

0 this week 68 Trust /100

Last scanned (13 hours ago)

Scores higher than 57% of remote servers

Reachable. Last reached 24 Oct 2026.

Category Entertainment and Games

Trust breakdown (7 categories)

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 Security46
Transport & Reachability100
Schema Quality & AI Usability55
  • AI-judged instruction clarity (good).Pass
  • 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. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
  • No destabilizing schema changes in the last 30 days.Pass
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
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • All 2 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
  • An AI judge read all 2 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
  • Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
Changelog

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
  • 11 Sept 26 0
    • Stability: 0.97 → pass security
  • 26 Aug 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
  • 13 Aug 26 0
    • Stability: unverified → 0.03 ▲ functional
  • 12 Aug 26 0

    First indexed and scored.

Diagnostics

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 24 Oct 2026 · Probed https://mcp-open.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 10 Oct 2026 8 Jan 2027 ECDSA 256 ECDSA-SHA256 bafd7ac491d0193d13cd3149786e7004
SANs: playfrog.games, mcp-open.playfrog.games, *.mcp-open.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

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of mcp-open.playfrog.games. — Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
games. present 52900 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

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://mcp-open.playfrog.games/mcp Verified 200
http (plaintext) http://mcp-open.playfrog.games/mcp Inconclusive 406
MCP tools · 2 exposed · ~720 tokens

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 →

Tool Tokens
publish_game ~412

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.

NameTypeReqDescription
controlsstring–E.g. "WASD to move, space to shoot".
coverobject–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.
descriptionstring–2 to 4 real sentences: what the game is, how to play, what makes it fun. Players read this before playing.
filesarrayyes–
genrestring–The gallery category the game is filed under (e.g. arcade, puzzle, platformer). Improves discoverability.
orientationstring–Only if the game works one way; phones held wrong get a rotate overlay.
titlestring–The game title players will see.
NameTypeReqDescription
action_requiredstring––
claim_url–yes–
dropped_filesarray––
expires_at–yes–
game_idstringyes–
game_urlstringyes–
manage_tokenstringyes–
metadata_hintstring––
play_urlstringyes–
slugstringyes–
statusstringyes–
version_idstringyes–

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.

NameTypeReqDescription
controlsstring–E.g. "WASD to move, space to shoot".
coverobject–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.
descriptionstring–2 to 4 real sentences: what the game is, how to play, what makes it fun. Players read this before playing.
filesarrayyes–
game_idstringyesFrom the publish_game response.
genrestring–The gallery category the game is filed under (e.g. arcade, puzzle, platformer). Improves discoverability.
manage_tokenstringyesFrom the publish_game response (starts with pfm_).
notesstring–One line about what changed in this version.
orientationstring–Only if the game works one way; phones held wrong get a rotate overlay.
titlestring–The game title players will see.
NameTypeReqDescription
action_requiredstring––
claim_url–yes–
dropped_filesarray––
expires_at–yes–
game_idstringyes–
game_urlstringyes–
manage_tokenstringyes–
metadata_hintstring––
play_urlstringyes–
slugstringyes–
statusstringyes–
version_idstringyes–

No examples provided.

Install

How do I install the games.playfrog/publish MCP server?

games.playfrog/publish is a hosted endpoint at https://mcp-open.playfrog.games/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 · mcp-open.playfrog.games

# add to Claude Code
claude mcp add --transport http games-playfrog-publish 'https://mcp-open.playfrog.games/mcp'
Common questions

What is the games.playfrog/publish MCP server?

games.playfrog/publish is an MCP server listed in the public MCP registry as games.playfrog/publish. Publish browser games to Playfrog and get a shareable play link. Static HTML5, files sent inline. This page covers its hosted endpoint (https://mcp-open.playfrog.games/mcp).

Is the games.playfrog/publish MCP server safe to use?

games.playfrog/publish scores 68 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 games.playfrog/publish MCP server expose?

games.playfrog/publish exposes 2 tools: publish_game, update_game. Their descriptions and schemas cost roughly 720 tokens of context every time the server is loaded.

Does the games.playfrog/publish MCP server require authentication?

No. We connected to games.playfrog/publish without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the games.playfrog/publish MCP server still maintained?

games.playfrog/publish is still listed as active in the MCP registry. We last reached this channel on 24 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.