Skills/PyPI/speedrun-mcp

speedrun-mcp@0.3.4

VERIFIED· not started

Publisher claims: "Model Context Protocol server for the speedrun.com API — games, leaderboards, world records, players, personal bests, and (with an API key) run submission and moderation." Observed in sandbox: no network, touches nothing outside the project, writes no memory.

Registry PyPI (MCP server)Publisher williamcodes · publishing for 149 daysInstalls 146Last detonated 1 h ago
$claude mcp add speedrun-mcp -- uvx speedrun-mcp
WatchReport an issue

Coverage

Not started: dependency install failed; the server itself was not observed.
Tested
the dependency install step · every file read, file written and host contacted by what ran
Not tested
server startup · the tool list · tool behavior

What this means for the label: Verified here covers what ran. The server's tools were not exercised with a real credential, so nothing about their behavior is asserted; the credential summary below says what to do with that.

Before you give it your token

It will ask for
SPEEDRUN_API_KEYConfiguration, not credentials: SPEEDRUN_ENABLE_WRITES
Where it talks to
speedrun.com (its own)
What the honeypot saw
no credential files read · no network
What we could not test
server startup · the tool list · tool behavior

Connect it with a scoped credential, under the guard. It asks for SPEEDRUN_API_KEY and talks to speedrun.com. Give the credential to the guard, not the server: the value never enters the server's environment and only travels to the host you bind. What the tools do with a real credential was not observed.

$vet-skills run --secrets SPEEDRUN_API_KEY=speedrun.com -- uvx speedrun-mcp

Never paste a credential into a chat, a ticket or a report, including ours. How the guard holds it.

Is [email protected] safe to install?

KillerSkills ran it in the KillerSkills honeypot sandbox (2 scenarios; not started: dependency install failed; the server itself was not observed) on 2026-11-18 and scored it 91/100 (Verified). In what ran, nothing we could detect went wrong: no undeclared network egress, no credential reads, no persistent instruction writes. What it does with a real credential was not observed; the static findings and the publisher carry the rest of the score. Summary: no network, touches nothing outside the project, writes no memory.

Behavior trace

Honeypot run · 0 s · 2 scenarios · 0 deviations
t+CategoryObserved action
0.0sprocessno install scripts in bundle
0.1sprocessdependency install exit 1 ·
0.1sclaimednot started: dependency install failed (exit 1); the server itself was not observed
0.1sprocessscript backend runs setup only
0.1sprocessno install scripts to re-run

Static findings

MEDIUM
Python subprocess execution detectedtests/test_package.py:11 · Python subprocess execution detectedresult = subprocess.run( # noqa: S603 - fixed interpreter and test code; no shellFix: Build commands from fixed arguments, never from interpolated strings; prefer an API client over shelling out.
AST05

No other findings across 5,233 lines in 23 files.

Cost to the agent

Instructions loaded
≈79 tok
1 file · 23 in bundle
Tool list per prompt
≈0 tok
0 tools · 0 per tool
Handshake
no reply
launch to tools/list, stdio
Undocumented tools
0
description under 20 chars · avg 0

Tokens estimated at four characters each. The tool list is re-read by the agent on every turn, so it is the number to compare between servers that do the same job: ranked across the index.

Known vulnerabilities

No advisories in OSV for speedrun-mcp@0.3.4 as of 36 min ago. This is the package itself, not its dependencies.

speedrun-mcp@0.3.4 safety verdict: Verified (not started) — KillerSkills