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

io.github.mdfifty50-boop/qc-validator

NPM · QC-VALIDATOR-MCP · SCANNED AUG 3

Output quality control and validation for AI agents

Available components

+35 this week 59 Trust /100
Trust breakdown (6 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 →

Supply Chain Security87
  • No malware found by supply-chain analysis.Pass
  • Only part of the dependency tree could be resolved (132 of 136), so this covers what we could see, not the whole tree.Partial
  • No install/post-install scripts declared.Pass
  • Only part of the dependency tree could be resolved (132 of 136), so this covers what we could see, not the whole tree. View diagnostics → Partial
Provenance & Transparency45
Schema Quality & AI Usability42
  • 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 Management0
  • Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
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
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass

Unverified: 1 category

A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.

Install

Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.

npm · qc-validator-mcp

# add to Claude Code
claude mcp add mdfifty50-boop-qc-validator -- npx -y qc-validator-mcp
# add to Codex CLI
codex mcp add mdfifty50-boop-qc-validator -- npx -y qc-validator-mcp
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "mdfifty50-boop-qc-validator": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "qc-validator-mcp"
      ],
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add mdfifty50-boop-qc-validator --command npx --arg -y --arg qc-validator-mcp
# ~/.hermes/config.yaml
mcp_servers:
  mdfifty50-boop-qc-validator:
    command: "npx"
    args: ["-y", "qc-validator-mcp"]
// mcp.json
{
  "mcpServers": {
    "mdfifty50-boop-qc-validator": {
      "command": "npx",
      "args": [
        "-y",
        "qc-validator-mcp"
      ]
    }
  }
}
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.

  • 2 Aug 26 +35
    • Provenance: unverified → fail security
    • Known CVEs: unverified → partial security
    • Install scripts: unverified → pass security
    • Malware scan: unverified → pass security
    • Schema quality: unverified → good functional
    • Maintenance: unverified → pass functional
    • Dependency health: unverified → partial functional
    • License: unverified → pass functional
    • Licence: MIT functional
  • 1 Aug 26 +5
    • Stability: Stability not yet verified: not enough scan history yet (needs a 30-day window). security
    • MCP protocol: unverified → pass functional
  • 31 Jul 26 −25
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 28 Jul 26 +20
    • Schema quality: unverified → 0 functional
    • Tool coverage: unverified → 100 functional
    • First check of Tool coverage: 100 functional
    • First check of Schema quality: unverified functional
    • First check of Schema quality: pass functional
    • First check of Schema quality: fail functional
  • 27 Jul 26 24

    First indexed and scored.

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 3 Aug 2026 · Analysed npm/[email protected]

Provenance none

Ecosystem: npm · Outcome: none

Dependencies 132 packages

132 packages in the resolved dependency tree · 132 deprecated · 49 stale.

The dependency tree was only partially resolved, so these counts may be incomplete.

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.

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_countnumberThreshold for number of specific claims before flagging as high risk (default 5)
outputstringyesThe agent output text to analyze
source_textstringOriginal 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.