MCP server for interacting with the Scryfall MTG API
Nothing to run from here
Penguin Statistics 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.
96/100
tool-list score
6
tools declared
remote
at its publisher
—
calls last 7d
What it does
Crowdsourced Arknights drop rates by stage and item, for the CN, US, JP and KR game servers
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http penguin-statistics-mcp https://mcp.penguin-stats.io/mcp
# 2 — ask your agent for something these tools do
# get_dataset_info, get_item_drop_rates, get_stage_drops and 3 more
Penguin Statistics costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Publishernot claimed
PSAll 1 server
penguin-stats1 server
1 category
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Installation
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. Nothing here runs on your machine and nothing runs on ours: this server answers at its publisher’s own address, and what you install is the connection straight to it.
Claude Codedeclared by this listing
This is a public server: it answers at its publisher’s own address and this marketplace is not in the path. Claude Code registers it in one command; --scope user makes it available in every project. The transport below is http, as the publisher's own manifest declares it.
claude mcp add --scope user --transport http penguin-statistics-mcp https://mcp.penguin-stats.io/mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
Free on mcprush, and it answers at its publisher’s own address: this marketplace is not in the path, so there is no key of ours to hold and no card to add.
What it writes
One config entry pointing straight at the publisher’s own address — this marketplace is not in the path, and nothing from this listing executes on your machine.
What you approve
6 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.
Describes the Penguin Statistics drop data: what its numbers mean (times, quantity, drop rate, sanity per item, window), the game servers with their time zones and how fresh the data of each is, the caveats, the license and how to credit it. Call it when unsure how to read or cite the numbers.
No parameter schema on file.
Where to farm an item: ranks every stage of a game server that drops it, with sanity per item, drop rate (items per run), runs (times) and quantity. Use it for any question about where to get an item, its best or most efficient stage, or which of several stages to run for it: one call ranks every stage, so don't look stages up one by one with get_stage_drops (only a named stage left out of the top
| Parameter | Type | Required | Notes |
|---|---|---|---|
| item_id | string | yes | Item ID, from search_items: 30012. A name or alias that only one item has works too: 固源岩, Orirock Cube |
| server | string | yes | Game server the user plays on: CN (mainland China: 国服, 官服, B服), US (global, English: 国际服, 美服), JP (日服) or KR (韩服). Stages, events and drop rates differ by server. Use the server the user named or the |
| top_n | integer | no | Most stages to return, 1 to 100. Default 10. |
| include_closed | boolean | no | false (default): only the stages open on the server now that still drop the item. true: also the stages of past events and the drops that ended, for history. |
| sort_by | string | no | sanity_per_item (default): the least sanity per item first. drop_rate: the most items per run first. |
| lang | string | no | Language of the names in the result: the language the user writes in, zh, en, ja or ko (en for other languages, and if omitted). |
What one stage drops on a game server: each item with drop rate (items per run), sanity per item, runs (times) and quantity, highest rate first, then the items it no longer drops; with the sanity cost of the stage and whether it is open now. For questions about a given stage. To find where to farm an item, call get_item_drop_rates instead: one call ranks every stage that drops it. Takes the stage
| Parameter | Type | Required | Notes |
|---|---|---|---|
| stage_id | string | yes | Stage ID, from search_stages: main_01-07. A code works too if only one stage on the server has it: 1-7 |
| server | string | yes | Game server the user plays on: CN (mainland China: 国服, 官服, B服), US (global, English: 国际服, 美服), JP (日服) or KR (韩服). Stages, events and drop rates differ by server. Use the server the user named or the |
| lang | string | no | Language of the names in the result: the language the user writes in, zh, en, ja or ko (en for other languages, and if omitted). |
Lists the events (limited-time activities) of a game server: status now (open, upcoming or closed), open and close times, whether a rerun. By default the open and upcoming events with their stage IDs (for get_stage_drops), or the latest 3 if there are none; open_only=false lists every event, latest first, with stage counts only. The main story and the permanent side stories are not events.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| server | string | yes | Game server the user plays on: CN (mainland China: 国服, 官服, B服), US (global, English: 国际服, 美服), JP (日服) or KR (韩服). Stages, events and drop rates differ by server. Use the server the user named or the |
| open_only | boolean | no | true (default): the events open or upcoming on the server, with their stages; if there are none, the latest 3. false: every event of the server, latest first, without their stages. |
| lang | string | no | Language of the names in the result: the language the user writes in, zh, en, ja or ko (en for other languages, and if omitted). |
| limit | integer | no | Most events to return, 1 to 50. Default 20. |
Finds items (materials, battle records, chips, furniture, event items) by name in any language (zh, en, ja, ko), by alias or nickname (土块, 狗粮), by pinyin (guyuanyan) or by item ID, and returns their item IDs (get_item_drop_rates takes a name too; search first when unsure which item is meant) and names in every language. Best matches first: exact before prefix before substring, names before aliases
| Parameter | Type | Required | Notes |
|---|---|---|---|
| query | string | yes | Name, alias, pinyin or ID of the item, in any language: 固源岩, Orirock Cube, 石头, guyuanyan or 30012 |
| lang | string | no | Language of the names in the result: the language the user writes in, zh, en, ja or ko (en for other languages, and if omitted). |
| limit | integer | no | Most items to return, 1 to 25. Default 10. |
Finds stages by code (1-7, S2-12, YW-4; full-width characters work too), by stage ID (main_01-07), or by the name or ID of their zone (第十章, Under Tides), and returns their stage IDs (for get_stage_drops; to find the stages that drop an item, use get_item_drop_rates) with their zone, sanity cost and whether they are open on the server now. Codes are not unique: the standard and tough versions of a
| Parameter | Type | Required | Notes |
|---|---|---|---|
| query | string | yes | Code or ID of the stage, or the name or ID of its zone, in any language: 1-7, S2-12, main_01-07, 第十章 or Under Tides |
| server | string | no | Game server the user plays on: CN (China), US (global, English), JP (Japan) or KR (Korea). Default CN. The stages open there now rank first. |
| lang | string | no | Language of the names in the result: the language the user writes in, zh, en, ja or ko (en for other languages, and if omitted). |
| limit | integer | no | Most stages to return, 1 to 25. Default 10. |
Free
$0 forever
- Every tool — any call limit is its publisher’s, not ours
- No card, and mcprush charges nothing for it
- Runs at its publisher’s own address — this marketplace is not in the path
- 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 Penguin Statistics 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: —
ATool-list grade · score 96 / 100
Release 1.0.0 · scanned 28 Oct 2026
Graded from the tools this server lists, not from its source code.
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 score96
Findings0 threat · 0 capability
Capabilityminimal
Coveragemanifest
Verificationnot in this report
Surface digest0538070d19eb004f3d9183555ad2c4b18a879b5d5eadf53f9e918fcaa2231c0a
Score vectorthreat 100 → client 96
| Term | Level | What it prices | Points |
|---|---|---|---|
| capability-exposure | minimal | capability blast radius (minimal) — client exposure if the model is manipulated | −0 |
| coverage-honesty | manifest | inspection depth (manifest) — how much of the target the scan could see | −4 |
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.
The scan read each tool’s name, description, input schema and annotations exactly as the server listed them the last time it answered us; no code was reviewed. We ask the server again about once a month, and a list that changed is graded again.
Tool surfaceread
Implementation sourcenot available
Package metadatanot available
Live transportnot available
The implementation source was not read — this reflects the declared tool metadata only.
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 |
|---|---|---|
| get_dataset_info | no tags | |
| get_item_drop_rates | no tags | |
| get_stage_drops | no tags | |
| list_events | no tags | |
| search_items | no tags | |
| search_stages | no tags |
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 digest0538070d19eb004f
Scanned2026-10-28
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
This is an address its publisher runs: which release it serves is theirs to choose, so there is nothing here to pin. The history below is for reading; the current release on file is 1.0.0.
1.0.0
undated
latestNo release note was published with this version.
—
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 Penguin Statistics 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.