Skip to main content
Glama
samalbanese

mcp-tournament

by samalbanese
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to mcp-tournament

No user-submitted related servers found.

    Related Servers

    • metrillm-mcp

      MetriLLM
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables benchmarking of local LLM models (performance and quality) and sharing results to a public leaderboard via MCP tools.
      14 npm
      8
      Apache 2.0

    • sure-but-wrong

      Ayesha458
      A
      license
      A
      quality
      C
      maintenance
      Enables users to benchmark AI models across English, Urdu, and Roman Urdu by running question sets, grading answers, measuring confidently wrong and hedged responses, and producing reports, comparisons, and CSV exports through an MCP client or CLI.
      8
      MIT

    • evalsmith-mcp

      diegoperezg7
      A
      license
      A
      quality
      A
      maintenance
      Enables MCP clients to score retrieval quality with recall, precision, nDCG, hit rate and MRR, compare 2-3 configurations with seeded paired-bootstrap confidence intervals, audit agent tool calls against expected traces, and detect prompt regressions against golden sets. It also generates Markdown, JSON or JUnit reports with pass/fail gates, all deterministically and offline without paid API keys.
      6
      308 npm
      1
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A4.2/5.0

    Scored across 8 tools

    Disambiguation4/5

    Most tools have clearly distinct roles (quick_test vs evaluate by cost/scale, leaderboard vs get_run by aggregate vs single). However, tournament_list_benches and tournament_options overlap on bench/scenario discovery, and plan_run vs evaluate require reading to distinguish preview from execution.

    Naming Consistency4/5

    Names follow a consistent tournament_ prefix with snake_case. Most use verb_noun (list_benches, plan_run, get_run, create_bench), but tournament_options and tournament_leaderboard are noun-only, a minor deviation from the pattern.

    Tool Count5/5

    Eight tools is well-scoped for a tournament/evaluation server. Each tool earns its place: discovery, planning, cheap vs full execution, results reading, and bench creation are all distinct responsibilities.

    Completeness4/5

    The evaluation lifecycle is well covered: discover, plan, execute (cheap and full), read results, and create custom benches, with paid-call safeguards. Minor gaps exist around managing saved artifacts (update/delete benches or runs) and cancelling long-running evaluations.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources