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/getmcpads-com/google-ads-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/getmcpads-com/google-ads-mcp-server/google-ads)<a href="https://agentmods.dev/mcp/getmcpads-com/google-ads-mcp-server/google-ads"><img src="https://agentmods.dev/badge/mcp/getmcpads-com/google-ads-mcp-server/google-ads.svg" alt="Measured on agentmods" height="20"></a>Grade A, and why
google-ads 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 6d 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-ads": {
"command": "npx",
"args": [
"-y",
"@getmcpads/google-ads-mcp-server"
],
"env": {
"GOOGLE_ADS_DEVELOPER_TOKEN": "",
"GOOGLE_ADS_CLIENT_ID": "",
"GOOGLE_ADS_CLIENT_SECRET": "",
"GOOGLE_ADS_REFRESH_TOKEN": "",
"GOOGLE_ADS_LOGIN_CUSTOMER_ID": "",
"GOOGLE_ADS_ENABLE_WRITES": ""
}
}
}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.
- 6d ago First seen · 17 lines scan A e60f37cca401
google-ads is an MCP server published in the GitHub repository getmcpads-com/google-ads-mcp-server (0 stars, last pushed 6d ago), licensed Apache-2.0. 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
mcp-ads
MCP server "mcp-ads" as configured in RoyAzran/mcp-ads. Runs locally from the mcp-ads 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.
google-ads-mcp-server
MCP server "google-ads-mcp-server" as configured in burhan29ee/google-ads-mcp-server. Runs locally from the google-ads-mcp-server Python package.
googleadsagent-mcp
Google Ads MCP Server — googleadsagent.ai. Runs locally from the googleadsagent-mcp Python package.
google-ads-mcp
MCP server "google-ads-mcp" as configured in noviq-ai/google-ads-mcp. Launched with /bin/zsh -l -c uvx --from git+https://github.com/noviq-ai/google-ads-mcp.git pyt.
google-ads-mcp
MCP Server for Google Ads, depends on Google Ads API. Runs locally from the google-ads-mcp Python package.