DocGuard
NPM · DOCGUARD-CLI
Deterministic doc-drift detection: guard, score, explain, verify-claims and diagnose MCP tools.
Available components
Last scanned (20 hours ago)
Scores higher than 99% of npm servers
Category Testing and QA
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 Security100
- 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
- 0 of 4 dependencies flagged as unhealthy. View diagnostics → Pass
Provenance & Transparency100
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to raccioly/docguard). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 1 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability80
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 603 tokens (~86/item across 7 items; 7 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
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 7 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
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.
- 4 Nov 26 0
- Stability: 0.97 → pass security
- 3 Nov 26 0
- Stability: pass → 0.97 functional
- 28 Oct 26 0
- Package version: 0.33.1 → 0.40.5 functional
- 22 Oct 26 0
- Stability: 0.97 → pass security
- 21 Oct 26 0
- Stability: pass → 0.97 functional
- 17 Oct 26 +2
- Stability: 0.80 → pass security
- 16 Oct 26 −2
- Stability: pass → 0.80 functional
- 15 Oct 26 0
- Package version: 0.33.1 → 0.40.5 functional
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 4 Nov 2026 · Analysed npm/docguard-cli@0.40.5
Provenance Verified
A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.
| Result | Verified |
|---|---|
| Ecosystem | npm |
| Reason | Verified |
| Discovered via | Registry attestation endpoint |
| Source repo | raccioly/docguard |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/raccioly/docguard/.github/workflows/release.yml@refs/heads/main |
| Rekor log index | 2839105235 |
| Predicate type | SLSA build provenance https://slsa.dev/provenance/v1 |
| Subject digest | sha512:7220564a6ca0d744a927723432ffbe1c966ed10620150122c66c766b1c3ca26f853771a19f03fa87fe3b371dd83435251e88d61ac6f370d6d17c973b0 |
Background: How many MCP packages publish verified provenance →
Dependencies 4 packages
| Packages resolved | 4 |
|---|---|
| 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 →
docguard_diagnose Diagnose what to fix ~80
Run guard and return only what needs fixing: failing/warning validators with their messages, structured findings, and suggested next actions — shaped for an agent to act on.
| Name | Type | Req | Description |
|---|---|---|---|
| projectDir | string | – | Path to the project to inspect (absolute, or relative to the server's working directory). Defaults to the working directory the server was started in. |
No output schema declared.
No examples provided.
docguard_explain Explain a finding code ~78
Explain a stable DocGuard finding code (e.g. STR001, ENV003): what it means, which validator emits it, and the inline suppression to use if it's a confirmed false positive.
| Name | Type | Req | Description |
|---|---|---|---|
| code | string | yes | The finding code guard prints next to each finding, e.g. STR001 or ENV003. Case-insensitive. |
No output schema declared.
No examples provided.
docguard_guard Guard docs against code ~97
Run every enabled DocGuard validator against the project's canonical docs. Returns the full guard JSON contract: status (PASS/WARN/FAIL), structured findings with stable codes and suggestions, nextStep, doc coverage map, semantic-claim count, and per-validator results.
| Name | Type | Req | Description |
|---|---|---|---|
| projectDir | string | – | Path to the project to inspect (absolute, or relative to the server's working directory). Defaults to the working directory the server was started in. |
No output schema declared.
No examples provided.
docguard_report Compliance-evidence bundle ~106
Generate the commit-stamped compliance-evidence bundle: guard verdict per validator, findings grouped by stable code, CDD score, ALCOA+ data-integrity attributes, fix history, and a tamper-evident sha256 integrity hash. Evidence, not a gate — it reports state without failing.
| Name | Type | Req | Description |
|---|---|---|---|
| projectDir | string | – | Path to the project to inspect (absolute, or relative to the server's working directory). Defaults to the working directory the server was started in. |
No output schema declared.
No examples provided.
docguard_score CDD maturity score ~65
Compute the project's CDD maturity score (0-100) with letter grade and per-category breakdown.
| Name | Type | Req | Description |
|---|---|---|---|
| projectDir | string | – | Path to the project to inspect (absolute, or relative to the server's working directory). Defaults to the working directory the server was started in. |
No output schema declared.
No examples provided.
docguard_verify_claims Extract claims to verify ~89
Extract the semantic claims in the project's canonical docs — documented numbers, limits, and enums — as a verification task list. Deterministic discovery, LLM judgment — the caller verifies each claim against the code.
| Name | Type | Req | Description |
|---|---|---|---|
| projectDir | string | – | Path to the project to inspect (absolute, or relative to the server's working directory). Defaults to the working directory the server was started in. |
No output schema declared.
No examples provided.
docguard_verify_evidence Verify declared evidence ~88
Evaluate `.docguard-evidence.json` against bounded local sources. Returns explicit verified-within-scope, contradicted, stale, inconclusive, and unsupported states; verification applies only to each selected statement.
| Name | Type | Req | Description |
|---|---|---|---|
| projectDir | string | – | Path to the project to inspect (absolute, or relative to the server's working directory). Defaults to the working directory the server was started in. |
No output schema declared.
No examples provided.
How do I install the DocGuard MCP server?
DocGuard runs locally as an npm package, launched with npx -y docguard-cli. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · docguard-cli
claude mcp add raccioly-docguard -- npx -y docguard-cli
What is the DocGuard MCP server?
DocGuard is an MCP server listed in the public MCP registry as io.github.raccioly/docguard. Deterministic doc-drift detection: guard, score, explain, verify-claims and diagnose MCP tools. This page covers its npm package (docguard-cli).
Is the DocGuard MCP server safe to use?
DocGuard scores 96 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 4 November 2026. It declares no install or post-install scripts. Its build provenance is signed and verified. 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 DocGuard MCP server expose?
DocGuard exposes 7 tools: docguard_guard, docguard_score, docguard_explain, docguard_verify_evidence, docguard_verify_claims, and 2 more. Their descriptions and schemas cost roughly 603 tokens of context every time the server is loaded.
Is the DocGuard MCP server still maintained?
DocGuard is still listed as active in the MCP registry. We last reached this channel on 4 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 DocGuard MCP server under?
DocGuard declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.