home / mcp / elenchus mcp server
Adversarial verification for code using a Verifier↔Critic debate loop, with multi-language dependency analysis and session management.
Configuration
View docs{
"mcpServers": {
"jhlee0409-elenchus-mcp": {
"command": "npx",
"args": [
"-y",
"@jhlee0409/elenchus-mcp"
],
"env": {
"LOCALAPPDATA": "not-set",
"XDG_DATA_HOME": "not-set",
"ELENCHUS_DATA_DIR": "~/.elenchus"
}
}
}
}Elenchus is an MCP server that orchestrates an adversarial verification workflow between a Verifier and a Critic to uncover issues in code through structured debate. It analyzes multiple dimensions like security, correctness, reliability, maintainability, and performance, guiding you toward a thorough, context-aware assessment rather than simple keyword checks.
Describe what you want to verify to your AI assistant. The system will engage in a Verifier↔Critic loop to surface issues, challenge findings, and converge on a final verdict. You can request checks on specific files or modules and specify focus areas such as security, correctness, and edge-case coverage. Use prompts that clearly identify targets (for example, a path like src/auth or a module like payment processing) and the desired verification focus.
Prerequisites: ensure you have Node.js installed (v18 or newer) and a modern MCP client that can load stdio MCP servers. You should have an environment capable of running npm or npx commands from your shell.
# Optional: verify Node.js version
node --version
```
```bash
# Install and start the Elenchus MCP server via MCP client integration (example shown in client configuration)
# You will typically add the server config to your MCP client settings as shown in the quick start snippetAdd the following MCP server configuration to your client’s settings so your assistant can access Elenchus through the standard MCP channel.
{
"mcpServers": {
"elenchus": {
"command": "npx",
"args": ["-y", "@jhlee0409/elenchus-mcp"]
}
}
}Initialize a new verification session by specifying the target, requirements, working directory, and optional mode and differential settings.
Retrieve the current session context, including files collected, issues, and recommended actions.
Submit a Verifier or Critic round with full analysis output and optional issue updates.
End the session and produce a final verdict with a summary.
Query issues with optional status filtering to review current findings.
LLM-based evaluation of verification convergence quality.
LLM-based severity classification for identified issues.
LLM-based validation of edge cases to ensure coverage.
Submit evaluation results from an LLM-based assessor.
Create a checkpoint for session state to enable rollback.
Rollback to a previous checkpoint.
Apply fixes and re-run verification as needed.
Analyze ripple effects across dependencies when changes occur.
Generate a summary of mediator actions and interventions.
Return the current role prompt for a given role (verifier/critic).
Summarize role configurations and compliance requirements.
Update role-related configuration such as minimum compliance and strict mode.
Initiate a re-verification pass on a target after fixes.
Save a differential baseline for comparison in future analyses.
Get a summary of diffs between baselines or revisions.
Fetch historical verification data for auditing.
Retrieve statistics on response caching.
Clear cached verification results.
Check the status of the tiered verification pipeline.
Escalate to a higher verification tier as needed.
Complete the current verification tier.
Query the status of quality safeguards.
Adjust confidence levels for verification results.
Record results from sampling in safeguards checks.
Check if convergence criteria can be satisfied.
Configure data compression mode for responses.
Obtain statistics on optimization of verification tasks.
Configure optimization settings for performance.
Estimate potential time or resource savings from optimizations.
Generate dynamic roles for Verifier and Critic.
Set dynamic role configurations for adaptive workflows.