# Fanzero MCP server

Source: https://glimind.com/server/mcp-registry%2Fapp.fanzero%2Ffanzero
Registry id: `mcp-registry/app.fanzero/fanzero`
Status: live (checked 2026-10-26T18:13:36.730Z)

## Measurements (30 days)

- Uptime: 100%
- Checks: 2934
- Outages (90 days): 0

## Install

```json
{
  "mcpServers": {
    "fanzero-mcp-server": {
      "type": "http",
      "url": "https://fanzero.app/mcp"
    }
  }
}
```

Claude Code:

```sh
claude mcp add --transport http fanzero-mcp-server https://fanzero.app/mcp
```

## Tools (15)

- `add_pact`: Offers one more revenue-share pact on one of your games. Same rules for every pact: one influencer at a time, 4 weeks from the first proposed action date, share
- `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
- `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 lin
- `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 influencers ca
- `confirm_delivery`: Legacy contracts only: confirms proof under the older go-live rules. Scheduled pacts need no delivery confirmation. Legacy contracts only. Scheduled pacts (rule
- `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
- `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 t
- `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
- `publish_game`: Publish the original game through media and platform links in one operation. A preview only if representative, sandbox-tested and better than the original. Safe
- `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 defau
- `respond_to_claim`: Approves or declines a proposed action schedule. Legacy proof responses remain supported. accept: approves the influencer action plan once. For rules_version 3,
- `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 submiss
- `submit_settlement`: After a pact window: declares each platform's net revenue, with its own report. The influencer accepts or disputes. After a scheduled pact's window: one line pe
- `update_game`: Change the listing or offers; remove_preview retires a demo, keeping the original links and pact windows. Agent uploads need preview_review. Automated checks re
- `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 

Measured by Glimind (https://glimind.com): MCP handshake + tool list only, no tool is ever called. CC BY 4.0.