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/us-all/google-drive-mcp-server/google-drivegit clone --depth 1 https://github.com/us-all/google-drive-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/us-all/google-drive-mcp-server/google-drive)<a href="https://agentmods.dev/mcp/us-all/google-drive-mcp-server/google-drive"><img src="https://agentmods.dev/badge/mcp/us-all/google-drive-mcp-server/google-drive.svg" alt="Measured on agentmods" height="20"></a>Grade A, and why
google-drive 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-drive": {
"command": "npx",
"args": [
"-y",
"@us-all/google-drive-mcp"
],
"env": {
"GOOGLE_CLIENT_ID": "",
"GOOGLE_CLIENT_SECRET": "",
"GOOGLE_REFRESH_TOKEN": "",
"GOOGLE_APPLICATION_CREDENTIALS": "",
"GOOGLE_SERVICE_ACCOUNT_KEY_PATH": "",
"GOOGLE_IMPERSONATE_USER": "",
"GOOGLE_DRIVE_SCOPES": "",
"GOOGLE_DRIVE_ALLOW_WRITE": "false",
"GD_TOOLS": "",
"GD_DISABLE": ""
}
}
}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 · 21 lines scan A 30471f575078
google-drive is an MCP server published in the GitHub repository us-all/google-drive-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
google-automation-mcp
Headless Google Workspace automation for AI - Apps Script, Gmail, Drive, Sheets, Calendar, Docs, Tasks, Forms. Runs locally from the google-automation-mcp Python package.
google-workspace-mcp-server
MCP server for Google Workspace APIs - Docs, Sheets, Drive, Gmail, and Calendar. Runs locally from the google-workspace-mcp-server npm package.
ms365
MCP server "ms365", hosted remotely at microsoft365.mcp.claude.com, as configured in tmargolis/career-navigator.
google-mcp
Streamable HTTP MCP server for Google Calendar and Sheets with OAuth login. Remote server at g.mcp.openbsp.dev.
auralis-google
MCP server for Google Workspace - Gmail, Calendar, Drive, Docs, Sheets integration for Claude AI. Runs locally from the auralis-google npm package.
google-workspace-mcp-server
MCP server for Google Workspace APIs - Docs, Sheets, Drive, Gmail, and Calendar. Runs locally from the google-workspace-mcp-server npm package.