feature-separate-eval-mcp
Related Servers
Alternatives to feature-separate-eval-mcp
No user-submitted related servers found.
Related Servers
- FlicenseCqualityCmaintenanceEnables users to analyze already-persisted single-patent evaluations to discover cross-patent batch issues such as language, technical-domain, input-structure sensitivity, and language-structure interactions, without modifying existing MCP, ledger, or single-record evaluation JSON.5-
- AlicenseCqualityDmaintenanceEnables acceptance gates for AI coding-agent runs by recording evidence, running deterministic validation, applying a quality gate, and rendering auditable outcomes.7Apache 2.0
- AlicenseNot gradedqualityBmaintenanceEnables auditing coding-agent claims against local execution traces to detect contradictions, exposing session audits, recent failures, and optional scope-alignment triage.MIT
- FlicenseNot gradedqualityBmaintenanceEnables deterministic auditing of RAG retrieval faithfulness and hallucination scores, providing structured JSON output for AI agents and MCP-compliant clients.8-
- FlicenseNot gradedqualityBmaintenanceEnables evaluation of synthetic tender requirements against supplier evidence by loading tenders, building compliance matrices, flagging unresolved risks, and preparing draft evidence packs with preserved provenance. Finalization stays blocked behind a mandatory human approval gate, so no award decision is made autonomously.-
- AlicenseAqualityCmaintenanceEnables scientific due diligence by grading claims against public literature, clinical trials, and filings, with explicit citations and optional attestation.4MIT
TDQS
Scored across 3 tools
Each tool covers a distinct stage of the evaluation workflow: status lists pending records, check performs a pre-flight evaluability test, and run executes the actual evaluation. There is no meaningful overlap or ambiguity between them.
All tool names follow the same feature_separate_eval_ prefix plus a single clear verb: status, check, run. The naming pattern is entirely consistent and predictable.
Three tools is appropriate for this focused evaluation pipeline. Each tool provides a distinct, necessary function, and none are redundant or ornamental.
The tool set covers the full workflow from discovering the next pending record, to verifying evaluability, to running the evaluation and persisting results. No critical missing operation is evident for the server's stated purpose.