docs-reader

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Security

Grade A, and why

docs-reader scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 3d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

tests/fixtures/clean-apps/ai-layer-clean/.mcp.json · 23 lines

What it actually says

{
  "docs-reader": {
    "command": "node",
    "args": [
      "./mcp-docs-server.js"
    ],
    "permissions": [
      "file_read"
    ],
    "tools": [
      {
        "name": "read_docs",
        "description": "Reads a markdown file from the local docs directory and returns its plain text contents.",
        "parameters": [
          {
            "name": "path",
            "description": "Relative path within the docs directory to read."
          }
        ]
      }
    ]
  }
}

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

Related

Other mcp servers, from other repositories