Skip to main content
Glama
keeganthewhi

tenth-man-mcp

by keeganthewhi
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault

No arguments

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{
  "listChanged": true
}

Tools

Functions exposed to the LLM to take actions

NameDescription
tenth_man_reviewA

Triggers the 10th Man Protocol — spawns 3 contrarian agents to independently challenge proposed code changes before execution.

Use when:

  • Changes touch 3+ files across modules

  • Architecture decisions (new patterns, major refactors)

  • Auth, security, or data model changes

  • DB migrations or schema changes

  • Any change where a mistake would be costly

The protocol takes 2-5 minutes depending on agent availability. External agents (Codex, Gemini) run in parallel; Claude subagents run sequentially in isolated context windows.

In STANDARD mode: writes a review file and waits for your verbal approval. After approval, you MUST create an execution plan. In AUTO mode: returns findings directly — incorporate them into your plan and proceed.

tenth_man_configureA

Configure agent preferences, timeouts, and trigger patterns for the 10th Man Protocol. Auto-detects available CLI agents if not specified.

tenth_man_historyA

Query past 10th Man audit reports from this repository. Returns recent reviews with verdicts, issues found, and agents used.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

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