qc-validator-mcp
Related Servers
Alternatives to qc-validator-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceScores AI outputs for faithfulness, relevancy, and hallucination inside any MCP client, with custom metrics, golden sets, and run history with dashboards.Apache 2.0
- AlicenseNot gradedqualityDmaintenanceRuntime safety guardrails for AI coding agents. Checks file access, validates shell commands, and scores your repo's AI safety — all via MCP.58MIT
- AlicenseBqualityCmaintenancePre-execution governance for AI agents. 45 MCP tools for hold queues, audit trails, risk scoring, and policy enforcement. Validates agent actions before they execute.45731MIT
- AlicenseNot gradedqualityBmaintenanceSecurity middleware for LLM agents. Authorize tool calls, scan for injection, quarantine poisoned memory, and redact PII — all through MCP. 0% injection success rate on 1,054 tested attacks.Apache 2.0
- FlicenseNot gradedqualityCmaintenanceEnables LLM agents to enforce security policies by authorizing tool calls, scanning for prompt injection, checking memory writes, redacting PII, and accessing audit trails through MCP.-
- AlicenseNot gradedqualityCmaintenanceAn MCP server that enforces runtime governance on AI agent actions — file access, command execution, delegation chains, and permission escalation.MIT
TDQS
Scored across 6 tools
The tools are mostly distinct: validate_output provides general scoring, while check_hallucination_risk and check_scope_compliance target specific failure modes. There is slight overlap between validate_output's forbidden patterns and check_scope_compliance's allowed/forbidden topics, but the descriptions clarify different scopes.
All tool names follow a consistent verb_noun pattern (validate_output, get_failure_patterns, check_hallucination_risk, check_scope_compliance, log_validation, generate_quality_report), using lowercase with underscores throughout. This makes the API predictable and easy to navigate.
With 6 tools, the server is well-scoped for its purpose of validating agent output. Each tool covers a distinct step in the validation workflow: executing checks, analyzing patterns, logging results, and reporting, without unnecessary bloat.
The core workflow (validate, log, analyze, report) is covered. However, there is no tool to manage the configurable criteria mentioned in validate_output, which is a minor gap. Additionally, update/delete operations for logged results are missing, but the main lifecycle is intact.