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-viewer/GroupDocs.Viewer.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/groupdocs-viewer/groupdocs.viewer.mcp/mcp-groupdocs-viewer-mcp)<a href="https://agentmods.dev/mcp/groupdocs-viewer/groupdocs.viewer.mcp/mcp-groupdocs-viewer-mcp"><img src="https://agentmods.dev/badge/mcp/groupdocs-viewer/groupdocs.viewer.mcp/mcp-groupdocs-viewer-mcp.svg" alt="Measured on agentmods" height="20"></a>Grade A, and why
groupdocs-viewer-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 7d 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-viewer-mcp": {
"command": "GroupDocs.Viewer.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.
- 7d ago First seen · 11 lines scan A d289d12e1031
groupdocs-viewer-mcp is an MCP server published in the GitHub repository groupdocs-viewer/GroupDocs.Viewer.Mcp (0 stars, last pushed yesterday), 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-metadata-dev
MCP server "groupdocs-metadata-dev" as configured in groupdocs-metadata/GroupDocs.Metadata.Mcp. Launched with dotnet run --project src/GroupDocs.Metadata.Mcp -c Release --no-launch-profile. Needs 3 environment variables to run.
groupdocs-metadata-mcp
MCP server "groupdocs-metadata-mcp" as configured in groupdocs-metadata/GroupDocs.Metadata.Mcp. Launched with GroupDocs.Metadata.Mcp. Needs 3 environment variables to run.
groupdocs-metadata
MCP server "groupdocs-metadata" as configured in groupdocs-metadata/GroupDocs.Metadata.Mcp. Launched with dnx GroupDocs.Metadata.Mcp --yes. Needs 1 environment variable to run.
groupdocs-parser-mcp
MCP server "groupdocs-parser-mcp" as configured in groupdocs-parser/GroupDocs.Parser.Mcp. Runs in Docker (ghcr.io/groupdocs-parser/parser-net-mcp:26.7.3). Needs 3 environment variables to run.
groupdocs-signature-mcp
MCP server "groupdocs-signature-mcp" as configured in groupdocs-signature/GroupDocs.Signature.Mcp. Launched with GroupDocs.Signature.Mcp. Needs 3 environment variables to run.
groupdocs-redaction-mcp
MCP server "groupdocs-redaction-mcp" as configured in groupdocs-redaction/GroupDocs.Redaction.Mcp. Launched with GroupDocs.Redaction.Mcp. Needs 3 environment variables to run.