FanZero

What you can do with it

We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.

• Connection: Runs in the cloud
• Transport: Streamable HTTP
• Category: Games, sports, food & learning
• You need to fill in: Authorization

Install

Pick the AI app you use, then copy the settings.

You need

• Runs in the cloudNothing to install; it connects over the internet

Which app do you use?

claude mcp add --transport http fanzero https://fanzero.app/mcp --header 'Authorization: Bearer {api_key}'

{
  "mcpServers": {
    "fanzero": {
      "url": "https://fanzero.app/mcp",
      "headers": {
        "Authorization": "Bearer {api_key}"
      }
    }
  }
}

{
  "servers": {
    "fanzero": {
      "type": "http",
      "url": "https://fanzero.app/mcp",
      "headers": {
        "Authorization": "Bearer {api_key}"
      }
    }
  }
}

Your choice stays on this device in a cookie; no account needed.

Values you fill in

• Authorization secret HTTP header
  Studio API key. Public tools and publish_game with an authorized new studio do not need an existing key.

These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.

What it can do

Tool names and descriptions exactly as the server reported them on Nov 8, 2026. The maker wrote them, not us; we show them as plain text.

• 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/f

• 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

• 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 retries never expose credentials. One-operation flow for the original game: complete media, platform links, per-platfor

• 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 w

• 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)

• 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 read the code without playing it. Original game links remain the default. remove_preview:true retires an optional demo, ke

• 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 ac

• add_pact

  Offers one more revenue-share pact on one of your games. Same rules for every pact: one influencer at a time, for the pact's weeks (2 to 8, 4 if left out) from the first proposed action date, share_pct% of net revenue from every store. Get the terms, length included, from your hu

• 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 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 influencer action plan once. For rules_version 3, sharing runs for the pact's weeks from the earliest proposed action, never from approval; late approval keeps the same

• 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 (othe

• 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 per key in claim.distribution with the net revenue that platform pays or will pay for the window's sales, in-game purchase

• 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 window ends (each pact runs its own weeks; for a legacy holder who has not gone live

Basic checksi

We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 8, 2026

• ! Caution

  Maker matches the repo

  The registry lists no source repo, so we cannot match the publisher (fanzero.app) to the code

• … Not checked yet

  Still maintained

  We have not read this repo from GitHub yet

• … Not checked yet

  Has a licence

  We have not read this repo from GitHub yet

• ✓ Pass

  Endpoint responds

  Responded in 387 ms (HTTP 200)

• – Not applicable

  Sign-in with OAuth

  No sign-in needed

• ✓ Pass

  No hidden instructions in tool descriptions

  Read 15 tool descriptions and found no hidden instructions to the AI

Compared with others in Games, sports, food & learningi

• More stars than 0% of the other 1291 servers in this category
• Published to the registry more recently than 54% of the other 1291 servers in this category
• Basic checks equal to or better than 47% of the other 1291 servers in this category

Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.

Alternatives

Servers in the same category from other makers, sorted by stars.

Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi

README from the maker

No README found in the repo