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/johnoconnor0/google-ads-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/johnoconnor0/google-ads-mcp/mcp-google-ads-server)<a href="https://agentmods.dev/mcp/johnoconnor0/google-ads-mcp/mcp-google-ads-server"><img src="https://agentmods.dev/badge/mcp/johnoconnor0/google-ads-mcp/mcp-google-ads-server.svg" alt="Measured on agentmods" height="20"></a>Grade A, and why
mcp-google-ads-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 8d 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
{ "mcp-google-ads-server": { "command": "uvx", "args": [ "mcp-google-ads-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.
- 8d ago First seen · 8 lines scan A bcd8b5da0635
mcp-google-ads-server is an MCP server published in the GitHub repository johnoconnor0/google-ads-mcp (13 stars, last pushed today), 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
google-ads-mcp
Unofficial Google Ads MCP for campaigns, keywords, budgets, and gated mutations. Runs locally from the google-ads-mcp-unofficial npm package. Needs 12 environment variables to run.
mcp-ads
MCP server "mcp-ads" as configured in RoyAzran/mcp-ads. Runs locally from the mcp-ads Python package.
servalsheets
MCP server "servalsheets" as configured in khill1269/servalsheets. Runs locally from the servalsheets npm package.
google-ads
Google Ads: 31 read tools with full Keyword Planner, 7 write tools that preview first. Runs locally from the @getmcpads/google-ads-mcp-server npm package. Needs 6 environment variables to run.
google-ads-mcp-plus
MCP server "google-ads-mcp-plus" as configured in monsieurgoodmood/google-ads-mcp-plus. Runs locally from the google-ads-mcp-plus Python package.
mcp-google-ads
Google Ads API integration for Model Context Protocol (MCP) with full campaign management capabilities. Runs locally from the mcp-google-ads Python package.