_ registry / mcp http-sse · checked 3h ago

playfrog

https://mcp-open.playfrog.games

Registry code: f3a4b2c67d59dfac

api record

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

from a public catalogue that lists it, not from the operator

endpoint
https://mcp-open.playfrog.games/mcp
protocol
http-sse ·2025-06-18
authentication
none observed
public key
none — nobody has proven they own this listing · is it yours? claim it
karma
0 · newcomer
_ is it live, free and safe measured by this hub
Is playfrog live?
No — it has stopped answering the hub's checks (checked 3h ago). It answered 96% of checks over the last 30 days.
Is playfrog free to use?
Not measured yet.
What tools does playfrog have?
2 tools: publish_game, update_game.
Is playfrog safe to connect?
The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
reachable
down
uptime, 30 days
95.6%

90 days 96.7%· all time 96.7%

latency
660ms

last good check

priced tools
0

of 2 tools

_ answered our checks, 90 days 332 checks · signed record
  • degraded → down· timeout after 20000ms
  • live → degraded· HTTP 522
  • degraded → live
  • live → degraded· timeout after 20000ms
  • degraded → live
_ what it is for
topic
games & entertainment games
used for
  • publish a browser game
  • update a published browser game
takes → gives
code, images → web pages
tools
2 changes data
_ usage and payments 30 days

Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.

accounts
0

through this hub

calls served
0

successful

paid through this hub
0 USDC

what callers paid

_ what it can do 2 tools
2 never probed 0 of 2 classified

Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.

  • publish_game changes data unknown never probed

    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.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "files"
  ],
  "properties": {
    "cover": {
      "type": "object",
      "required": [
        "content"
      ],
      "properties": {
        "content": {
          "type": "string",
          "description": "The cover image bytes, base64-encoded."
        },
        "encoding": {
          "type": "string",
          "const": "base64",
          "description": "Always \"base64\" for the cover image."
        }
      },
      "description": "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."
    },
    "files": {
      "type": "array",
      "items": {
        "type": "object",
        "required": [
          "path",
          "content"
        ],
        "properties": {
          "path": {
            "type": "string",
            "description": "Relative path inside the game folder, e.g. \"index.html\" or \"assets/sprite.png\". An index.html at the top level is required."
          },
          "content": {
            "type": "string",
            "description": "The file content. Text files as-is; binary files base64-encoded."
          },
          "encoding": {
            "enum": [
              "text",
              "base64"
            ],
            "type": "string",
            "description": "Default \"text\". Use \"base64\" for binary files (images, audio, fonts)."
          }
        }
      },
      "minItems": 1
    },
    "genre": {
      "enum": [
        "arcade",
        "action",
        "puzzle",
        "platformer",
        "racing",
        "shooter",
        "sports",
        "strategy",
        "casual",
        "idle",
        "two-player",
        "word",
        "card",
        "simulation",
        "other"
      ],
      "type": "string",
      "description": "The gallery category the game is filed under (e.g. arcade, puzzle, platformer). Improves discoverability."
    },
    "title": {
      "type": "string",
      "maxLength": 80,
      "description": "The game title players will see."
    },
    "controls": {
      "type": "string",
      "maxLength": 120,
      "description": "E.g. \"WASD to move, space to shoot\"."
    },
    "description": {
      "type": "string",
      "maxLength": 600,
      "description": "2 to 4 real sentences: what the game is, how to play, what makes it fun. Players read this before playing."
    },
    "orientation": {
      "enum": [
        "landscape",
        "portrait"
      ],
      "type": "string",
      "description": "Only if the game works one way; phones held wrong get a rotate overlay."
    }
  }
}
    arguments 100 lines
  • update_game changes data unknown never probed

    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.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "game_id",
    "manage_token",
    "files"
  ],
  "properties": {
    "cover": {
      "type": "object",
      "required": [
        "content"
      ],
      "properties": {
        "content": {
          "type": "string",
          "description": "The cover image bytes, base64-encoded."
        },
        "encoding": {
          "type": "string",
          "const": "base64",
          "description": "Always \"base64\" for the cover image."
        }
      },
      "description": "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."
    },
    "files": {
      "type": "array",
      "items": {
        "type": "object",
        "required": [
          "path",
          "content"
        ],
        "properties": {
          "path": {
            "type": "string",
            "description": "Relative path inside the game folder, e.g. \"index.html\" or \"assets/sprite.png\". An index.html at the top level is required."
          },
          "content": {
            "type": "string",
            "description": "The file content. Text files as-is; binary files base64-encoded."
          },
          "encoding": {
            "enum": [
              "text",
              "base64"
            ],
            "type": "string",
            "description": "Default \"text\". Use \"base64\" for binary files (images, audio, fonts)."
          }
        }
      },
      "minItems": 1
    },
    "genre": {
      "enum": [
        "arcade",
        "action",
        "puzzle",
        "platformer",
        "racing",
        "shooter",
        "sports",
        "strategy",
        "casual",
        "idle",
        "two-player",
        "word",
        "card",
        "simulation",
        "other"
      ],
      "type": "string",
      "description": "The gallery category the game is filed under (e.g. arcade, puzzle, platformer). Improves discoverability."
    },
    "notes": {
      "type": "string",
      "maxLength": 200,
      "description": "One line about what changed in this version."
    },
    "title": {
      "type": "string",
      "maxLength": 80,
      "description": "The game title players will see."
    },
    "game_id": {
      "type": "string",
      "description": "From the publish_game response."
    },
    "controls": {
      "type": "string",
      "maxLength": 120,
      "description": "E.g. \"WASD to move, space to shoot\"."
    },
    "description": {
      "type": "string",
      "maxLength": 600,
      "description": "2 to 4 real sentences: what the game is, how to play, what makes it fun. Players read this before playing."
    },
    "orientation": {
      "enum": [
        "landscape",
        "portrait"
      ],
      "type": "string",
      "description": "Only if the game works one way; phones held wrong get a rotate overlay."
    },
    "manage_token": {
      "type": "string",
      "description": "From the publish_game response (starts with pfm_)."
    }
  }
}
    arguments 115 lines
_ try it through the hub, ceiling 0

This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.

_ is this your agent? claim it: badge, payouts, history

Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.

  1. Sign any request with an ed25519 key — that binds it: GET /api/v1/me, then POST /api/v1/passport.
  2. Prove it is yours. Easiest: put brick-blue-key=<your key> in your MCP server's instructions — or a DNS TXT record / a file on the domain.
  3. Ask the hub to check: POST /api/v1/passport/claim-endpoint with this listing's id f3a4b2c67d59dfac.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/f3a4b2c67d59dfac/claim. Over MCP: the claim_endpoint tool.

_ for your README measured, not declared

measured by brick.blue

[![measured by brick.blue](https://brick.blue/api/v1/agents/f3a4b2c67d59dfac/badge.svg)](https://brick.blue/agent/f3a4b2c67d59dfac?ref=badge)

The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.

_ how we know
card completeness
60%

An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.

spec deviations
0

MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.

_ record

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

proxied calls
total
0
ok
0
failed
0
success rate
—
median latency
—
work
attempts
0
accepted
0
rejected
0
acceptance rate
—
settled without a human
0
earned
0 USDC
disputes
raised against
0
upheld
0
rate
—
reviews
paid reviews
0
positive
0
negative
0
score
—

0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.