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/stanislawherjan1/gdocs-comments-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/stanislawherjan1/gdocs-comments-mcp/gdocs-comments-mcp)<a href="https://agentmods.dev/mcp/stanislawherjan1/gdocs-comments-mcp/gdocs-comments-mcp"><img src="https://agentmods.dev/badge/mcp/stanislawherjan1/gdocs-comments-mcp/gdocs-comments-mcp.svg" alt="Measured on agentmods" height="20"></a>Grade A, and why
gdocs-comments-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.
Copies of this mod
1 near-identical copy found in the catalogue:
- gdocs-comments-mcp — 100% identical, 0 lines differ
What it actually says
{
"gdocs-comments-mcp": {
"command": "npx",
"args": [
"-y",
"gdocs-comments-mcp"
],
"env": {
"GDOCS_COMMENTS_PROFILE_DIR": "",
"GDOCS_COMMENTS_CDP_URL": ""
}
}
}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 · 13 lines scan A f8c8b9cd6fb4
gdocs-comments-mcp is an MCP server published in the GitHub repository stanislawherjan1/gdocs-comments-mcp (3 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
google-workspace-mcp
MCP server for Google Workspace: Docs, Sheets, Drive, Gmail, Calendar, Slides, and Forms. Runs locally from the google-workspace-mcp npm package.
mcp-server-excel
MCP server "mcp-server-excel" as configured in sbroenne/mcp-server-excel. Launched with Sbroenne.ExcelMcp.McpServer.
anytype-mcp
Official MCP server for Anytype API - your encrypted, local and collaborative wiki. Runs locally from the @anyproto/anytype-mcp npm package. Needs 1 environment variable to run.
adeu
MCP server "adeu" as configured in dealfluence/adeu. Runs locally from the adeu-server Python package.
mcp-outline
A Model Context Protocol (MCP) server for Outline (https://www.getoutline.com). Runs locally from the mcp-outline Python package. Needs 6 environment variables to run.
logisheets-mcp
An Excel-compatible spreadsheet engine for agents: deterministic formulas, block memory, real .xlsx. Runs locally from the logisheets-mcp npm package. Needs 1 environment variable to run.