Benchwarmers
Related Servers
Alternatives to Benchwarmers
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceEnables orchestrating a panel of frontier AI models that independently propose, critique, revise, and converge on a single agreed answer to a problem, using existing vendor subscriptions or API keys.15 npm1MIT
- AlicenseNot gradedqualityDmaintenanceAn MCP server that queries a panel of LLMs from different providers via OpenRouter and returns their answers side by side, optionally synthesizing them to highlight disagreements.1MIT
- AlicenseAqualityBmaintenanceBlind multi-model councils with anonymous LLM seats and direct 1:1 chat as a local MCP server. Enables asking one question to get independent answers from multiple model CLIs, then blind scoring and reveal.1759 PyPIAGPL 3.0
- FlicenseNot gradedqualityAmaintenanceEnables coding agents and OpenAI- or Anthropic-compatible clients to send chat requests through a single local pooled endpoint that spans free provider tiers, with keyless startup, automatic failover, model discovery, and capacity/health inspection tools.-
- AlicenseNot gradedqualityBmaintenanceSelf-hosted MCP gateway that aggregates many MCP servers into a single endpoint for AI clients, supporting hosted, local stdio, and Git-sourced MCPs.3MIT
- AlicenseNot gradedqualityCmaintenanceA self-hostable MCP server that routes prompts to multiple LLM providers using declarative policies, with multi-role orchestration for independence and verification.MIT
TDQS
Scored across 4 tools
Each tool targets a distinct action: enumerate collections, query a collection, list seats awaiting judgment, and submit a judgment. The pending_verdicts/verdict pair is complementary (read vs. write) and clearly separated, though the note that pending_verdicts is for a Stop hook and 'you do not need to call it' adds mild confusion about whether an agent should invoke it at all.
All names use snake_case, so the casing convention is uniform, but the verb style is mixed: `list_collections` is verb_noun, `ask` is a bare verb, while `verdict` and `pending_verdicts` are nouns with no verb at all. Readable, but a reader cannot predict a tool's shape from its name.
Four tools match the narrow domain of querying model collections and recording judgments; each has a clear job (discover, ask, check pending, judge). It is on the lean side and leans on server-side configuration for collections, but no tool feels redundant or missing at this scope.
The core loop (list collection → ask → verdict) is covered, and call ids are surfaced in ask output. However, there is no tool to retrieve a prior call's answers by call id, no way to inspect a collection's members in detail, and no way to review already-submitted verdicts or the 'confidently wrong' record — so the call-id datum is a dead end for the agent.