← fanzero.app

INDIVIDUAL MCP TOOL

confirm_delivery

Legacy contracts only: confirms proof under the older go-live rules.

fanzero.appnone authenticationAvailability not checked

LIVE ENDPOINT

https://fanzero.app/mcp

No auth detected

Connect to this endpoint to inspect the live schema for confirm_delivery and invoke it with your own arguments.

Indexed input schema

{}

Risk classification

Inferred read-only · medium confidence · heuristic, not a guarantee.

  • No write-capable action terms were found; this is not proof that invocation has no side effects.

Parent server

fanzero.app

CONNECT WITH APPROVAL

Client installation

Review this server and its permissions before adding it. Secret placeholders must be set locally.

Codex

~/.codex/config.toml

[mcp_servers.fanzero]
url = "https://fanzero.app/mcp"
enabled = true
Claude Code

.mcp.json

{
  "mcpServers": {
    "fanzero": {
      "type": "http",
      "url": "https://fanzero.app/mcp"
    }
  }
}
Claude Desktop

Settings → Connectors → Add custom connector

Name: fanzero
Remote MCP URL: https://fanzero.app/mcp

Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.

Cursor

.cursor/mcp.json

{
  "mcpServers": {
    "fanzero": {
      "url": "https://fanzero.app/mcp"
    }
  }
}
Visual Studio Code

.vscode/mcp.json

Add to Visual Studio Code
{
  "servers": {
    "fanzero": {
      "type": "http",
      "url": "https://fanzero.app/mcp"
    }
  }
}
Generic MCP

Client-specific MCP configuration

{
  "name": "fanzero",
  "transport": "streamable-http",
  "url": "https://fanzero.app/mcp"
}
MCP Inspector

Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.

Related tools

  • read_listing_guidelines — What FanZero accepts: build rules, pitch, pact rules and how review works.
  • check_build — Runs the automated checks on a build (and the pitch and pacts if sent).
  • whoami — Which studio the key belongs to, with game and pact-request counts.
  • create_studio — Registers the studio once and returns its API key.
  • submit_game — Submits a NEW game (build, pitch, pacts), runs the checks and the critic, then queues it for a human curator.
  • get_review — Status, next step, check results, critic notes, curator note and log for one of your games.
  • update_game — Changes the pitch, pacts or build of one of your games.
  • list_my_games — Your games, who holds each one, and every pact request with its proposed actions, dates and next step.