io.github.ZUHcYa/ai-validation
NPM · AI-VALIDATION-MCP · SCANNED SEP 20
Independent AI code validation: test bias, edge cases, coverage gaps.
Available components
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 Security98
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- 39 of 122 dependencies flagged as unhealthy (1 deprecated). View diagnostics → Partial
Provenance & Transparency19
- Repository check failed: the declared repository URL returned HTTP 404. See how to fix → View diagnostics → Fail
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 181 days ago).Pass
- Security-disclosure policy not yet verified: we couldn't inspect the source repository.Unverified
Schema Quality & AI Usability80
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 229 tokens (~76/item across 3 items; 3 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management90
- Stability observed for 27 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 3 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 3 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
How do I install the io.github.ZUHcYa/ai-validation MCP server?
io.github.ZUHcYa/ai-validation runs locally as an npm package, launched with npx -y ai-validation-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 · ai-validation-mcp
claude mcp add zuhcya-ai-validation -- npx -y ai-validation-mcp
{
"mcpServers": {
"zuhcya-ai-validation": {
"command": "npx",
"args": [
"-y",
"ai-validation-mcp"
]
}
}
} {
"servers": {
"zuhcya-ai-validation": {
"command": "npx",
"args": [
"-y",
"ai-validation-mcp"
]
}
}
} codex mcp add zuhcya-ai-validation -- npx -y ai-validation-mcp
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"zuhcya-ai-validation": {
"type": "local",
"command": [
"npx",
"-y",
"ai-validation-mcp"
],
"enabled": true
}
}
} openclaw mcp add zuhcya-ai-validation --command npx --arg -y --arg ai-validation-mcp
mcp_servers:
zuhcya-ai-validation:
command: "npx"
args: ["-y", "ai-validation-mcp"] {
"McpServers": {
"zuhcya-ai-validation": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"ai-validation-mcp"
]
}
}
} assistant mcp add zuhcya-ai-validation -t stdio -c npx -a -y ai-validation-mcp
{
"mcpServers": {
"zuhcya-ai-validation": {
"command": "npx",
"args": [
"-y",
"ai-validation-mcp"
]
}
}
} 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.
- 19 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
- 17 Sept 26 −3
- Stability: pass → 0.80 functional
- 16 Sept 26 +1
- Stability: 0.97 → pass security
- 14 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.
- 12 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
- 10 Sept 26 −3
- Stability: pass → 0.80 functional
- 9 Sept 26 +1
- Stability: 0.97 → pass security
- 7 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.
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 20 Sept 2026 · Analysed npm/ai-validation-mcp@0.1.2
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 →
Dependencies 122 packages
| Packages resolved | 122 |
|---|---|
| Deprecated | 1 |
| Stale | 38 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
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 →
coverage_gap_analysis ~81
Identify untested code paths, branches, and logic gaps in existing tests. Returns coverage score, gap details, and suggested tests to close gaps.
| Name | Type | Req | Description |
|---|---|---|---|
| language | string | – | Programming language (default: typescript) |
| sourceCode | string | yes | The source code to analyze coverage for |
| testCode | string | yes | The existing test code to evaluate |
No output schema declared.
No examples provided.
suggest_edge_cases ~68
Suggest comprehensive edge cases for a given function/code. Returns categorized edge cases: happy path, error handling, boundary, type coercion, integration.
| Name | Type | Req | Description |
|---|---|---|---|
| language | string | – | Programming language (default: typescript) |
| sourceCode | string | yes | The source code to analyze for edge cases |
No output schema declared.
No examples provided.
validate_tests ~80
Analyze existing tests for bias, missing edge cases, and quality issues. Returns bias warnings, missing edge case suggestions, and an overall quality score.
| Name | Type | Req | Description |
|---|---|---|---|
| language | string | – | Programming language (default: typescript) |
| sourceCode | string | yes | The source code to validate tests against |
| testCode | string | yes | The existing test code to analyze |
No output schema declared.
No examples provided.
What is the io.github.ZUHcYa/ai-validation MCP server?
io.github.ZUHcYa/ai-validation is an MCP server listed in the public MCP registry as io.github.ZUHcYa/ai-validation. Independent AI code validation: test bias, edge cases, coverage gaps. This page covers its npm package (ai-validation-mcp).
Is the io.github.ZUHcYa/ai-validation MCP server safe to use?
io.github.ZUHcYa/ai-validation scores 78 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 20 September 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.ZUHcYa/ai-validation MCP server expose?
io.github.ZUHcYa/ai-validation exposes 3 tools: validate_tests, suggest_edge_cases, coverage_gap_analysis. Their descriptions and schemas cost roughly 229 tokens of context every time the server is loaded.
Is the io.github.ZUHcYa/ai-validation MCP server still maintained?
io.github.ZUHcYa/ai-validation is still listed as active in the MCP registry. We last reached this channel on 20 September 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.ZUHcYa/ai-validation MCP server under?
io.github.ZUHcYa/ai-validation declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.