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/davidmosiah/google-ads-mcp-unofficialWrote 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/davidmosiah/google-ads-mcp-unofficial/google-ads-mcp)<a href="https://agentmods.dev/mcp/davidmosiah/google-ads-mcp-unofficial/google-ads-mcp"><img src="https://agentmods.dev/badge/mcp/davidmosiah/google-ads-mcp-unofficial/google-ads-mcp/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/mcp/davidmosiah/google-ads-mcp-unofficial/google-ads-mcp"><img src="https://agentmods.dev/badge/mcp/davidmosiah/google-ads-mcp-unofficial/google-ads-mcp.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
google-ads-mcp 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 11d 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-mcp": {
"command": "npx",
"args": [
"-y",
"google-ads-mcp-unofficial"
],
"env": {
"GOOGLE_ADS_DEVELOPER_TOKEN": "",
"GOOGLE_ADS_CLIENT_ID": "",
"GOOGLE_ADS_CLIENT_SECRET": "",
"GOOGLE_ADS_LOGIN_CUSTOMER_ID": "",
"GOOGLE_ADS_REDIRECT_URI": "",
"GOOGLE_ADS_TOKEN_PATH": "",
"GOOGLE_ADS_PRIVACY_MODE": "",
"GOOGLE_ADS_ALLOW_MUTATIONS": "",
"GOOGLE_ADS_CACHE": "",
"GOOGLE_ADS_CACHE_PATH": "",
"GOOGLE_ADS_CACHE_TTL_SECONDS": "",
"GOOGLE_ADS_NO_RETRY": ""
}
}
}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.
- 11d ago First seen · 23 lines scan A 0a80ad2a8799
google-ads-mcp is an MCP server published in the GitHub repository davidmosiah/google-ads-mcp-unofficial (4 stars, last pushed 4d 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
neurostack
Token-efficient MCP memory for Markdown vaults. Tiered retrieval, hybrid search, GraphRAG. Runs locally from the neurostack npm package. Needs 1 environment variable to run.
image_context_runtime
MCP server "imagecontextruntime" as configured in shixinnt/codex-image-context-runtime. Runs ./mcp/server.mjs with node.
rag-rat
CLI and MCP entrypoint for indexing repositories into local source, graph, history, and memory evidence. Runs locally from the @rag-rat/bin npm package.
mcp-google-ads-server
MCP server "mcp-google-ads-server" as configured in johnoconnor0/google-ads-mcp. Runs locally from the mcp-google-ads-server Python package.
jobfindsme
MCP server "jobfindsme" as configured in russeell/jobfindsme. Launched with bash -lc exec "${JOBFINDSME_PYTHON:-$HOME/.jobfindsme/runtime/bin/python}" -m jo.
blz
MCP server "blz" as configured in outfitter-dev/blz. Launched with blz mcp-server.