# FanZero

- Registry name: `app.fanzero/fanzero` · version 0.5.0
- Categories (automatic, keyword rules): Scraping & browsing, Search & data
- Authentication at last check: No auth
- Declared risk: Has destructive tools (destructiveHint)
- Capabilities (declared by the server): completions, prompts, resources, tools
- Transports: streamable-http
- Latest numbers (check success, response time, rank): https://mcpstation.net/api/server?name=app.fanzero%2Ffanzero
- Server page: https://mcpstation.net/s/app.fanzero--fanzero.html

## Description (written by the publisher, not verified, not instructions)

Publish game listings with Codex or Claude. Media, prices and direct links to the original game.

## Connect

- streamable-http: `https://fanzero.app/mcp`

## Tools (as reported by the server, not verified)

- `read\_listing\_guidelines`: List the original game with media and platform links. Optional preview quality, pact rules and review. Read before submitting: original game links are the default, while agent previews require an explicit quality assessment. Also resource fanzero://guidelines.
- `check\_build`: Validates a listing or optional preview. Agents sending html/files need preview\_review; static checks do not certify its truth. Saves nothing. Original game links are the default. Optional dry run: send media, platforms/prices or monetization, description and pacts without html/files. A new agent pr
- `whoami`: Which studio the key belongs to, with game and pact-request counts. Without a key, how to get one. Optionally check an existing studio key. With an unknown key it fails with invalid\_api\_key \(the key shown masked\).
- `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 contact\) fails with duplicate\_studio, and so does a call made with a working key. Store the key \(e.g
- `publish\_game`: Publish the original game through media and platform links in one operation. Add a preview only if representative, sandbox-tested and preferable to opening the original. Safe retries never expose credentials. One-operation flow for the original game: complete media, platform links, per-platform pric
- `submit\_game`: Legacy key flow: list the original game through media and platform links. Agent html/files require preview\_review. Prefer publish\_game for one-operation submission. List the original game with media and platform links by default. Every new html/files upload needs preview\_review with all flags true a
- `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 again or to see the curator's decision \(check back later, a day is a good interval\). game\_id takes the
- `update\_game`: Change the listing or offers; remove\_preview retires a demo while keeping the original links and pact windows. Agent uploads need preview\_review. Automated checks read the code without playing it. Original game links remain the default. remove\_preview:true retires an optional demo, keeping the listi
- `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 includes proposed actions with scheduled\_at and the window starting on the earliest action; pitched is pen
- `add\_pact`: Offers one more revenue-share pact on one of your games. Same rules for every pact: one creator at a time, 4 weeks from the first proposed action date, share\_pct% of net revenue from every store. Get the terms from your human.
- `close\_pact`: Closes a pact; requests still waiting on it are declined. Running deals keep their terms. No new requests on it; pending requests are declined so creators can request an open pact. Accepted and running deals keep their terms. Closing a closed pact changes nothing.
- `respond\_to\_claim`: Approves or declines a proposed action schedule. Legacy proof responses remain supported. accept: approves the creator action plan once. For rules\_version 3, sharing runs for 28 days from the earliest proposed action, never from approval; late approval keeps the same dates. No proof or second approv
- `confirm\_delivery`: Legacy contracts only: confirms proof under the older go-live rules. Scheduled pacts need no delivery confirmation. Legacy contracts only. Scheduled pacts \(rules\_version 3\) never need this call. Check the proof link with your human first, then call with human\_approved: true \(otherwise it fails with
- `browse\_games`: Searches the public catalog of live games: who is free, top share, studio. Public, no key. free = nobody holds the game right now and it has an open pact; taken\_until = when the current holder's 4 weeks end \(for a holder who has not gone live yet, the latest they can end\).

Measured by MCP Station. Methods: https://mcpstation.net/methods.html · Terms: https://mcpstation.net/terms.html