MCP server for the Codabench REST API — drives a full ML-benchmark participant workflow.
MCP server for the Codabench REST API. Lets an AI agent drive a full participant ML-benchmark workflow: discover competitions, read rules, download data, submit, poll, read leaderboards. Curated tools for the participant path: (streaming + SHA-256) (handles Codabench's 3-step upload flow) (backoff + timeout + non-error "stillrunning") — generic REST escape hatch (GET-only by default) You need a…
Inferred from the transports this listing declares (stdio). A client not listed here hasn’t been ruled out — it just isn’t something Forge can confirm.
Verification confirms publisher identity (repo ownership), not code safety. The security scan covers known CVEs and suspicious install scripts.
Forge read 0 source files from the published package tarball and matched no MCP tool registrations. Extraction is pattern-based over shipped source: a server that builds its tool list at runtime, or that ships only bundled or minified code, registers nothing this can see. Treat it as “not detected”, not as “exposes none”.
MCP server for the Codabench REST API. Lets an AI agent drive a full participant ML-benchmark workflow: discover competitions, read rules, download data, submit, poll, read leaderboards. Curated tools for the participant path: (streaming + SHA-256) (handles Codabench's 3-step upload flow) (backoff + timeout + non-error "still_running") — generic REST escape hatch (GET-only by default) You need a Codabench API token. Two ways to get one: 2. Find the endpoint → Try it out 3. POST your…
Forge's dependency resolver reads npm metadata only, so this PyPI package has no resolved tree. That is a gap in coverage, not a clean bill of health.