io.github.stanislawherjan1/gdocs-comments-mcp
NPM · GDOCS-COMMENTS-MCP · SCANNED SEP 20
Add inline, range-anchored comments to Google Docs - the one comment op the Google APIs can't do.
Available components
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security98
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- 31 of 96 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 69 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability71
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 481 tokens (~240/item across 2 items; 2 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management90
- Stability observed for 27 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 2 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 3 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
How do I install the io.github.stanislawherjan1/gdocs-comments-mcp server?
io.github.stanislawherjan1/gdocs-comments-mcp runs locally as an npm package, launched with npx -y gdocs-comments-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · gdocs-comments-mcp
claude mcp add stanislawherjan1-gdocs-comments-mcp -- npx -y gdocs-comments-mcp
{
"mcpServers": {
"stanislawherjan1-gdocs-comments-mcp": {
"command": "npx",
"args": [
"-y",
"gdocs-comments-mcp"
]
}
}
} {
"servers": {
"stanislawherjan1-gdocs-comments-mcp": {
"command": "npx",
"args": [
"-y",
"gdocs-comments-mcp"
]
}
}
} codex mcp add stanislawherjan1-gdocs-comments-mcp -- npx -y gdocs-comments-mcp
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"stanislawherjan1-gdocs-comments-mcp": {
"type": "local",
"command": [
"npx",
"-y",
"gdocs-comments-mcp"
],
"enabled": true
}
}
} openclaw mcp add stanislawherjan1-gdocs-comments-mcp --command npx --arg -y --arg gdocs-comments-mcp
mcp_servers:
stanislawherjan1-gdocs-comments-mcp:
command: "npx"
args: ["-y", "gdocs-comments-mcp"] {
"McpServers": {
"stanislawherjan1-gdocs-comments-mcp": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"gdocs-comments-mcp"
]
}
}
} assistant mcp add stanislawherjan1-gdocs-comments-mcp -t stdio -c npx -a -y gdocs-comments-mcp
{
"mcpServers": {
"stanislawherjan1-gdocs-comments-mcp": {
"command": "npx",
"args": [
"-y",
"gdocs-comments-mcp"
]
}
}
} Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 20 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.
- 19 Sept 26 0
- Security disclosure: unverified → fail ▼ functional
- 18 Sept 26 +1
- Security disclosure: fail → unverified ▼ functional
- 17 Sept 26 −3
- Stability: pass → 0.80 functional
- 16 Sept 26 0
- Stability: 0.97 → pass security
- 15 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 13 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.
- 11 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 20 Sept 2026 · Analysed npm/gdocs-comments-mcp@0.1.1
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Background: How many MCP packages publish verified provenance →
Dependencies 96 packages
| Packages resolved | 96 |
|---|---|
| Stale | 31 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
add_comment ~339
Add an inline comment anchored to a specific text fragment in a Google Doc (the comment is pinned to that exact phrase, like selecting text and commenting on it by hand). USE THIS WHEN the user wants to leave feedback, notes, questions, edits, or review comments on specific passages of a Google Doc — e.g. "review this doc and comment on the weak spots", "leave a comment on that sentence", "add editorial feedback inline". This is the ONLY way to place anchored comments: the Google Docs and Drive APIs cannot anchor a comment to a text range, so this drives a real logged-in Docs session in a browser. Do NOT use for list/reply/resolve/delete — those work over the Drive API. Requires a one-time `npx gdocs-comments-mcp login` by the human operator (you cannot log in for them). Omit find_text to add a general, unanchored comment on the document instead. Returns only { ok, anchored, occurrence_used, verified } — never document content.
| Name | Type | Req | Description |
|---|---|---|---|
| comment_text | string | yes | The comment body. Plain text; newlines allowed. |
| doc | string | yes | Google Docs document id, or the full docs.google.com/document/d/<id>/edit URL. |
| find_text | string | – | Exact single-line text fragment to anchor the comment to. Must match the doc text exactly; pick a fragment unique enough to identify the spot (or pass occurrence). Omit for a general, unanchored comm… |
| occurrence | integer | – | When find_text appears multiple times, anchor to the N-th match (1-based). Default: 1. |
No output schema declared.
No examples provided.
check_connection ~62
Check whether the Google session behind this server is usable: launches/attaches the browser and probes docs.google.com. Returns { connected, mode }. Call this to diagnose failures; if connected=false, ask the operator to run `npx gdocs-comments-mcp login`.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
What is the io.github.stanislawherjan1/gdocs-comments-mcp server?
io.github.stanislawherjan1/gdocs-comments-mcp is listed in the public MCP registry as io.github.stanislawherjan1/gdocs-comments-mcp. Add inline, range-anchored comments to Google Docs - the one comment op the Google APIs can't do. This page covers its npm package (gdocs-comments-mcp).
Is the io.github.stanislawherjan1/gdocs-comments-mcp server safe to use?
io.github.stanislawherjan1/gdocs-comments-mcp scores 82 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 20 September 2026. It declares no install or post-install scripts. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the io.github.stanislawherjan1/gdocs-comments-mcp server expose?
io.github.stanislawherjan1/gdocs-comments-mcp exposes 2 tools: add_comment, check_connection. Their descriptions and schemas cost roughly 401 tokens of context every time the server is loaded.
Is the io.github.stanislawherjan1/gdocs-comments-mcp server still maintained?
io.github.stanislawherjan1/gdocs-comments-mcp is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the io.github.stanislawherjan1/gdocs-comments-mcp server under?
io.github.stanislawherjan1/gdocs-comments-mcp declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.