Skip to main content
Glama
keeganthewhi

tenth-man-mcp

by keeganthewhi
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to tenth-man-mcp

No user-submitted related servers found.

    Related Servers

    • Panel Review

      TruVerifAI
      A
      license
      Not graded
      quality
      A
      maintenance
      Panel Review is the guardian agent for AI's highest-stakes coding decisions. Before an agent's riskiest designs, diffs, or commits ship, four frontier models, from OpenAI, Anthropic, Google, and xAI, argue them through and return severity-tagged findings, with review gates the agent cannot silently skip.
      131 npm
      2
      MIT

    • paranoia-local

      subvertnormality
      A
      license
      Not graded
      quality
      A
      maintenance
      A local MCP server that provides adversarial code review by having one frontier agent (Claude Code or Codex) critique code changes using the other agent (Codex or Claude Code) with full repository access, enabling a genuine second opinion on code and plans.
      14
      MIT

    • agentdesk-mcp

      Rih0z
      A
      license
      A
      quality
      C
      maintenance
      Adversarial AI review API — independent AI reviews another AI's output. Stop LLMs from grading their own homework. Provides automated quality assurance for AI-generated code, content, and other outputs through independent review pipelines.
      4
      5 npm
      3
      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.1/5.0

    Scored across 3 tools

    Disambiguation5/5

    Each tool serves a distinct purpose: configuration, history query, and triggering a review. There is no ambiguity or overlap between them.

    Naming Consistency5/5

    All tool names follow the same pattern: 'tenth_man_' followed by a verb (configure, history, review). This is consistent and predictable.

    Tool Count5/5

    With only 3 tools, the server is tightly scoped to its core functionality (configure, review, history). This is appropriate for a focused protocol like the 10th Man.

    Completeness4/5

    The tools cover the essential lifecycle: configuration, triggering a review, and querying history. A minor gap is the lack of a tool for approval or execution plan creation, but these are described as manual steps outside the tool surface.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources