MCP server for interacting with the Scryfall MTG API
Nothing to run from here
Scorezilla is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
100/100
trust score
32
downloads a day
local
runs on your machine
597
downloads in 30d
What it does
Scorezilla is a hosted leaderboard API for games. This MCP server lets Claude Code, Cursor or any MCP client do the setup for you. One request creates a game, a leaderboard board and API keys, and returns ready-to-paste SDK code. After that you can ask "what's on my high-scores board?" and get real data.
Getting started: create a free account at dashboard.scorezilla.dev, generate a token, and set it as SCOREZILLA_TOKEN.
Tools (11):Read: list_games, list_boards, get_keys, get_board_top_n, get_sdk_snippetCreate: bootstrap_leaderboard, create_game, create_board, mint_keyUpdate: update_board_config, update_game_config
Plans: the Free plan includes 2 games with 3 boards each. When you reach a limit, the tool error includes a direct upgrade link. Paid plans start at $9/month (scorezilla.dev/pricing).
Safety: creating games, boards and keys is supported, but deleting, archiving and revoking keys can only be done in the dashboard. Start the server with --read-only to turn off all tools that create or change anything.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --env 'SCOREZILLA_TOKEN=${SCOREZILLA_TOKEN}' --transport stdio scorezilla-mcp '--' npx -y @scorezilla/mcp
# 2 — ask your agent for something these tools do
# list_games, list_boards, get_keys and 8 more
It needs SCOREZILLA_TOKEN: this reads it from your environment, so export it first.
Scorezilla costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Publisher
Installation
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. This one runs on your machine: your client starts Scorezilla as a process under your own user, with your files and your network, so the tool surface below is what it can do to your computer rather than to a server somewhere else. Its scan result is on the Security tab — read the surface before you approve it.
Claude Codedeclared by this listing
This is a public server: you run it yourself and this marketplace is not in the path. You need Node.js — the current LTS (24) is the safe choice; npx comes with it. Claude Code registers it in one command; --scope user makes it available in every project. Claude Code reads SCOREZILLA_TOKEN (MCP token for the Scorezilla API. Issue one at https://dashboard.scorezilla.dev/account/tokens. Format: mcp_live_<base62>) from your environment each time it starts the server, so the value stays out of its config: export it in your shell profile (macOS, Linux), or run setx SCOREZILLA_TOKEN … and open a new terminal (Windows). The '--' is in quotes so that PowerShell passes it on.
claude mcp add --scope user --env 'SCOREZILLA_TOKEN=${SCOREZILLA_TOKEN}' --transport stdio scorezilla-mcp '--' npx -y @scorezilla/mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
Free on mcprush, and it runs from its publisher’s own package: this marketplace is not in the path, so there is no key of ours to hold and no card to add.
What it asks of you
It reaches a system of yours, so it needs your own credential rather than the publisher’s: SCOREZILLA_TOKEN — MCP token for the Scorezilla API. Issue one at https://dashboard.scorezilla.dev/account/tokens. Format: mcp_live_<base62>.. You set it in your own client’s config, on your machine — this marketplace never holds it.
What it writes
One config entry your client uses to start the process locally. A local server runs with your file system and your network, which is why it is priced without metering.
What you approve
11 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
List all games owned by the authenticated developer. Returns each game with id, slug, name, and createdAt. Use this first to orient before creating new resources or inspecting an existing game. If the result is an empty list and the developer wants to add a leaderboard, call bootstrap_leaderboard…
No parameter schema on file.
List all leaderboards (boards) under a given game. Each board has its own id, slug, ranking (sortDir: desc = high-score-wins, asc = lowest-time-wins), score kind (integer / duration_ms / float), retention policy, and optional min/max score bounds. Call this to find a board's id before generating a…
| Parameter | Type | Required | Notes |
|---|---|---|---|
| gameId | string | yes | UUID of the game to list boards for (from list_games) |
Get a game's API keys. Returns, per key: kind ('public' | 'secret'), prefix, createdAt, and rotation/revocation timestamps. The PUBLIC key includes its full plaintext (it's safe to embed in client code). The SECRET key's plaintext is ALWAYS null over MCP — only its prefix is shown, for…
| Parameter | Type | Required | Notes |
|---|---|---|---|
| gameId | string | yes | UUID of the game to fetch keys for (from list_games) |
Get the top-ranked entries on a leaderboard. Call this after the developer submits a test score to confirm the integration is wired correctly — they will see their own test entry appear. Also useful for displaying current standings.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| boardId | string | yes | UUID of the board |
| n | integer | no | Number of entries to return (1–100). Defaults to 10. |
Call this whenever the developer asks how to submit a score, initialize the SDK, or integrate a leaderboard into their code — INCLUDING when they want a setup other than the default: anti-cheat (server-validated scores), OAuth player identity, or a non-TypeScript server. Returns a ready-to-paste…
| Parameter | Type | Required | Notes |
|---|---|---|---|
| gameId | string | yes | UUID of the game |
| boardId | string | yes | UUID of the board to target in the snippet |
| Parameter | Type | Required | Notes |
|---|---|---|---|
| gameName | string | yes | Display name of the game (any string) |
| gameSlug | string | yes | URL-safe slug for the game, e.g. "my-racing-game" (2–42 chars, lowercase + hyphens; derive from gameName) |
| boardName | string | yes | Display name of the leaderboard |
| boardSlug | string | yes | URL-safe slug for the board, e.g. "high-scores" (2–42 chars, lowercase + hyphens) |
| sortDir | string | no | "desc" for high-scores-win, "asc" for lowest-time-wins |
| scoreKind | string | no | Score type: integer (default), duration_ms (time trials), or float |
Create a new (empty) game in the developer's account. Use this when they ALREADY have a game (so bootstrap_leaderboard would conflict) or want an additional game — call list_games first to check. Returns the gameId; follow up with create_board to add leaderboards and mint_key for keys. For a…
| Parameter | Type | Required | Notes |
|---|---|---|---|
| name | string | yes | Display name of the game |
| slug | string | yes | URL-safe slug, e.g. "neon-runner" (2–42 chars, lowercase + hyphens; derive from name) |
Add a leaderboard board to an EXISTING game (by gameId — get it from list_games). This is how you add boards to a game that already exists; bootstrap_leaderboard only works for brand-new games. sortDir "desc" = high-scores-win, "asc" = lowest-time-wins. Returns the created board including its id.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| gameId | string | yes | UUID of the game to add the board to (from list_games) |
| name | string | yes | Display name of the leaderboard |
| slug | string | yes | URL-safe slug for the board, e.g. "high-scores" (2–42 chars, lowercase + hyphens) |
| sortDir | string | no | "desc" for high-scores-win, "asc" for lowest-time-wins |
| scoreKind | string | no | Score type: integer (default), duration_ms (time trials), or float |
| retentionPolicy | string | no | How long scores are kept: all (default), top_n (best N — set retentionN), or rolling_30d |
| retentionN | integer | no | Required when retentionPolicy="top_n": how many top scores to retain (1–1,000,000) |
| minScore | number | no | Optional lower bound; scores below are rejected |
| maxScore | number | no | Optional upper bound; scores above are rejected |
Mint a fresh public/secret key pair for an EXISTING game (by gameId). Returns publicKey (pk_ — safe for the browser/widget) and secretKey (sk_ — server-only, shown ONCE; tell the developer to store it now). Use when a game needs keys, or to add another pair. Key revocation/rotation is done in the…
| Parameter | Type | Required | Notes |
|---|---|---|---|
| gameId | string | yes | UUID of the game to mint keys for (from list_games) |
Update a board's scoring config AFTER creation (by gameId + boardId — from list_games / list_boards). PARTIAL: only the fields you pass change. Use it to cap scores for anti-cheat (maxScore), set a floor (minScore), or change retention. A bound can be cleared by passing null. Returns the full…
| Parameter | Type | Required | Notes |
|---|---|---|---|
| gameId | string | yes | UUID of the game (from list_games) |
| boardId | string | yes | UUID of the board to update (from list_boards) |
| minScore | number | no | Lower bound; scores below are rejected. Pass null to clear it. |
| maxScore | number | no | Upper bound; scores above are rejected (the anti-cheat cap). Pass null to clear it. |
| retentionPolicy | string | no | How long scores are kept: all, top_n (set retentionN), or rolling_30d |
| retentionN | integer | no | Top scores to retain when retentionPolicy="top_n" (1–1,000,000); null clears it |
Set a game's allowed-origins allowlist AFTER creation (by gameId — from list_games). Restricts browser score submissions to specific web origins: an exact origin like "https://yourgame.com" or a wildcard host like "*.yourgame.com" (up to 20). Pass an empty array to allow all origins (the default).…
| Parameter | Type | Required | Notes |
|---|---|---|---|
| gameId | string | yes | UUID of the game (from list_games) |
| allowedOrigins | array | yes | — |
Free
$0 forever
- Every tool, no call limit
- No card, and mcprush charges nothing for it
- Source published under MIT
- Runs on your machine — nothing of it reaches our gateway
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install Scorezilla or to call it, at any volume.
Call allowance · this installenforced at the gateway
Monthly allowance, in calls
—
—
Alert at 80% · then the tool returns a normal MCP error
Used this month: —
ATrust score 100 / 100
Release 0.4.2 · scanned 14 Oct 2026
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
Threat score100
Client score100
Findings1 threat · 0 capability
Capabilityminimal
Coveragesource
Verificationsource
Surface digest16e41213f7c2b2de189b81f6145b6bb02ddc5dc0fd891495a550e7891d9c4716
Score vectorthreat 100 → client 100
| Term | Level | What it prices | Points |
|---|---|---|---|
| capability-exposure | minimal | capability blast radius (minimal) — client exposure if the model is manipulated | −0 |
| verification-discount | source | publisher verification (provenance) — cryptographic build provenance ties the artifact to its source | −0 |
| coverage-honesty | source | inspection depth (source) — how much of the target the scan could see | −0 |
score = clamp(round(threatScore − E_cap − E_ver − E_cov), 0, 100). No model, no opinion, no network call at scoring time: the same methodology version against the same bytes always produces this number, and every line above is a field of the report rather than a summary of it.
What the scan could actually read
A grade is only as meaningful as its coverage, so the scanner publishes its own depth before it publishes its result.
Tool surfacenot available
Implementation sourceread
Package metadataread
Live transportnot available
No tools were enumerated, so prompt-injection, capability and toxic-flow analysis had no tool surface to inspect. To grade a package’s real runtime tools, scan the running server: --command "npx -y <package>".
Capability — what it could do if the model were manipulated
Tags derived from each tool’s schema and the implementation, not from what the tool calls itself. minimal is the level these add up to.
| Tool | Capability tags | Why the tag was assigned |
|---|---|---|
| No per-tool rows for this release — see the note below. | ||
No tool surface was enumerated, so there is nothing to attribute a capability to.
Toxic-flow graph
The lethal trifecta, checked as a graph rather than as a checklist: untrusted input, a sensitive source and an external sink have to meet before there is a path worth worrying about.
The public result for this release does not print the flow graph, so there is nothing to show here. That is not the same as "no paths were found": what the scan did read is above, under coverage.
Supply chain and provenance
Integrityfirst-seen
Surface digest16e41213f7c2b2de
Scanned2026-10-14
This is the first scan of this surface here, so there is nothing yet to compare it against.
Every result on this tab comes from one deterministic pass over the published package — offline, rule by rule, and auditable line by line above. Same methodology version, same bytes, same score.
Release history
Always latest — the install command names no version, so it installs the newest release when it runs; the current release on file is 0.4.2. Pin a release below and the command asks for exactly that one.
0.4.2
10 Oct 2026
latestNo release note was published with this version.
0.4.0
undated
- The version this listing was on when mcprush began following its releases. The registry was not asked when it shipped, so this row carries no date.
—
no reviews yet
Who can review
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Sign in to write one
Any signed-in account that does not publish Scorezilla can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
No reviews yet
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.