A
licenseNot graded
qualityB
maintenanceEnables deterministic auditing of multi-hop agent trajectories through cyclic loop detection, diversity scoring, and execution drift prevention via the Model Context Protocol.
7
MIT
JevGuard MCP Server
by seb4ez
Related Servers
Alternatives to JevGuard MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceEnables deterministic execution, cryptographic security, and game-theoretic optimization through the Model Context Protocol, returning deterministic JSON tool results for agent telemetry and task inputs.7MIT
LogicMem MCP Serverofficial
AlicenseBqualityCmaintenanceProvides persistent memory, reasoning, agent-to-agent sharing, and immutable audit trail for AI agents via the Model Context Protocol.121MIT- AlicenseBqualityFmaintenanceProvides persistent memory, reasoning engine, agent-to-agent sharing, and immutable audit trail for AI agents via the Model Context Protocol.12MIT
- AlicenseNot gradedqualityDmaintenanceProvides natural language inference (NLI) capabilities via the Model Context Protocol, allowing AI agents to verify factual consistency and detect contradictions in text.32 PyPI3MIT
- FlicenseNot gradedqualityBmaintenanceEnables deterministic multi-agent debate cross-examination and consensus arbitration through the Model Context Protocol, with structured JSON output and zero external dependencies.7-
TDQS
B3.4/5.0
Scored across 7 tools
Disambiguation2/5
Several tools occupy overlapping conceptual space: evaluate_decision, jevguard_calibrate, and jevguard_evaluate all involve evaluating, calibrating, or escaping closed-world options. Command safety and code patch verification are distinct, but an agent could easily misselect among the evaluation-related tools.
Naming Consistency2/5
Naming is inconsistent: some tools use the jevguard_ prefix with snake_case (jevguard_prune_state, jevguard_calibrate), while others use bare action-style names (evaluate_command_safety, verify_code_patch). This mixed convention makes the tool set feel less predictable.
Tool Count4/5
Seven tools is a reasonable size for a specialized evaluation server. The count is not excessive, though the overlapping evaluation/calibration tools could likely be consolidated without losing much functionality.
Completeness4/5
The tool set covers the core pipeline stages: state pruning, fingerprinting, safety evaluation, code patch verification, decision evaluation, calibration, and full pipeline execution. Minor gaps exist around direct inspection of cached fingerprints or explicit configuration of the full pipeline, but the core domain is covered.
Maintenance
ActivitySlowing
ResponsivenessNo recent community issues