DocGuard
Related Servers
Alternatives to DocGuard
- AlicenseAqualityCmaintenanceMCP server that indexes Markdown, Word, HTML, and PDF documents into a SQLite knowledge graph with CJK+Latin full-text search and cross-document reference tracking. Runs drift audits to surface stale policies, conflicting research claims, superseded ADRs, and undocumented code exports.108MIT
Related Servers
- AlicenseNot gradedqualityCmaintenanceA local MCP server that wraps the DocuGenerate API to generate documents (invoices, contracts, letters) from templates via natural language commands.MIT
- AlicenseAqualityAmaintenanceAn MCP server that exposes governance, trust-scoring, compliance, guardrail, cost, drift, and supply-chain scanning tools and resources to any MCP client over stdio, Streamable HTTP, or legacy HTTP+SSE. It lets agents route every tool call through a deterministic five-way decision (allow, redact, require approval, deny, or quarantine) with hash-chained evidence, human approval workflows, and in-agent trust gates for LangChain, LangGraph, and Google ADK.302MIT
- AlicenseAqualityAmaintenanceMCP server for DocsMint, an AI-native knowledge workspace. It gives AI agents scoped access to search, read, create, update and organize documents using hybrid retrieval and GraphRAG.22118Apache 2.0
- AlicenseNot gradedqualityAmaintenanceA stateless MCP server for composing, validating, auditing, and rendering consequential documents from a small semantic model.MIT
- FlicenseNot gradedqualityBmaintenanceLocal documentation search server for AI models using hybrid retrieval (phrase, keyword, vector). Provides MCP tools to search and fetch documentation from bundled or custom doc sets without any external API keys.-
- FlicenseNot gradedqualityDmaintenanceMCP server that exposes one or more documentation folders (Markdown, MDX, TXT) to AI agents, enabling listing, reading, and searching of documentation files.-
TDQS
Scored across 11 tools
Tools are mostly distinct, covering different stages of documentation compliance: scoring, guarding, reporting, verification, and doc inspection. However, docguard_guard and docguard_diagnose overlap (diagnose runs guard and filters output), and the verify_evidence/verify_claims pair could cause some uncertainty, though descriptions clarify the distinction.
All tools use a consistent docguard_ prefix with snake_case names. The pattern is predictable and readable, with no mixing of conventions.
With 11 tools, the set is well-scoped for a documentation compliance server. Each tool appears to earn its place by covering a specific capability without excessive redundancy.
The surface covers scoring, guarding, reporting, evidence verification, claim extraction, doc structure, section reading, task context, diagnosis, and code explanation. Minor gaps exist, such as no direct tool to list all validators or apply doc fixes, but core workflows are covered.