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.
git clone --depth 1 https://github.com/koraynar/doc-extract-mcpWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/mcp/koraynar/doc-extract-mcp/doc-extract-mcp)<a href="https://agentmods.dev/mcp/koraynar/doc-extract-mcp/doc-extract-mcp"><img src="https://agentmods.dev/badge/mcp/koraynar/doc-extract-mcp/doc-extract-mcp/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/mcp/koraynar/doc-extract-mcp/doc-extract-mcp"><img src="https://agentmods.dev/badge/mcp/koraynar/doc-extract-mcp/doc-extract-mcp.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
doc-extract-mcp 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 8d 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.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
What it actually says
{
"doc-extract-mcp": {
"command": "uvx",
"args": [
"doc-extract-mcp"
]
}
}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.
- 8d ago First seen · 8 lines scan A ad1214a2fda4
doc-extract-mcp is an MCP server published in the GitHub repository koraynar/doc-extract-mcp (0 stars, last pushed 11d ago), licensed MIT. Its token cost is not measured: an MCP server costs its tool schemas, not its config file. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other mcp servers, from other repositories
frame-check
Frame Check MCP server: deterministic structural framing analysis for AI-generated documents, with default-on frame-divergence block per FRAMEDIVERGENCECONTRACTv1 c1.0. MCP surface delegates V4.2 judgment to the caller's agent model; zero Frame Check LLM cost per query. Runs locally from the frame-check-mcp Python…
mcp-server-excel
MCP server "mcp-server-excel" as configured in sbroenne/mcp-server-excel. Launched with Sbroenne.ExcelMcp.McpServer.
mcp-tools-py
MCP server "mcp-tools-py" as configured in MarcusJellinghaus/mcp-workspace. Launched with ${MCP_CODER_VENV_PATH}\mcp-tools-py.exe --project-dir ${MCP_CODER_PROJECT_DIR} -. Needs 1 environment variable to run.
seekstone
Filesystem-direct Obsidian MCP server — search and edit your vault with low context-tax. Runs locally from the seekstone npm package. Needs 1 environment variable to run.
itglue-mcp
MCP server "itglue-mcp" as configured in WYRE-AI/itglue-mcp. Runs in Docker (ghcr.io/wyre-ai/itglue-mcp:v1.16.5). Needs 6 environment variables to run.
evc-relay
MCP server for reading and writing Obsidian vault documents via EVC Team Relay. Runs locally from the evc-team-relay-mcp Python package. Needs 3 environment variables to run.