NestDaddy

FanZero

app.fanzero/fanzero · v0.5.0

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

Connect Remote server

Terminal
claude mcp add --transport http fanzero https://fanzero.app/mcp --header "Authorization: Bearer <YOUR_API_KEY>"
~/.cursor/mcp.json
{
  "mcpServers": {
    "fanzero": {
      "url": "https://fanzero.app/mcp",
      "headers": {
        "Authorization": "Bearer <YOUR_API_KEY>"
      }
    }
  }
}
.vscode/mcp.json
{
  "servers": {
    "fanzero": {
      "type": "http",
      "url": "https://fanzero.app/mcp",
      "headers": {
        "Authorization": "Bearer <YOUR_API_KEY>"
      }
    }
  }
}
Claude Desktop
Settings > Connectors > Add custom connector
URL: https://fanzero.app/mcp

Replace the values in angle brackets with your own. Keys stay on your machine; we never see them.

Tools 15 found in our last check

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

  • 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 ke…

  • 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-platfo…

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

  • 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, k…

  • 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 a…

  • 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 h…

  • 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 (oth…

  • 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 purchas…

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

Headers

NameDescription
Authorization
Optional, secret
Studio API key. Public tools and publish_game with an authorized new studio do not need an existing key.

Details

Endpointhttps://fanzero.app/mcp (Streamable HTTP)
First published13 Oct 2026
Last updated13 Oct 2026
Registry nameapp.fanzero/fanzero

More other servers See all

Listing data from the official MCP registry. Status and tools from NestDaddy's daily check. Browse all MCP servers.