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/salviz/google-mcp-server/google-mcp-servergit clone --depth 1 https://github.com/salviz/google-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/salviz/google-mcp-server/google-mcp-server)<a href="https://agentmods.dev/mcp/salviz/google-mcp-server/google-mcp-server"><img src="https://agentmods.dev/badge/mcp/salviz/google-mcp-server/google-mcp-server.svg" alt="Measured on agentmods" height="20"></a>Grade A, and why
google-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 5d 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-mcp-server": { "command": "npx", "args": [ "-y", "@salviz/google-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.
- 5d ago First seen · 9 lines scan A a2440460900a
google-mcp-server is an MCP server published in the GitHub repository salviz/google-mcp-server (0 stars, last pushed 6mo 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 integration. Runs locally from the google-workspace-mcp Python package.
gws-mcp
MCP server "gws-mcp" as configured in samuel-stidham/gws-mcp. Runs locally from the gws-mcp Python package.
gws-mcp-server
Google Workspace as 39 curated MCP tools: Gmail, Calendar, Drive, Sheets, Docs, and Tasks. Runs locally from the gws-mcp-server npm package.
google-workspace-mcp
MCP server "google-workspace-mcp" as configured in adelaidasofia/google-workspace-mcp. Launched with https://github.com/adelaidasofia/google-workspace-mcp/releases/download/v0.1.0/g. Needs 2 environment variables to run.
better-workspace-mcp
Google Workspace MCP — Docs, Drive, Calendar, Gmail, Sheets, Slides, Tasks, Chat, People, Forms. Runs locally from the @n24q02m/better-workspace-mcp npm package. Needs 2 environment variables to run.
gdocs-mcp
Treat a Google Doc like a local file: content editing, tracked-changes review, comments, tables. Runs locally from the @dasasian/gdocs-mcp npm package.