Log inSubmit server
Docguard logo

Docguard

by raccioly

Deterministically checks project documentation against code through five read-only MCP tools.

InstallRepositoryWebsite
Full README Compare alternatives Embed widget Claim this listing

Install Docguard

Pick your client, then add it in one click or paste the config.

STDIONode.js
~/Library/Application Support/Claude/claude_desktop_config.json
claude_desktop_config.json
{
  "mcpServers": {
    "raccioly-docguard": {
      "command": "npx",
      "args": [
        "-y",
        "docguard-cli"
      ]
    }
  }
}

Settings → Developer → Edit Config, merge this into mcpServers, then fully quit and reopen Claude Desktop.

Install not yet sandbox-tested— we haven't run this command through our automated sandbox yet. Not a red flag; we're working through the catalog.

Overview

The raccioly/docguard MCP server compares a project's canonical documentation with local code and reports documentation drift using deterministic checks. It exposes five read-only stdio tools: guard, score, explain, verify-claims, and diagnose. Findings include stable codes and suggested fixes, while score measures documentation maturity and diagnose produces AI-ready repair prompts. Use it when agents need verified repository context or when documentation checks should run without modifying project files.

Use cases

  • Validate canonical docs against repository code
  • Score documentation maturity before an AI task
  • Explain stable drift findings to an agent
  • Verify selected claims with local evidence
  • Diagnose issues and generate repair prompts

Key features

  • Five read-only MCP tools
  • Deterministic documentation-drift checks
  • Stable finding codes with suggested fixes
  • Canonical-claim verification
  • Documentation maturity scoring
  • AI-ready diagnostic prompts

Security & health

What it can reach and how reliably it runs — from our own checks, not the maintainer’s claims.

ActiveLast checked 1d ago

Recent health check succeeded.

10/13 checks healthy over the last 79d

Supply-chain signal

No high-severity advisories surfaced by our automated scan.

Critical 0High 0Medium 0Low 0

Scanned 5d ago via OSV.dev · docguard-cli (npm)

Adoption & maintenance

Factual signals from GitHub, npm, and our automated checks — not a rating.

GitHub stars32Stargazers on the source repository.
npm downloads6.7kPackage downloads in the last 30 days.
Last commit9d agoMost recent push to the default branch.
Directory activity4 viewsConfig copies, upvotes, and views on AllMCPs.

How Docguard works

What raccioly/docguard MCP server does

The raccioly/docguard MCP server checks whether a project's canonical documentation matches evidence in its codebase. It is intended for documentation-led development and for repositories where AI agents rely on specifications, claims, references, and generated sections as working context.

Checks are deterministic rather than based on an LLM's interpretation. Findings have stable codes and include suggested fixes, giving an agent or developer a repeatable way to identify and address drift. The server also keeps unresolved or unverified claims visible instead of treating them as confirmed.

The project is listed in the Developer Tools category and is available as the docguard-cli package. The repository describes it as a community extension for GitHub Spec Kit, where it validates artifacts produced during the specification workflow.

How it works

The MCP process communicates over stdio. It reads the project supplied to a tool call, examines documentation and local repository evidence, and returns structured results without writing to the project. The five exposed tools are:

  • guard validates documentation and can serve as an enforcement check.
  • score calculates a documentation maturity grade.
  • explain provides details about findings or checks.
  • verify-claims checks selected declarations against available local evidence.
  • diagnose analyzes issues and returns prompts intended to help an AI repair documentation.

The underlying command-line project contains validators for supported facts, references, and generated sections. Exact declarations can be placed in .docguard-evidence.json for verification against current local evidence; statements without that evidence remain unverified.

Setup and configuration

Run the server directly with Node.js using npx -y docguard-cli mcp. Node.js 18 or newer is required. A client configuration can start that command as a stdio MCP server. The README specifically mentions Claude and Cursor as MCP clients.

A container image is also published at ghcr.io/raccioly/docguard:latest. Mount the repository at /workspace, run the container with an interactive stdin, and pass /workspace as projectDir in tool calls or use the default working directory. The container's stdout is reserved for the JSON-RPC channel. Pin a version instead of using latest when running it in CI.

Tools and capabilities

The raccioly/docguard MCP server is useful for checking documentation before an AI agent acts on repository context, reviewing canonical specifications against implementation evidence, and exposing stable findings to CI or repair workflows. Its read-only behavior makes it suitable for inspecting a mounted working tree without allowing the MCP process to alter files.

The broader CLI also supports commands such as init, generate, diagnose, guard, and score, but the MCP interface exposes only the five tools listed above. The package is distributed through npm, with a Python wrapper also available; the Python wrapper delegates to npx and still requires Node.js.

Limitations and notes

Validation only covers supported facts and available repository evidence. A claim is not automatically verified merely because it appears in documentation. The server does not edit files, apply suggested fixes, or replace human judgment about requirements and architectural decisions. Its transport is stdio, so unrelated output must not be written to stdout when it is used as an MCP process.

Read the full README View source on GitHub

Reviews

No reviews yet — be the first to share how it worked for you.

Frequently Asked Questions about Docguard

raccioly/docguard is an MCP server that connects AI agents to a local project's canonical documentation and codebase. Its main tools are guard, score, explain, verify-claims, and diagnose, which deterministically check documentation drift, assess maturity, explain findings, verify claims, and produce repair prompts without modifying project files.

Run it with `npx -y docguard-cli mcp` as a stdio MCP process. Node.js 18 or newer is required. You can also run the published GHCR container, mounting the project at `/workspace` and passing that path as `projectDir`.

Yes, raccioly/docguard works with Cursor through its stdio MCP interface.

Yes, the MCP server is read-only and does not modify the inspected project. It reads documentation and local code evidence, then returns validation results, scores, explanations, claim checks, or diagnostic prompts.

Related MCP servers

All in Developer Tools All alternatives
Add a badge to your READMEShow it’s listed — live SVG, Markdown or HTML.

AllMCPs Directory Badge

Full Badge Customizer

Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.

Badge Style:
Live Dynamic SVG PreviewDocguard AllMCPs Directory Badge
Markdown (GitHub README)
[![AllMCPs](https://allmcps.com/api/badge/raccioly-docguard?style=directory)](https://allmcps.com/mcp/raccioly-docguard)
HTML Embed
<a href="https://allmcps.com/mcp/raccioly-docguard"><img src="https://allmcps.com/api/badge/raccioly-docguard?style=directory" alt="Docguard on AllMCPs" /></a>