Qc Validator MCP server

by mdfifty50-boop·io.github.mdfifty50-boop/qc-validator·v0.1.3

No reviews yet

Output quality control and validation for AI agents

B78/100grade B

Write a review Install

What users say

No reviews yet

Be the first

Safety scan

B78/100

full report

Adoption

New

0 stars58 downloads/wk

Reviews

Write one

Nobody has reviewed Qc Validator yet.

If you have run it, two minutes of your experience saves the next person an afternoon.

Qc Validator tools (6)

write = sends, deletes, buys or posts

Read from the package source without running it. The installed server may list more.

check_hallucination_risk
Estimate hallucination likelihood in agent output. If source text is provided, checks grounding. Otherwise flags outputs with high counts of specific numbers, dates, and URLs.
check_scope_compliance
Validate that agent output stays within a defined scope contract. Checks allowed/forbidden topics, word limits, and required sections.
generate_quality_report
Generate a quality dashboard for all validated agents. Shows per-agent summaries, overall pass rate, worst/best performers, and actionable recommendations.
get_failure_patterns
Analyze common failure modes for a specific agent. Returns pass rate, average score, most frequent issue types, and quality trend direction.
log_validation
Store a validation result for trending and failure pattern analysis. Accumulates per-agent statistics over time.
validate_output
Score agent output quality against configurable criteria. Checks length, required keywords, forbidden patterns, claim density, and task relevance.

Public scan report

scanner v0.1.9 · 2026-09-27 · same rubric, same numbers if you re-run it

no findings

Code scan13 source files scanned25/25
–Live reliabilityno gateway calls yet and no remote to proben/a
–Tool poisoningtools not inspected (local package is not executed); not countedn/a
Auth qualitylocal package, no credentials required12/15
Maintenancelast push 156 days ago8/15
Maintainer identityregistry namespace matches repository owner6/10

Overall 78/100. Components that don't apply are left out of the denominator. Any critical finding is an F.Rubric Appeal a finding JSON

How Qc Validator compares

Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.

Safety score: 78/100; higher than 57% of 48,255 servers
Tools: 6; the typical server has 7
Tools that change things: 0%; typical: 0%. Fewer write tools means less an agent can break
Downloads a week: 58; more than 48% of 12,191 servers with a package

What its tools let an agent do: 5 read · 1 create

Install Qc Validator in Claude Code, Cursor or VS Code

Runs npx -y qc-validator-mcp on your machine. Read the scan report first; the gateway never runs local packages.

claude mcp add qc-validator -- npx -y qc-validator-mcp

Add to Cursor

What the publisher says

From the Qc Validator repository's README, as published. We do not edit it. Read it on GitHub

qc-validator-mcp

Runtime quality validation for AI agent outputs. Detect hallucinations, enforce scope compliance, and score output quality — all via MCP.

Install

npx qc-validator-mcp

Claude Desktop

{
  "mcpServers": {
    "qc-validator": {
      "command": "npx",
      "args": ["qc-validator-mcp"]
    }
  }
}

Tools

validate_output

Score agent output against configurable criteria: length limits, required keywords, forbidden patterns, and factual claim density.

Params: output, task_description, criteria { max_length, required_keywords[], forbidden_patterns[], factual_claims_count }
Returns: { pass, score, issues[], recommendation }

checkhallucinationrisk

Estimate hallucination likelihood. With source text, checks sentence-level grounding. Without source, flags outputs dense with specific numbers, dates, and URLs.

Params: output, source_text (optional), claim_count (default 5)
Returns: { risk_level, unsupported_claims[], confidence, suggestion }

checkscopecompliance

Validate output against a scope contract — allowed/forbidden topics, word limits, required sections.

Params: output, scope { allowed_topics[], forbidden_topics[], max_words, required_sections[] }
Returns: { compliant, violations[], scope_utilization_percent }

log_validation

Store validation results for per-agent trending.

Params: agent_id, output_hash, score, pass, issues_count
Returns: { logged, agent_id, total_validations }

getfailurepatterns

Analyze common failure modes for a specific agent.

Params: agent_id
Returns: { total_validations, pass_rate, avg_score, most_common_issues[], trend }

generatequalityreport

Quality dashboard across all validated agents — no parameters required.

Returns: { total_agents, overall_pass_rate, agents[], worst_performers[], best_performers[], recommendations[] }

Resource

qc://dashboard — Quality metrics for all validated agents

Architecture

Pure Node.js ES modules
In-memory Maps (no external dependencies)
stdio transport via @modelcontextprotocol/sdk
Zero configuration required

License

MIT

Nothing above is checked by us. What we check is on the safety report.

Qc Validator: common questions

Is Qc Validator MCP server safe?: Mostly: it is graded B (78/100). Read the Qc Validator safety report
How do I install Qc Validator?: It runs on your machine. Copy the Claude Code, Cursor, VS Code or Claude Desktop config from the install section.
Does Qc Validator need an API key?: Not as far as the registry entry and our scan can tell: no credentials are declared or required.
Is Qc Validator maintained?: The last commit was 194 days ago (2026-04-24). The latest release is v0.1.3.
How does Qc Validator compare with other MCP servers?: safety score 78/100 (higher than 57% of 48,255 servers); tools 6 (the typical server has 7); tools that change things 0% (typical: 0%. Fewer write tools means less an agent can break). Full comparison.