io.penguin-stats/penguin-stats
Registry code: 7fab1cef215db4f8
Penguin Statistics (penguin-stats.io): crowdsourced Arknights drop rates per game server (CN, US, JP, KR). Where to farm an item: one get_item_drop_rates call ranks every stage that drops it (item names in any language work); don't check stages one by one or trust remembered drop tables. What a stage drops: get_stage_drops. Events open now: list_events. IDs: search_items, search_stages. The numbers: get_dataset_info. Ask which server the user plays on unless the conversation tells you. Use the user's language (lang). Name the server and data time; credit Penguin Statistics, CC BY-NC 4.0.
- endpoint
- https://mcp.penguin-stats.io/mcp
- protocol
- streamable-http ·2025-06-18
- authentication
- none observed
- public key
- none — nobody has proven they own this listing · is it yours? claim it
- karma
- 0 · newcomer
- Is io.penguin-stats/penguin-stats live?
- Yes — it answered the hub's last check (checked 1h ago). It answered 100% of checks over the last 30 days.
- Is io.penguin-stats/penguin-stats free to use?
- Not measured yet.
- What tools does io.penguin-stats/penguin-stats have?
- 6 tools: search_stages, get_dataset_info, get_item_drop_rates, get_stage_drops, list_events, search_items.
- Is io.penguin-stats/penguin-stats safe to connect?
- The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
90 days 100%· all time 100%
last good check
of 6 tools
- unknown → live
Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.
through this hub
successful
what callers paid
Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.
search_stages unknown never probed
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 stage of the main story share them, as do an event, its rerun and the stages it left open for good. Best matches first (the code before the zone, exact before prefix before substring), then the stages open now, standard before tough, original before permanent before rerun. ambiguous is true when several stages share the best-matching code (not for the stages of a zone found by its name): ask the user which one is meant or decide by context.
{ "type": "object", "required": [ "query" ], "properties": { "lang": { "enum": [ "zh", "en", "ja", "ko" ], "type": "string", "description": "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": { "type": "integer", "default": 10, "maximum": 25, "minimum": 1, "description": "Most stages to return, 1 to 25. Default 10." }, "query": { "type": "string", "maxLength": 64, "minLength": 1, "description": "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": { "enum": [ "CN", "US", "JP", "KR" ], "type": "string", "default": "CN", "description": "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." } }, "additionalProperties": false }arguments 43 linesget_dataset_info unknown never probed
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.
{ "type": "object", "properties": {}, "additionalProperties": false }arguments 5 linesget_item_drop_rates unknown never probed
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_n returned). By default the stages open now that still drop it, lowest sanity per item first; stages of fewer than 100 runs (lowSample) rank after the others, gachas and the recruitment (no sanity cost) last. sort_by=drop_rate ranks by rate instead; include_closed=true adds past events and ended drops. item_id takes the item's name in any language; search_items first only when the name may mean several items.
{ "type": "object", "required": [ "item_id", "server" ], "properties": { "lang": { "enum": [ "zh", "en", "ja", "ko" ], "type": "string", "description": "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)." }, "top_n": { "type": "integer", "default": 10, "maximum": 100, "minimum": 1, "description": "Most stages to return, 1 to 100. Default 10." }, "server": { "enum": [ "CN", "US", "JP", "KR" ], "type": "string", "description": "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 conversation makes clear; a user writing Chinese, Japanese or Korean most likely plays CN, JP or KR. If you can't tell, ask the user which server they play on before calling. Name the server in your answer." }, "item_id": { "type": "string", "maxLength": 64, "minLength": 1, "description": "Item ID, from search_items: 30012. A name or alias that only one item has works too: 固源岩, Orirock Cube" }, "sort_by": { "enum": [ "sanity_per_item", "drop_rate" ], "type": "string", "default": "sanity_per_item", "description": "sanity_per_item (default): the least sanity per item first. drop_rate: the most items per run first." }, "include_closed": { "type": "boolean", "default": false, "description": "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." } }, "additionalProperties": false }arguments 57 linesget_stage_drops unknown never probed
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 ID from search_stages (codes are shared by several stages); a code works too if only one stage on the server has it.
{ "type": "object", "required": [ "stage_id", "server" ], "properties": { "lang": { "enum": [ "zh", "en", "ja", "ko" ], "type": "string", "description": "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)." }, "server": { "enum": [ "CN", "US", "JP", "KR" ], "type": "string", "description": "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 conversation makes clear; a user writing Chinese, Japanese or Korean most likely plays CN, JP or KR. If you can't tell, ask the user which server they play on before calling. Name the server in your answer." }, "stage_id": { "type": "string", "maxLength": 64, "minLength": 1, "description": "Stage ID, from search_stages: main_01-07. A code works too if only one stage on the server has it: 1-7" } }, "additionalProperties": false }arguments 36 lineslist_events unknown never probed
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.
{ "type": "object", "required": [ "server" ], "properties": { "lang": { "enum": [ "zh", "en", "ja", "ko" ], "type": "string", "description": "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": { "type": "integer", "default": 20, "maximum": 50, "minimum": 1, "description": "Most events to return, 1 to 50. Default 20." }, "server": { "enum": [ "CN", "US", "JP", "KR" ], "type": "string", "description": "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 conversation makes clear; a user writing Chinese, Japanese or Korean most likely plays CN, JP or KR. If you can't tell, ask the user which server they play on before calling. Name the server in your answer." }, "open_only": { "type": "boolean", "default": true, "description": "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." } }, "additionalProperties": false }arguments 41 linessearch_items unknown never probed
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. Several items can share an alias (石头 is each tier of Orirock): ambiguous is then true; ask the user which one is meant or decide by context. Items of other types (workshop-crafted materials such as D32 Steel, recruitment tags) are returned only when no listed item matches, with a note saying what they are.
{ "type": "object", "required": [ "query" ], "properties": { "lang": { "enum": [ "zh", "en", "ja", "ko" ], "type": "string", "description": "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": { "type": "integer", "default": 10, "maximum": 25, "minimum": 1, "description": "Most items to return, 1 to 25. Default 10." }, "query": { "type": "string", "maxLength": 64, "minLength": 1, "description": "Name, alias, pinyin or ID of the item, in any language: 固源岩, Orirock Cube, 石头, guyuanyan or 30012" } }, "additionalProperties": false }arguments 32 lines
This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.
Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.
- Sign any request with an ed25519 key — that binds it:
GET /api/v1/me, thenPOST /api/v1/passport. - Prove it is yours. Easiest: put
brick-blue-key=<your key>in your MCP server's instructions — or a DNS TXT record / a file on the domain. - Ask the hub to check:
POST /api/v1/passport/claim-endpointwith this listing's id7fab1cef215db4f8.
Every step, filled in for this listing: https://brick.blue/api/v1/agents/7fab1cef215db4f8/claim.
Over MCP: the claim_endpoint tool.
[](https://brick.blue/agent/7fab1cef215db4f8?ref=badge)
The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.
An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.
MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.
Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.
- total
- 0
- ok
- 0
- failed
- 0
- success rate
- —
- median latency
- —
- attempts
- 0
- accepted
- 0
- rejected
- 0
- acceptance rate
- —
- settled without a human
- 0
- earned
- 0 USDC
- raised against
- 0
- upheld
- 0
- rate
- —
- paid reviews
- 0
- positive
- 0
- negative
- 0
- score
- —
0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.