DocGuard

Name: DocGuard
Author: raccioly

by racciolyversion 0.40.5i★ –iRuns on your computer

Registry nameio.github.raccioly/docguard

Install

Overview

Description from the maker (original English)

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

PopNx MCP’s three pillars

These three are never merged into one score: opinions, measurements and popularity are different things.

User voiceiNo reviews yetReviews open together with accounts in a later step
Our basic checksi1 of 1 passedChecked from public information; code not scanned yet
UsageiNot measured yet★ –

What you can do with it

We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.

Connection: Runs on your computer
Transport: stdio
Category: Other

Install

Pick the AI app you use, then copy the settings.

Before you install

Basic checks: 1 of 1 passed
Runs on your computer with your user’s permissions (files, network, apps).
The registry lists no key to fill in.

You need

npmNode.js installed (for the npx command)

Which app do you use?

ClaudeClaude CodeCursorVS CodeChatGPT

Pick your app above. We remember it, so next time the button says “Install in …”.

Open Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json

{
  "mcpServers": {
    "docguard": {
      "command": "npx",
      "args": [
        "-y",
        "docguard-cli",
        "mcp"
      ]
    }
  }
}

Run this in your terminal

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

Open in Cursor

Or copy the settings yourself

Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json

{
  "mcpServers": {
    "docguard": {
      "command": "npx",
      "args": [
        "-y",
        "docguard-cli",
        "mcp"
      ]
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

Open in VS Code

Or copy the settings yourself

Paste into .vscode/mcp.json in your project

{
  "servers": {
    "docguard": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "docguard-cli",
        "mcp"
      ]
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

This one runs on your computer, and ChatGPT can only connect to servers on the internet. Pick another app.

Your choice stays on this device in a cookie; no account needed.

These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.

What it can do

Runs on your computer; the tool list appears in your AI app after you install it.

Basic checksi

We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 7, 2026

✓ Pass
Maker matches the repo
The registry name was verified with the GitHub account raccioly, which owns the repo
… Not checked yet
Still maintained
We have not read this repo from GitHub yet
… Not checked yet
Has a licence
We have not read this repo from GitHub yet
– Not applicable
Endpoint responds
This one runs on your computer; there is no internet endpoint
– Not applicable
Sign-in with OAuth
Runs on your computer and uses local settings instead
… Not checked yet
No hidden instructions in tool descriptions
Runs on your computer; we can only read tool lists from internet endpoints

Compared with others in Otheri

More stars than 0% of the other 32673 servers in this category
Published to the registry more recently than 43% of the other 32673 servers in this category
Basic checks equal to or better than 100% of the other 32673 servers in this category

Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.

Common questions

Is DocGuard safe?

It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.

What keys or codes does it need?

The registry does not list a required key, though some servers ask you to sign in on first use.

Does it run on my computer or in the cloud?

It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).

Is it still maintained?

The GitHub repo last changed –, and the latest version (0.40.5) reached the registry 2 months ago.

Which apps can use it?

Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Node.js on your computer.

What can I use instead?

In the same category: Spec Driven Development, Remote Desktop Commander, Systemdox

Alternatives

Servers in the same category from other makers, sorted by stars.

Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi

Spec Driven Development

by formulahendry

MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.

Runs on your computer★ 440MITUpdated 14 months ago

Install

Remote Desktop Commander

by desktop-commander

Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.

Runs in the cloud★ 211Updated 2 days ago

Install

Systemdox

by puglieseweb

Your architecture in your agents' context: checks, specs, ADRs and docs over MCP, at write time.

Runs on your computerUpdated today

Install

README from the maker

Open the README

Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.

🛡️ 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.

📚 [Documentation](https://raccioly.github.io/docguard/): Installation · Existing projects · Spec Kit · CI · Languages and frameworks · Coding agents · Finding codes · Troubleshooting

What is DocGuard?
Why DocGuard?
Quick Start
Spec Kit Integration
Usage
Validators
Reading a finding
Templates
AI Agent Support
Slash Commands
Examples
Testing
Enterprise Adoption
CI/CD Integration
What's New
File Structure
Configuration
Research Credits

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.

Traditional Development	Canonical-Driven Development
Code first, docs maybe	Docs first, code conforms
Docs rot silently	Drift is tracked and enforced
Docs are optional	Docs are required and validated
One AI agent, one context	Any agent, shared context via canonical docs

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.

🧭 [How it works (10-page brief)](https://raccioly.github.io/docguard/docguard-explained.html) (PDF) · 📖 [Philosophy](PHILOSOPHY.md) · 📋 [CDD Standard](STANDARD.md) · ⚖️ [Comparisons](https://github.com/raccioly/docguard/blob/main/COMPARISONS.md) · 🔬 [Validation](https://github.com/raccioly/docguard/blob/main/VALIDATION.md) · 🗺️ [Roadmap](https://github.com/raccioly/docguard/blob/main/ROADMAP.md)

Architecture

graph TD

CLI["CLI Entry docguard.mjs"] --> Commands["Commands (28)"] 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 · ignore explain · memory · upgrade · agents · hooks · badge · ci · watch"]

guard --> Validators["Validators (36)"] generate --> Scanners["Scanners (4) routes · schemas · doc-tools · speckit"] score --> Scoring["Weighted Scoring 8 categories"] diagnose --> Validators diagnose --> AIPrompts["AI-Ready Fix Prompts"]

Validators --> Output["Output"] Scanners --> Output Scoring --> Output Output --> Terminal["Terminal"] Output --> JSON["JSON"] Output --> Badge["Badge"]

style CLI fill:#2d5016,color:#fff style Validators fill:#1a3a5c,color:#fff style Scanners fill:#1a3a5c,color:#fff style Output fill:#5c3a1a,color:#fff

Distribution: Node.js core (npm) · Python wrapper (PyPI) · GitHub Action (action.yml) · Spec Kit Extension (ZIP)

Why DocGuard?

DocGuard checks declared documentation facts against repository evidence and gives agents structured repair tasks. Deterministic checks cover supported facts, references, and generated sections. Human-authored requirements and architectural decisions retain their authority when implementation diverges.

A guard result describes the checks performed. The CDD grade measures structural maturity. Exact declarations in .docguard-evidence.json can verify selected statements against current local evidence; every other statement remains unverified. Coverage and unresolved claims remain visible, so teams can choose an appropriate enforcement policy.

Research motivates evaluation of this approach. A 2026 study found that repository context files did not generally improve task success and increased inference cost in its evaluated settings. It also found agents generally followed the instructions. These results support testing concise, relevant context and measuring actual task outcomes; they do not establish DocGuard's effectiveness. Evaluating AGENTS.md, revised June 2026.

The current roadmap prioritizes accurate detection, reproducible evidence, document lifecycle management, and contributor-supplied regression cases. Released plans and superseded specifications are removed from active AI context and remain recoverable from Git.

⚡ Quick Start

Package naming: this repo is raccioly/docguard; the published package is `docguard-cli` on both npm and PyPI; the installed command is docguard. Same project — the -cli suffix is just the registry name. The package runs no install scripts, so npm i -g docguard-cli --ignore-scripts is equivalent.

Node.js (npm)

# No install needed — run directly

npx docguard-cli diagnose

Or install globally

npm i -g docguard-cli docguard diagnose

Python (PyPI)

pip install docguard-cli

docguard diagnose

Note: The Python package is a thin wrapper that delegates to npx. Node.js 18+ is required on the system.

Docker (MCP server)

The MCP server ships as a container image on GHCR — no Node.js install required. Public image, so no authentication is needed to pull it:

# Run the MCP server against the current directory

docker run -i --rm -v "$PWD":/workspace ghcr.io/raccioly/docguard:latest

The entrypoint is the stdio MCP transport: stdout is the JSON-RPC channel, so keep every other output off it. Mount the project you want inspected at /workspace; tools inspect it by default, and a projectDir in a tool call must be /workspace or a directory inside it (add --root after the image name to serve another mounted tree).

Pin a version rather than tracking latest in CI:

docker run -i --rm -v "$PWD":/workspace ghcr.io/raccioly/docguard:0.34.9

The server is read-only: it only reads the mounted project.

More ways to integrate

pre-commit — changed-only guard on every commit:

  repos:

repo: https://github.com/raccioly/docguard rev: v0.46.0 hooks: [{ id: docguard-guard }] # docguard-guard-full for pre-push

- **MCP** (Claude, Cursor, any MCP client) — `claude mcp add docguard -- npx -y docguard-cli mcp`; read-only tools to check docs (guard, score, diagnose, …) and to navigate them one bounded section at a time — the full list is in [docs/ai-integration.md](docs/ai-integration.md). Registry manifest ships in-repo (`server.json`, Smithery-ready).

GitLab CI — component staged at templates/ci/gitlab-component.yml (guard/score/ci job with a SARIF artifact).
Homebrew — brew install raccioly/tap/docguard. The release workflow renders the formula template in packaging/homebrew/ from the published npm tarball and pushes it to the tap.

Core Workflow

# 1. Initialize docs for your project

npx docguard-cli init

2. Or reverse-engineer docs from existing code

npx docguard-cli generate

3. AI diagnoses issues and generates fix prompts

npx docguard-cli diagnose

4. Validate — use as CI gate

npx docguard-cli guard

5. Check maturity score

npx docguard-cli score

The AI Loop

diagnose  →  AI reads prompts  →  AI fixes docs  →  guard verifies

↑ ↓ └───────────────── issues found? ←──────────────────────┘

diagnose is the primary command. It runs all validators, maps every failure to an AI-actionable fix prompt, and outputs a remediation plan. Your AI agent runs it, fixes the docs, and runs guard to verify.

Mechanical vs. agent fixes

DocGuard splits drift into two kinds and is explicit about which is which:

Kind	Example	How it's fixed
Mechanical (deterministic)	An endpoint documented in `API-REFERENCE.md` that the OpenAPI spec confirms is gone	`docguard fix --write` deletes the row + detail block itself — no AI
Agent (needs judgment)	Rewriting an X-Ray prose section as CloudWatch; writing a new endpoint's request/response	Routed to an AI agent via `diagnose` / `fix --doc` prompts

docguard fix --write only touches docs marked (override with --force), is idempotent, and prints exactly what changed. Prose stays with the agent.

Continuous documentation workflow

guard ──▶ fix --write (mechanical, auto) ──▶ guard ──▶ diagnose (agent prompts for the rest)

CI / pre-commit: docguard hooks --type pre-commit --auto-fix installs a hook that applies mechanical fixes, re-stages the docs, then runs guard; anything left is surfaced as agent prompts.
Agent-driven: docguard diagnose --auto scaffolds missing docs and applies mechanical fixes, then emits prompts for the content rewrites that remain.
JSON for automation: guard/diagnose --format json include a mechanicalFixes array and tag each issue mechanical vs agent, so an agent can apply or delegate precisely.

☁️ AWS AI-DLC Integration

DocGuard reads AWS AI-DLC workspaces on its own: traceability targets that no longer exist, gaps left in completed stages, deliverables removed afte

Only the beginning is shown; read the rest in the repo

DocGuard

Overview

PopNx MCP’s three pillars

What you can do with it

Install

Before you install

What it can do

Basic checksi

Maker matches the repo

Still maintained

Has a licence

Endpoint responds

Sign-in with OAuth

No hidden instructions in tool descriptions

Compared with others in Otheri

Common questions

Alternatives

Spec Driven Development

Remote Desktop Commander

Systemdox

README from the maker

🛡️ DocGuard

Table of Contents

What is DocGuard?

Architecture

Why DocGuard?

⚡ Quick Start

Node.js (npm)

Or install globally

Python (PyPI)

Docker (MCP server)

More ways to integrate

Core Workflow

2. Or reverse-engineer docs from existing code

3. AI diagnoses issues and generates fix prompts

4. Validate — use as CI gate

5. Check maturity score

The AI Loop

Mechanical vs. agent fixes

Continuous documentation workflow

☁️ AWS AI-DLC Integration