bench-registry
This server does not currently have a deployable release on Glama. Follow the repository's setup instructions to install and configure it for your MCP client, including any required credentials and local dependencies.
bench-registry
One process, one port, one SQLite file: an MCP server + REST API + zero-build web UI for logging training / benchmark / eval runs and querying leaderboards across machines.
Built for the pattern of "agent fleet runs benchmarks on several hosts, results scattered across logs" — every agent (or curl) appends a run with free-form metrics/config JSON, and anyone can ask "what was the best tokens/sec on any GPU for model X?" and get a ranked answer.
Reproduce in 3 commands
python3 -m venv .venv && .venv/bin/pip install -r requirements.txt
.venv/bin/python server.py & # UI on http://127.0.0.1:8100/ , MCP on /mcp
.venv/bin/python selftest.py # raw JSON-RPC end-to-end test, no LLM neededselftest.py prints PASS for initialize → tools/list → add → list →
leaderboard → get → delete and cleans up after itself. Linux smoke-tested.
Related MCP server: metrillm-mcp
What you get
Surface | Where |
Web UI (runs table + metric leaderboard picker) |
|
REST |
|
MCP (streamable HTTP) |
|
MCP tools
bench_run_add(project, model, hardware, metrics, run_type, config, notes, status)— log a run;metrics/configare free-form JSON objectsbench_run_list(project?, model?, hardware?, run_type?, limit?)— newest firstbench_run_get(run_id)/bench_run_delete(run_id)bench_leaderboard(metric, project?, hardware?, model?, higher_is_better?, limit?)— rank runs by any numeric metricbench_summary()— counts per project/model/hardware + every numeric metric key that exists
Registering with an MCP client
Point any streamable-HTTP MCP client at http://127.0.0.1:8100/mcp.
For Hermes:
hermes config set mcp_servers.bench-registry.url http://127.0.0.1:8100/mcp(takes effect in new sessions)
Data model
Single runs table in runs.db (override with BENCH_REGISTRY_DB):
id, created, project, run_type, model, hardware, status, config(json), metrics(json), notes.
Port override: BENCH_REGISTRY_PORT (default 8100). No telemetry, no auth —
keep it on localhost/LAN like any other local tool.
Why
Benchmark results across a fleet usually die in per-machine log files. This makes them a first-class queryable dataset that every agent on the network can write to and read from through its normal tool loop — and a human can eyeball in a browser.
License
MIT
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
This server cannot be deployed
Maintenance
Related MCP Connectors
Remote MCP for Gemini upgrade evals, prompt regressions, output diffs, and eval receipts.
MCP server providing access to the Scorecard API to evaluate and optimize LLM systems.
A paid remote MCP for AI SDK benchmark dashboard, built to return verdicts, receipts, usage logs, an
Hosted MCP messaging across owners, tools, and machines, with readable transcripts.
Related MCP Servers
AlicenseNot gradedqualityDmaintenanceEnables running LLM evaluations, experiments, and custom evaluators through a standardized MCP interface.16Apache 2.0- AlicenseNot gradedqualityDmaintenanceEnables benchmarking of local LLM models (performance and quality) and sharing results to a public leaderboard via MCP tools.19 npm8Apache 2.0
- AlicenseNot gradedqualityBmaintenanceEnables AI agents to register, submit signed scores, and query leaderboards and profiles on the FloweringAgents performance registry via MCP tools.MIT
- AlicenseNot gradedqualityBmaintenanceEnables external agents to monitor and control ML training runs via 35 MCP tools. Covers training status, checkpoints, experiments, recovery, and dashboard configuration.2MIT