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.
npx agentmods add mcp/tg-tool/google-sheets-write-mcp-server/sheets-write-mcp-servergit clone --depth 1 https://github.com/tg-tool/google-sheets-write-mcp-serverWrote 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/tg-tool/google-sheets-write-mcp-server/sheets-write-mcp-server)<a href="https://agentmods.dev/mcp/tg-tool/google-sheets-write-mcp-server/sheets-write-mcp-server"><img src="https://agentmods.dev/badge/mcp/tg-tool/google-sheets-write-mcp-server/sheets-write-mcp-server.svg" alt="Measured on agentmods" height="20"></a>Grade A, and why
sheets-write-mcp-server 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 3d 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
{ "sheets-write-mcp-server": { "command": "uvx", "args": [ "sheets-write-mcp-server" ] } }
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.
- 3d ago First seen · 8 lines scan A ca6f81e8d23d
sheets-write-mcp-server is an MCP server published in the GitHub repository tg-tool/google-sheets-write-mcp-server (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
gsheets-mcp
Node.js MCP server for Google Sheets — all 19 tools, service account auth, folder support. Runs locally from the gsheets-mcp npm package.
servalsheets
MCP server "servalsheets" as configured in khill1269/servalsheets. Runs locally from the servalsheets npm package.
gsheets-mcp
Standalone MCP server for Google Sheets operations. Runs locally from the gsheets-mcp Python package.
sheets-finance-mcp
MCP server "sheets-finance-mcp" as configured in henrysouchien/sheets-finance-mcp. Runs locally from the sheets-finance-mcp Python package.
google-sheets
Query your Google Sheets as structured JSON: list sheets and tabs, read schemas, filter rows. Remote server at pastesheet.com.
pastesheet
MCP server "pastesheet", hosted remotely at pastesheet.com, as configured in 199ocero/google-sheets-mcp.