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-watermark/GroupDocs.Watermark.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-watermark/groupdocs.watermark.mcp/groupdocs-watermark-dev)<a href="https://agentmods.dev/mcp/groupdocs-watermark/groupdocs.watermark.mcp/groupdocs-watermark-dev"><img src="https://agentmods.dev/badge/mcp/groupdocs-watermark/groupdocs.watermark.mcp/groupdocs-watermark-dev.svg" alt="Measured on agentmods" height="20"></a>Grade A, and why
groupdocs-watermark-dev 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 today.
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.
This is a copy
86% identical to groupdocs-metadata-dev — 4 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
What it actually says
{
"groupdocs-watermark-dev": {
"type": "stdio",
"command": "dotnet",
"args": [
"run",
"--project",
"src/GroupDocs.Watermark.Mcp",
"-c",
"Release",
"--no-launch-profile"
],
"env": {
"GROUPDOCS_MCP_STORAGE_PATH": "${input:storage_path}",
"DOTNET_CLI_TELEMETRY_OPTOUT": "1",
"DOTNET_NOLOGO": "1"
}
}
}What else mcp.json configures
This page is one entry in a file that holds 2. Installing the file brings all of them; each is measured and scanned on its own page.
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.
- today First seen · 19 lines scan A 6a1033b51341
groupdocs-watermark-dev is an MCP server published in the GitHub repository groupdocs-watermark/GroupDocs.Watermark.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. It is 86% identical to groupdocs-metadata-dev, differing in 4 lines, and is treated as a copy.
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.