@mhdd_24/ai-benchmark-mcp
Related Servers
Alternatives to @mhdd_24/ai-benchmark-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityDmaintenanceEnables benchmarking of local LLM models (performance and quality) and sharing results to a public leaderboard via MCP tools.16 npm8Apache 2.0
- AlicenseNot gradedqualityBmaintenanceLets MCP clients browse benchmark tasks, inspect individual tasks, grade answers, execute the benchmark suite, and fetch provenance metadata.31 npmMIT

Patronus MCP Serverofficial
AlicenseNot gradedqualityDmaintenanceEnables running LLM evaluations, experiments, and custom evaluators through a standardized MCP interface.16Apache 2.0- AlicenseNot gradedqualityBmaintenanceEnables users to list and inspect benchmark tasks, grade answers, run benchmark evaluations, and retrieve provenance through its MCP interface.27 npmMIT
- FlicenseNot gradedqualityBmaintenanceEnables running deterministic multi-model prompt regression and golden dataset benchmark suites, exposing structured results and telemetry through the Model Context Protocol for integration with MCP-compliant clients.8-
- AlicenseNot gradedqualityBmaintenanceEnables MCP clients to list and inspect benchmark tasks, score submitted answers, run evaluations through OpenRouter, and retrieve provenance data for exploit-resistance testing.111 npmMIT
TDQS
Scored across 4 tools
The four tools are mostly distinct: status shows configuration/health, list enumerates entities, inspect examines a single artifact, and compare contrasts two items. There is slight potential confusion between 'inspect' and 'compare' since both involve examining artifacts, but their purposes are clear enough.
All tools share the 'aibench_' prefix and use simple verb-based names (status, list, inspect, compare). This is consistent, though the prefix is a bit verbose and 'aibench_status' is more of a noun than a verb_noun pattern.
Four tools is a reasonable, focused set for a benchmark server. It covers the core operations without being bloated, though it is on the smaller side.
The set covers status, listing, inspection, and comparison, which are the main read-only operations for benchmarks. However, there are no tools to run, create, or delete benchmarks, so the surface is incomplete for a full lifecycle.