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/ringo380/claude-google-sheets-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/ringo380/claude-google-sheets-mcp/google-sheets)<a href="https://agentmods.dev/mcp/ringo380/claude-google-sheets-mcp/google-sheets"><img src="https://agentmods.dev/badge/mcp/ringo380/claude-google-sheets-mcp/google-sheets.svg" alt="Measured on agentmods" height="20"></a>Grade A, and why
google-sheets 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
{
"google-sheets": {
"command": "/path/to/claude-google-sheets-mcp/venv/bin/python",
"args": [
"-m",
"claude_google_sheets.server",
"--credentials-dir",
"/path/to/your/credentials"
]
}
}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 b91ea0270376
google-sheets is an MCP server published in the GitHub repository ringo380/claude-google-sheets-mcp (19 stars, last pushed 11mo 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-30.
Other mcp servers, from other repositories
mcp-office-excel
Local-first MCP servers for Microsoft Office — Excel, PowerPoint, and Word automation via the Model Context Protocol. Runs on Windows. Runs locally from the mcp-office Python package. Needs 4 environment variables to run.
mcp-office-powerpoint
Local-first MCP servers for Microsoft Office — Excel, PowerPoint, and Word automation via the Model Context Protocol. Runs on Windows. Runs locally from the mcp-office Python package. Needs 3 environment variables to run.
mcp-office-word
Local-first MCP servers for Microsoft Office — Excel, PowerPoint, and Word automation via the Model Context Protocol. Runs on Windows. Runs locally from the mcp-office Python package. Needs 3 environment variables to run.
mcp-google-sheets-server
Advanced MCP Server for Google Sheets - 40+ tools for complete sheet management, charts, and formatting. Runs locally from the mcp-google-sheets-server npm package.
servalsheets
MCP server "servalsheets" as configured in khill1269/servalsheets. Runs locally from the servalsheets npm package.
localdata-mcp
MCP server for databases, spreadsheets, structured files, and directed graphs. Runs locally from the localdata-mcp Python package.