Elenchus MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
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
| Capability | Details |
|---|---|
| tools | {} |
| logging | {} |
| prompts | {} |
| resources | {
"subscribe": true,
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| elenchus_start_sessionB | Start a new Elenchus verification session. Collects initial context, builds dependency graph, and initializes mediator. |
| elenchus_get_contextB | Get current verification context including files, issues summary, and session state. |
| elenchus_submit_roundA | Submit the output of a verification round. Analyzes for new issues, context expansion, convergence, and mediator interventions. |
| elenchus_end_sessionB | End the verification session with a final verdict. |
| elenchus_get_issuesB | Get issues from the current session with optional filtering. |
| elenchus_checkpointB | Create a checkpoint for potential rollback. |
| elenchus_rollbackC | Rollback session to a previous checkpoint. |
| elenchus_apply_fixA | Apply a fix for an issue within the current session. Creates checkpoint, updates issue status, refreshes file context, and optionally triggers re-verification. Use this to maintain fix-verify continuity without starting new sessions. |
| elenchus_ripple_effectA | Analyze ripple effect of a code change. Shows which files and functions will be affected by modifying a specific file. |
| elenchus_mediator_summaryA | Get mediator summary including dependency graph stats, verification coverage, and intervention history. |
| elenchus_get_role_promptA | Get detailed role prompt and guidelines for Verifier or Critic. Includes mustDo/mustNotDo rules, output templates, and checklists. |
| elenchus_role_summaryB | Get role enforcement summary including compliance history, average scores, violations, and current expected role. |
| elenchus_update_role_configC | Update role enforcement configuration. Can enable strict mode, change minimum compliance score, or toggle role alternation requirement. |
| elenchus_start_reverificationA | Start a re-verification session for resolved issues. Links to a previous verification session and focuses on verifying that fixes are correct and complete. Returns focused verification context with target issues. |
| elenchus_save_baselineA | Save verification baseline after a successful session. This baseline is used for differential analysis in future verifications to only check changed code. |
| elenchus_get_diff_summaryA | Get differential analysis summary for a project. Shows what has changed since the last verification and estimates token savings. |
| elenchus_get_project_historyB | Get verification history for a project including past sessions and baselines. |
| elenchus_get_cache_statsB | Get cache statistics including hit rate, total entries, and token savings. |
| elenchus_clear_cacheB | Clear all cached verification results. Requires confirm: true. |
| elenchus_get_pipeline_statusB | Get current tier pipeline status including completed tiers, escalations, and token usage. |
| elenchus_escalate_tierA | Manually escalate to a higher verification tier (screen → focused → exhaustive). |
| elenchus_complete_tierC | Mark the current tier as complete and check for auto-escalation based on issues found. |
| elenchus_get_safeguards_statusB | Get quality safeguards status including periodic verification, confidence, and sampling stats. |
| elenchus_update_confidenceB | Update confidence scores for files based on verification method (cache, chunk, tiered, etc.). |
| elenchus_record_sampling_resultB | Record results from random sampling verification of a skipped file. |
| elenchus_check_convergence_allowedB | Check if session convergence is allowed based on quality safeguards. |
| elenchus_set_compression_modeC | Set the response compression mode for token optimization. Use "compact" for moderate savings or "minimal" for aggressive savings. |
| elenchus_get_optimization_statsB | Get current token optimization statistics and recommendations. |
| elenchus_configure_optimizationC | Configure token optimization settings including compression, context management, and semantic caching. |
| elenchus_estimate_savingsC | Estimate potential token savings for a verification session. |
| elenchus_generate_rolesA | Generate customized Verifier/Critic role prompts based on user requirements. This is a 3-step process:
Each step returns a prompt to send to an LLM. After all 3 steps, call elenchus_set_dynamic_roles with the results. |
| elenchus_set_dynamic_rolesA | Set dynamically generated roles for a session. Call this after completing all 3 steps of elenchus_generate_roles. The roles will be used automatically by getRolePrompt when sessionId is provided. |
| elenchus_evaluate_convergenceC | Get LLM evaluation prompt for convergence quality assessment. Returns a prompt to send to an LLM. |
| elenchus_evaluate_severityB | Get LLM evaluation prompt for issue severity assessment. Returns a prompt to send to an LLM. |
| elenchus_evaluate_edge_casesA | Get LLM evaluation prompt for edge case coverage. Returns a prompt to send to an LLM. |
| elenchus_submit_llm_evaluationB | Submit LLM evaluation response. Call this after receiving an LLM response to an evaluation prompt. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| verify | Run adversarial verification on target code with Verifier↔Critic loop |
| consolidate | Consolidate verification results into prioritized fix plan |
| apply | Apply consolidated fixes to codebase with verification |
| complete | Run complete pipeline: VERIFY → CONSOLIDATE → APPLY → RE-VERIFY until zero issues |
| cross-verify | Adversarial cross-verification loop for thorough validation |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/jhlee0409/elenchus-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server