publish MCP server
games.playfrog/publishplayfrog.gamesstreamable-httpv0.2.0Scanned
Publish browser games to Playfrog and get a shareable play link. Static HTML5, files sent inline.
2 tools: 2 can delete or cancel things.
- Reads private data · 0
- Reads text others write · 2
- Can send data out · 1
- No findings
Sign-in required, no OAuth metadata. Remote posture
Anlyon alternative
2 of these tools change something. Run those as governed actions.
Declare what an action changes, and Anlyon puts it under a shared limit, binds every approval to the exact request, and grades the outcome. It works on any HTTPS API you can describe as an action.
Anlyon Radar does not run, proxy or govern this MCP server. A tool your own code calls directly is not routed through Anlyon and is not governed by it.
Import an OpenAPI spec →What the publish MCP server can do
The publish MCP server is published by playfrog.games, a domain the MCP Registry verified. It has 2 tools. It can delete or cancel things (2 tools: publish_game and update_game). None of its tools only reads.
2 tools bring in text other people can write (publish_game and update_game); 1 tool can send data out of your system (publish_game).
None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.
Last scanned Nov 2, 2026, version 0.2.0.
Tools
Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.
2 tools
Deletes or cancels 2Claude Code: deny
publish_gamePublish a browser game (HTML5/JavaScript, static files) to Playfrog and get a public, shareable play link in seconds.Reads text others writeCan send data outNo findings
Why it is in this group
- The name "publish_game" says "publish": a word for a change that another call does not undo.
- The server marks it destructive (destructiveHint: true).
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
- outboundThe name "publish_game" says "publish": it sends or publishes something to other people.
Description, as the server wrote it 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.
Annotations the server declares
- title: Publish a game to Playfrog
- readOnlyHint: false
- destructiveHint: true
- idempotentHint: false
- openWorldHint: true
update_gamePublish a new version of an existing Playfrog game at the same play link.Reads text others writeNo findings
Why it is in this group
- The name "update_game" says "update": a word for a change.
- The description's first verb is "publish": a word for a change that another call does not undo.
- The server marks it destructive (destructiveHint: true).
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it 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.
Annotations the server declares
- title: Update a Playfrog game
- readOnlyHint: false
- destructiveHint: true
- idempotentHint: false
- openWorldHint: true
This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.
Exfil surface
Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.
No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data.
- Reads private data0
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write2
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out1
- Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.
Remote posture
What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.
Looked at Nov 20, 2026, 18:54 UTC, unchanged since Nov 13, 2026. No credentials were sent and no tool was called. What is looked at.
- Reachable
- yes
- HTTP status of an anonymous initialize
- 522
- tools/list served without credentials
- no
- Tools that change things, listed without credentials
- 0
- Protocol version
- not observed
- WWW-Authenticate on 401
- not observed
- resource_metadata in WWW-Authenticate
- not observed
- RFC 9728 protected resource metadata
- not observed
- Authorization servers
- not observed
- Legacy HTTP+SSE transport
- no
- Dynamic client registration
- not observed
- Client ID metadata documents
- not observed
The probe stopped: initialize answered HTTP 522.
Posture changes
- Nov 13, 2026
- HTTP status of an anonymous initialize: 200 to 522
- tools/list served without credentials: yes to no
- Tools that change things, listed without credentials: 2 to 0
- Protocol version: 2025-06-18 to none
Findings
Matches of fixed checks, with the text they matched.
No check matched anything in these tool definitions. That is not a safety guarantee.
History
Changes to its tool definitions and to its remote endpoint, newest first.
PostureRemote posture changed. HTTP status of an anonymous initialize: 200 -> 522; tools/list served without credentials: yes -> no; Tools that change things, listed without credentials: 2 -> 0 (and 1 more).View diff
- HTTP status of an anonymous initialize: 200 to 522
- tools/list served without credentials: yes to no
- Tools that change things, listed without credentials: 2 to 0
- Protocol version: 2025-06-18 to none
Install
Pinned to version 0.2.0. Values in angle brackets are yours to fill in.
claude mcp add --transport http publish https://mcp-open.playfrog.games/mcpclaude mcp add --transport http publish https://mcp-open.playfrog.games/mcpRun in a terminal.
Claude Code permissions
Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.
{
"permissions": {
"allow": [],
"ask": [],
"deny": [
"mcp__publish__publish_game",
"mcp__publish__update_game"
]
}
}Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as publish. Review it before you use it.
Capability tags behind 2 rules
- mcp__publish__publish_game untrusted-input, outbound
- mcp__publish__update_game untrusted-input
Pin
Keep the decision: fail CI when the tools change, follow every change, or show a badge.
Pin in CI
Fail a build when the tools you reviewed are not the tools the server serves today.
curl -s "https://radar.anlyon.com/api/v1/servers/games.playfrog/publish/verify?hash=c01c83368a942548ae48fce922ee8d41a7ef1017c35e3c2fc6af736111c9e660" | jq -e '.changed == false'Pinned hash c01c83368a94, from Nov 2, 2026, 06:18 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/games.playfrog/publish/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/games.playfrog/publish)Source: MCP Registry. Synced Oct 21, 2026, 18:13 UTC.
publish MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the publish MCP server safe?
- No scan can promise that. What its definitions show: 2 tools, 2 of which can change, send or delete something, and 0 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.
Can the publish MCP server delete data?
- Yes. 2 tools can delete, cancel or revoke something: publish_game and update_game.
Can the publish MCP server do things that cannot be undone?
- No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.
What tools does the publish MCP server have?
- 2 tools: 2 destructive. publish_game and update_game.
Does the publish MCP server need sign-in or OAuth?
- Its remote endpoint did not answer the last anonymous look.
Does the publish MCP server send data to outside services?
- 1 tool can carry data out (it sends, posts or publishes, or takes a recipient, channel or URL): publish_game.
Has the publish MCP server changed its tools?
- Not since Anlyon Radar started tracking it. Last scanned Nov 2, 2026.