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/groupdocs-markdown/GroupDocs.Markdown.McpInstalling this writes the configuration, not the program: `GroupDocs.Markdown.Mcp` has to be on your PATH already, or the server will not start.
Wrote 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/groupdocs-markdown/groupdocs.markdown.mcp/mcp-groupdocs-markdown-mcp)<a href="https://agentmods.dev/mcp/groupdocs-markdown/groupdocs.markdown.mcp/mcp-groupdocs-markdown-mcp"><img src="https://agentmods.dev/badge/mcp/groupdocs-markdown/groupdocs.markdown.mcp/mcp-groupdocs-markdown-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/groupdocs-markdown/groupdocs.markdown.mcp/mcp-groupdocs-markdown-mcp"><img src="https://agentmods.dev/badge/mcp/groupdocs-markdown/groupdocs.markdown.mcp/mcp-groupdocs-markdown-mcp.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
groupdocs-markdown-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 1mo 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
{
"groupdocs-markdown-mcp": {
"command": "GroupDocs.Markdown.Mcp",
"args": [],
"env": {
"GROUPDOCS_MCP_STORAGE_PATH": "{storage_path}",
"GROUPDOCS_MCP_OUTPUT_PATH": "{output_path}",
"GROUPDOCS_LICENSE_PATH": "{license_path}"
}
}
}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.
- 1mo ago First seen · 11 lines scan A e06a1163daf0
groupdocs-markdown-mcp is an MCP server published in the GitHub repository groupdocs-markdown/GroupDocs.Markdown.Mcp (0 stars, last pushed 1mo 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
groupdocs-conversion-mcp
MCP server "groupdocs-conversion-mcp" as configured in groupdocs-conversion/GroupDocs.Conversion.Mcp. Launched with GroupDocs.Conversion.Mcp. Needs 3 environment variables to run.
groupdocs-total-mcp
MCP server "groupdocs-total-mcp" as configured in groupdocs-total/GroupDocs.Total.Mcp. Runs in Docker (ghcr.io/groupdocs-total/total-net-mcp:26.7.3). Needs 3 environment variables to run.
groupdocs-merger-mcp
MCP server "groupdocs-merger-mcp" as configured in groupdocs-merger/GroupDocs.Merger.Mcp. Launched with GroupDocs.Merger.Mcp. Needs 3 environment variables to run.
groupdocs-watermark-mcp
MCP server "groupdocs-watermark-mcp" as configured in groupdocs-watermark/GroupDocs.Watermark.Mcp. Launched with GroupDocs.Watermark.Mcp. Needs 3 environment variables to run.
groupdocs-watermark
MCP server "groupdocs-watermark" as configured in groupdocs-watermark/GroupDocs.Watermark.Mcp. Launched with dnx GroupDocs.Watermark.Mcp --yes. Needs 1 environment variable to run.
groupdocs-annotation-mcp
MCP server "groupdocs-annotation-mcp" as configured in groupdocs-annotation/GroupDocs.Annotation.Mcp. Launched with GroupDocs.Annotation.Mcp. Needs 3 environment variables to run.