Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

io.github.mdfifty50-boop/qc-validator

NPM · QC-VALIDATOR-MCP

Output quality control and validation for AI agents

Available components

0 this week 73 Trust /100

Last scanned (23 hours ago)

Scores higher than 46% of npm servers

Category Testing and QA

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →

Supply Chain Security80
  • No malware found by supply-chain analysis.Pass
  • CVE check failed: a known high-severity CVE affects zod 3.25.76, a direct dependency. A fixed version is available. View diagnostics → Fail
  • No install/post-install scripts declared.Pass
  • 52 of 130 dependencies flagged as unhealthy (1 deprecated). View diagnostics → Partial
Provenance & Transparency45
Schema Quality & AI Usability45
  • 0% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Fail
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 423 tokens (~60/item across 7 items; 6 tools + 1 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management97
  • Stability observed for 29 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 6 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 7 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
What we tested

Checks we ran (16)

  • Malware scan
  • Known CVEs
  • Install scripts
  • Dependency health
  • Source repository
  • Provenance
  • License
  • Maintenance
  • Security disclosure
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Does not apply to this package (2)

  • Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
  • Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.

The score does not measure everything. What the score does not measure →

Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 21 Nov 26 0
    • Stability: pass → 0.97 functional
  • 15 Nov 26 0
    • Stability: 0.97 → pass security
    • Dependency health: partial → 0.82 functional
  • 14 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.

  • 13 Nov 26 0
    • Dependency health: 0.82 → partial functional
  • 12 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.

  • 10 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.

  • 8 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 73 to 77. That category is still filling its 30-day observation window: 22 days of observed history at the previous scan, 23 at this one. The score rises as the window fills, whether or not the server changes.

  • 6 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 67 to 70. That category is still filling its 30-day observation window: 20 days of observed history at the previous scan, 21 at this one. The score rises as the window fills, whether or not the server changes.

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 21 Nov 2026 · Analysed npm/qc-validator-mcp@0.1.3

Provenance No attestation

The registry publishes no build provenance for this version, so there is nothing to verify.

Result No attestation
Ecosystem npm

Background: How many MCP packages publish verified provenance →

Vulnerabilities 1 finding
ID CVE Severity Vector Fix available
GHSA-mrhx-c7xc-m3w5 CVE-2023-54404 high CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H yes

Background: What a vulnerability scan can and cannot prove →

Dependencies 130 packages
Packages resolved 130
Deprecated 1
Stale 51
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 6 exposed · ~419 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
check_hallucination_risk ~101

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.

NameTypeReqDescription
claim_countnumber–Threshold for number of specific claims before flagging as high risk (default 5)
outputstringyesThe agent output text to analyze
source_textstring–Original source material the output should be grounded in (optional)

No output schema declared.

No examples provided.

check_scope_compliance ~60

Validate that agent output stays within a defined scope contract. Checks allowed/forbidden topics, word limits, and required sections.

NameTypeReqDescription
outputstringyesThe agent output text to check
scopeobjectyesScope contract to validate against

No output schema declared.

No examples provided.

generate_quality_report ~36

Generate a quality dashboard for all validated agents. Shows per-agent summaries, overall pass rate, worst/best performers, and actionable recommendations.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

get_failure_patterns ~47

Analyze common failure modes for a specific agent. Returns pass rate, average score, most frequent issue types, and quality trend direction.

NameTypeReqDescription
agent_idstringyesAgent identifier to analyze

No output schema declared.

No examples provided.

log_validation ~101

Store a validation result for trending and failure pattern analysis. Accumulates per-agent statistics over time.

NameTypeReqDescription
agent_idstringyesUnique identifier for the agent whose output was validated
issues_countintegeryesNumber of issues found
output_hashstringyesHash or identifier for the specific output that was validated
passbooleanyesWhether the output passed validation
scorenumberyesQuality score from 0-100

No output schema declared.

No examples provided.

validate_output ~74

Score agent output quality against configurable criteria. Checks length, required keywords, forbidden patterns, claim density, and task relevance.

NameTypeReqDescription
criteriaobjectyesQuality criteria to check against
outputstringyesThe agent output text to validate
task_descriptionstringyesDescription of what the agent was asked to do

No output schema declared.

No examples provided.

Install

How do I install the io.github.mdfifty50-boop/qc-validator MCP server?

io.github.mdfifty50-boop/qc-validator runs locally as an npm package, launched with npx -y qc-validator-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

npm · qc-validator-mcp

# add to Claude Code
claude mcp add mdfifty50-boop-qc-validator -- npx -y qc-validator-mcp
Common questions

What is the io.github.mdfifty50-boop/qc-validator MCP server?

io.github.mdfifty50-boop/qc-validator is an MCP server listed in the public MCP registry as io.github.mdfifty50-boop/qc-validator. Output quality control and validation for AI agents. This page covers its npm package (qc-validator-mcp).

Is the io.github.mdfifty50-boop/qc-validator MCP server safe to use?

io.github.mdfifty50-boop/qc-validator scores 73 out of 100 on VerifyMCP. We recorded 1 known advisory against it as of 21 November 2026. It declares no install or post-install scripts. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the io.github.mdfifty50-boop/qc-validator MCP server expose?

io.github.mdfifty50-boop/qc-validator exposes 6 tools: validate_output, check_hallucination_risk, check_scope_compliance, log_validation, get_failure_patterns, generate_quality_report. Their descriptions and schemas cost roughly 419 tokens of context every time the server is loaded.

Is the io.github.mdfifty50-boop/qc-validator MCP server still maintained?

io.github.mdfifty50-boop/qc-validator is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What licence is the io.github.mdfifty50-boop/qc-validator MCP server under?

io.github.mdfifty50-boop/qc-validator declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.

What did VerifyMCP test on the io.github.mdfifty50-boop/qc-validator MCP server?

VerifyMCP ran 16 checks on io.github.mdfifty50-boop/qc-validator, covering Malware scan, Known CVEs, Install scripts, Dependency health and 12 more. Endpoint Security and Transport & Reachability do not apply to an npm package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.