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/amekala/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/amekala/ads-mcp/adspirer)<a href="https://agentmods.dev/mcp/amekala/ads-mcp/adspirer"><img src="https://agentmods.dev/badge/mcp/amekala/ads-mcp/adspirer/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/amekala/ads-mcp/adspirer"><img src="https://agentmods.dev/badge/mcp/amekala/ads-mcp/adspirer.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
adspirer 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 10d 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
{
"adspirer": {
"type": "http",
"url": "https://mcp.adspirer.com/mcp"
}
}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.
- 10d ago First seen · 6 lines scan A 3787f17c658d
adspirer is an MCP server published in the GitHub repository amekala/ads-mcp (89 stars, last pushed 3d 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-30.
Other mcp servers, from other repositories
paidsync
MCP server "paidsync", hosted remotely at mcp.paidsync.ai, as configured in traffiy/paidsync-mcp.
google-meta-ads-ga4-mcp
Google Ads, Meta Ads & GA4 MCP server - 250+ tools for campaigns, creatives, audiences & reports. Remote server at mcp.get-ryze.ai.
google-meta-ads-ga4
MCP server "google-meta-ads-ga4", hosted remotely at connector.get-ryze.ai, as configured in irinabuht12-oss/google-meta-ads-ga4-mcp.
mureo
MCP server "mureo" as configured in logly/mureo. Launched with sh -c if [ -x "${HOME}/.local/bin/mureo-mcp-wrapper.sh" ]; then exec "${HOME}/.l.
mcp-ads
MCP server "mcp-ads" as configured in RoyAzran/mcp-ads. Runs locally from the mcp-ads Python 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.