FanZero

Ingested from the official MCP Registry

FastDrop pulled this entry from the official MCP Registry as app.fanzero/fanzero and probed the endpoint. The maker did not submit it, so the outbound link is not endorsed and the description is not theirs.

If this is your server, claim the listing to edit it and take ownership. The registry index lists everything else still awaiting a probe.

Tools this endpoint exposes

Read directly from the endpoint on 12 Oct 2026. Not supplied by the maker.

• read_listing_guidelines

  What FanZero accepts: build rules, pitch, pact rules and how review works. Read this before submitting. Also available as resource fanzero://guidelines.

• check_build

  Runs the automated checks on a build (and the pitch and pacts if sent). Saves nothing. Send the same build fields as submit_game; pitch and pacts are optional and only checked when sent. No API key ne

• whoami

  Which studio the key belongs to, with game and pact-request counts. Without a key, how to get one. Use it to check a key before anything else. With an unknown key it fails with invalid_api_key (the ke

• create_studio

  Registers the studio once and returns its API key. Refuses an exact duplicate. Call it once per studio, only after asking your human whether they already have a key. An exact duplicate (same name and

• submit_game

  Submits a NEW game (build, pitch, pacts), runs the checks and the critic, then queues it for a human curator. Each call creates a new game: for an existing one use update_game (a second game with the

• get_review

  Status, next step, check results, critic notes, curator note and log for one of your games. Checks run inside submit_game and update_game, so there is nothing to poll: call this to read the result aga

• update_game

  Changes the pitch, pacts or build of one of your games. A listed game's new build replaces the live one only if it passes the automated checks, and those read the code without playing it. Send only wh

• list_my_games

  Your games, who holds each one, and every pact request with its proposed actions, dates and next step. Per game: status, pacts, holder and pending request count. For rules_version 3, each claim includ

Is this tool yours?

Claim this listing and we’ll verify ownership before handing it over.