DocGuard MCP server

by raccioly·io.github.raccioly/docguard·v0.40.5·31 stars

No reviews yet

Deterministic doc-drift detection: guard, score, explain, verify-claims and diagnose MCP tools.

A92/100grade A

Write a review Install

What users say

No reviews yet

Be the first

Safety scan

A92/100

full report

Adoption

Established

31 stars1.3k downloads/wk

Reviews

Write one

Nobody has reviewed DocGuard yet.

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

DocGuard tools (7, 2 write)

write = sends, deletes, buys or posts

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

docguard_diagnosewrite action
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.
docguard_explain
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.
docguard_guardwrite action
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.
docguard_report
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.
docguard_score
Compute the project's CDD maturity score (0-100) with letter grade and per-category breakdown.
docguard_verify_claims
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.
docguard_verify_evidence
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.

Public scan report

scanner v0.1.10 · 2026-10-03 · same rubric, same numbers if you re-run it

no findings

Code scan140 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 1 days ago15/15
Maintainer identityregistry namespace matches repository owner; GitHub account older than a year8/10

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

How DocGuard compares

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

Safety score: 92/100; higher than 95% of 48,255 servers
Tools: 7; the typical server has 7
Tools that change things: 29%; typical: 0%. Fewer write tools means less an agent can break
GitHub stars: 31; more than 92% of 28,688 servers
Downloads a week: 1,305; more than 95% of 12,191 servers with a package

What its tools let an agent do: 5 read · 2 change

Install DocGuard in Claude Code, Cursor or VS Code

Runs npx -y docguard-cli on your machine. Read the scan report first; the gateway never runs local packages.

claude mcp add docguard -- npx -y docguard-cli

Add to Cursor

What the publisher says

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

🛡️ DocGuard

English · Português (BR) · Español

The enforcement layer for Spec-Driven Development.

Validate. Score. Enforce. Ship documentation that AI agents can actually use.

-green)

✨ See what DocGuard catches in 30 seconds — no install, no setup:

bash

npx docguard-cli demo

Runs against a baked-in sample project with intentional drift and shows you the findings + a clear path to fixing them.

What is DocGuard?
Why DocGuard?
Quick Start
Spec Kit Integration
Usage
Validators
Templates
AI Agent Support
Slash Commands
Examples
Testing
Enterprise Adoption

What is DocGuard?

DocGuard enforces Canonical-Driven Development (CDD) — a methodology where documentation is the source of truth, not an afterthought. AI writes the docs, DocGuard validates them.

DocGuard is an official GitHub Spec Kit community extension. It validates the artifacts that Spec Kit creates, ensuring your specs stay high-quality throughout the development lifecycle.

📖 Philosophy · 📋 CDD Standard · ⚖️ Comparisons · 🔬 Validation · 🗺️ Roadmap

Architecture

graph TD
    CLI["CLI Entry<br/>docguard.mjs"] --> Commands["Commands (23)"]
    Commands --> guard["guard"]
    Commands --> generate["generate"]
    Commands --> score["score"]
    Commands --> diagnose["diagnose"]
    Commands --> setup["setup wizard"]
    Commands --> other["diff · init · fix · trace · impact · sync · reconcile · retire · specs<br/>explain · memory · upgrade · agents · hooks · badge · ci · watch"]

Shortened. The full README is on GitHub.

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

DocGuard: common questions

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