Supabase
Supabase’s official server lets AI create tables, query data and review project settings in your Supabase database.
Description from the maker (original English)
Crowdsourced Arknights drop rates by stage and item, for the CN, US, JP and KR game servers
These three are never merged into one score: opinions, measurements and popularity are different things.
We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.
Pick the AI app you use, then copy the settings.
You need
Which app do you use?
Pick your app above. We remember it, so next time the button says “Install in …”.
Works in Claude on the web, desktop and mobile:
https://mcp.penguin-stats.io/mcpRun this in your terminal
claude mcp add --transport http penguin-stats https://mcp.penguin-stats.io/mcpPaste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"penguin-stats": {
"url": "https://mcp.penguin-stats.io/mcp"
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
Paste into .vscode/mcp.json in your project
{
"servers": {
"penguin-stats": {
"type": "http",
"url": "https://mcp.penguin-stats.io/mcp"
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
ChatGPT connects only to servers on the internet:
https://mcp.penguin-stats.io/mcpMenu names can differ slightly by plan and over time.
Your choice stays on this device in a cookie; no account needed.
These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.
Tool names and descriptions exactly as the server reported them on Nov 7, 2026. The maker wrote them, not us; we show them as plain text.
get_dataset_infoDescribes 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 cit
get_item_drop_ratesWhere 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
get_stage_dropsWhat 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
list_eventsLists 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
search_itemsFinds 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 it
search_stagesFinds 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 zo
We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 9, 2026
The publisher (penguin-stats.io) is not the repo owner (penguin-statistics); someone else may have listed it
We have not read this repo from GitHub yet
We have not read this repo from GitHub yet
Responded in 503 ms (HTTP 200)
No sign-in needed
Read 6 tool descriptions and found no hidden instructions to the AI
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
It passed 2 of 3 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.
The registry does not list a required key, though some servers ask you to sign in on first use.
It runs in the maker’s cloud. Connect over the internet with nothing to install, but what you send passes through the maker’s servers.
The GitHub repo last changed –, and the latest version (1.0.0) reached the registry 17 days ago.
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. It connects by URL, so apps that accept remote MCP servers work too, such as ChatGPT in developer mode.
In the same category: Supabase, MongoDB MCP Server, Elasticsearch MCP Server
Servers in the same category from other makers, sorted by stars.
Reading a card:↓ Downloads per weeki★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi
Supabase’s official server lets AI create tables, query data and review project settings in your Supabase database.
Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.
The re-designed Penguin Statistics v3 Backend, built with Go.
The drop data is public:
https://penguin-stats.io/PenguinStats/api/v2/: see the developer docs and the OpenAPI (Swagger 2.0) spec.https://mcp.penguin-stats.io/mcp: Streamable HTTP, no authentication, read-only. In Claude Code: claude mcp add --transport http --scope user penguin-stats https://mcp.penguin-stats.io/mcp
The steps for every other app, in English and Chinese, are at https://mcp.penguin-stats.io/.
The drop data is licensed CC BY-NC 4.0: non-commercial use, with credit. Credit it as Data: Penguin Statistics (penguin-stats.io), CC BY-NC 4.0. The code of this repository is MIT.
This Go project mainly uses:
This project mainly follows a RESTful API design.
The report worker moves a report task out of the penguin-reports stream into penguin-reports-dead (subjects REPORT_DEAD.*) when it can never be processed (it is not a task, or a stage of it does not exist) or when it failed at each of its 30 deliveries, which take about 97 minutes of retry delays. Each move is logged at error level (reportwkr.malformed, reportwkr.parked or reportwkr.dead). The copy keeps the payload as published, with these headers:
Penguin-Original-Subject: the subject it was published under, like REPORT.SINGLEPenguin-Original-Sequence: its sequence in penguin-reportsPenguin-Deliveries: its deliveries when it movedPenguin-Last-Error: the error that moved itA task too close to the maximum payload to fit with these headers moves without them, and its subject under REPORT_DEAD.* names its original subject; its move is logged as reportwkr.dead.bare, with the sequence and the error.
Nothing in the stream expires. With the nats CLI, once the cause is fixed:
# list the tasks, with their headers
nats stream view penguin-reports-dead
nats stream get penguin-reports-dead 42
nats stream get penguin-reports-dead 42 --json | jq -r .data | base64 -d \ | nats pub REPORT.SINGLE --force-stdin
nats stream rmm penguin-reports-dead 42 -f
A task that moved after failing at each delivery may have been stored by one of them whose commit outcome was unknown (for example the connection dropped during the commit); check drop_reports for its account and time before replaying it.
internal/workers/reportwkr/consumerbench_test.go (build tag consumerbench) drives the report consumer through its real code path: each task is published to a JetStream stream of its own, fetched and handed to Worker.ingestPreprocess (BenchmarkConsumer/ingest), which stores it in PostgreSQL and sets its recall key in Redis, with logging and tracing configured as in production. BenchmarkConsumer/process runs Worker.process alone. Besides wall time and allocations it reports, per task, the CPU time of the process (cpu-ns/op, user + system from getrusage, which a shared machine disturbs far less than the wall time) and the time spent waiting on PostgreSQL (pg-wait-ns/op, pg-wait-%) and Redis.
The tasks (internal/workers/reportwkr/testdata/consumerbench/tasks.jsonl.gz) are encoded as the report handler publishes them, drawn from the stages, servers, times, sources, versions and drop patterns of recent production reports, with synthetic accounts, IPs and task ids.
It needs a scratch database, Redis and NATS with JetStream. The scratch database holds the schema and the reference tables of a restore of production (penguinprod, only read) and synthetic accounts; the benchmark truncates its drop_reports and drop_report_extras:
scripts/consumerbench/setup-db.sh # creates penguin_cpubench and the role cpubench on 127.0.0.1:5434
CONSUMERBENCH_GENERATE=1 go test -tags consumerbench -run TestConsumerBenchGenerate ./internal/workers/reportwkr/
The defaults point at penguin_cpubench on 127.0.0.1:5434, Redis DB 14 on 127.0.0.1:16379 and NATS on 127.0.0.1:4222 (CONSUMERBENCH_POSTGRES_DSN, CONSUMERBENCH_REDIS_URL, CONSUMERBENCH_NATS_URL). Then:
# one run
go test -tags consumerbench -run '^$' -bench BenchmarkConsumer -benchtime 2000x ./internal/workers/reportwkr/
COUNT=10 scripts/consumerbench/run.sh bench prod logoff traceoff off devnull trace1
scripts/consumerbench/run.sh profile prod
Outputs go to $OUT (default a new temporary directory). Each run logs the load average and the queries other sessions had active on the cluster to $OUT/runs.log. The PostgreSQL connection runs over loopback, where a write system call also does the receiving side's TCP work, so the system calls weigh more than against a remote server.
This project has mainly being maintained by the following contributors (in alphabetical order):
The full list of active contributors of the _Penguin Statistics_ project can be found at the Team Members page of the website.
This project is made possible by the following contributors. Contributions are always welcome!