Run on your hardware.
Three minutes. No account. Point the CLI at your local model server — Ollama, LM Studio, MLX, llama.cpp — and it runs 34 standardized tasks, auto-detects your hardware, and lands your run on the public leaderboard alongside others running the same model on different rigs.
That's the whole command. The CLI probes localhost for your model server, lists the models it's actually serving, asks for an optional leaderboard nickname, auto-detects your hardware, runs, and submits. Scripting it, or running non-interactively? Use explicit flags — every local server keeps its OpenAI-compatible API under /v1:
npx @pipelinescore/cli run \ --provider local --endpoint http://localhost:11434/v1 \ --model llama3.2 --user yourname
Run on your machine
- ✓ No API key, no provider account
- ✓ Zero inference cost
- ✓ Compare hardware (M3 Max vs RTX 4090 vs CPU-only)
- ✓ Reproducible — your tokens, your weights
Bring your own key
- • Anthropic / OpenAI / OpenAI-compatible
- • Your key, your machine, never sent to us (how)
- • Set a spending cap at the provider first
- • Hardware tag = cloud-api
npx @pipelinescore/cli run \ --provider anthropic \ --model claude-opus-4-7
Don't have the CLI? Paste this into any AI.
Works with Claude, ChatGPT, Cursor, Codex, Gemini — anything that can run a shell command. The AI walks you through the benchmark.
Power user? Install the skill or MCP.
If you live in Claude Code, Codex, OpenCode, OpenClaw, Cursor, or any MCP-compatible client, you can install PipelineScore as a tool. Your AI will run benchmarks for you without you ever leaving the editor.
Drop-in markdown
Single SKILL.md file that any AI reads at session start. Works in Claude Code, Codex, OpenCode, OpenClaw, Cursor.
mkdir -p ~/.claude/skills/pipelinescore curl -L https://pipelinescore.ai/skills/\ pipelinescore/SKILL.md \ -o ~/.claude/skills/pipelinescore/SKILL.md
Three structured tools
run_benchmark, get_user_leaderboard, get_user_profile. Stdio transport, npm-installed.
// ~/.claude/settings.json
{
"mcpServers": {
"pipelinescore": {
"command": "npx",
"args": ["@pipelinescore/mcp"]
}
}
}Local servers we've tested
Anything with an OpenAI-compatible /v1/chat/completions endpoint works. These five are the most common:
Frontier providers (cloud)
For when you want to benchmark the labs' flagships. Bring your own key.
What happens when you run it
- 01
Load the bundled test pack
The 34-task pack ships inside the npm package (integrity-checked at install) and is executed locally — the CLI never runs tasks fetched over the network. The backend is only asked whether a newer pack version exists.
- 02
Run your model
Each task is sent to the provider you chose. Inputs, outputs, timings, and token counts are captured locally.
- 03
Score locally, then submit
Grading happens on your machine — code is executed, everything else is exact-match or measured. The server stores and ranks your client-computed score; it never re-scores. No judge model, no API key.
- 04
See your card, share your run
A tier badge, a category breakdown, and a share link (
pipelinescore.ai/s/…) for the run — your browser opens straight to your spot on the board.