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/proxy-intell/google-ads-library-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/proxy-intell/google-ads-library-mcp/google-ads-library)<a href="https://agentmods.dev/mcp/proxy-intell/google-ads-library-mcp/google-ads-library"><img src="https://agentmods.dev/badge/mcp/proxy-intell/google-ads-library-mcp/google-ads-library.svg" alt="Measured on agentmods" height="20"></a>Grade A, and why
google-ads-library 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- google-ads-library — 100% identical, 0 lines differ
What it actually says
{
"google-ads-library": {
"command": "npx",
"args": [
"-y",
"@proxy-intell/google-ads-library-mcp"
],
"env": {}
}
}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 · 10 lines scan A 3e0e8216e738
google-ads-library is an MCP server published in the GitHub repository proxy-intell/google-ads-library-mcp (11 stars, last pushed 27d 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-hotels
Google Hotels prices, ratings, reviews, and photos via an Apify Actor, hosted MCP. Remote server at mcp.apify.com.
tachy
TypeScript Execute (tsx): Node.js enhanced with esbuild to run TypeScript & ESM files. Runs locally from the tsx npm package.
webhook
Send, validate, debug webhooks for AI agents. Runs locally from the @rog0x/mcp-webhook-tools npm package.
skyvern
AI-powered browser automation — navigate, click, fill forms, and extract data from any website. Remote server at api.skyvern.com.
proximo-proxmox
The Proxmox MCP you can hand the keys: VE/PBS/PMG/PDM. Plan, prove, undo, diagnose. MCP/A2A/API. Runs locally from the proximo-proxmox Python package.
hackmd-mcp
A Model Context Protocol server for integrating HackMD's note-taking platform with AI assistants. Runs locally from the hackmd-mcp npm package. Needs 2 environment variables to run.