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/alifanov/scopegateWrote 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/alifanov/scopegate/google-ads)<a href="https://agentmods.dev/mcp/alifanov/scopegate/google-ads"><img src="https://agentmods.dev/badge/mcp/alifanov/scopegate/google-ads/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/alifanov/scopegate/google-ads"><img src="https://agentmods.dev/badge/mcp/alifanov/scopegate/google-ads.svg" alt="Reviewed on agentmods" width="80" 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 1mo 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": {
"type": "http",
"url": "https://scopegate.chatindex.app/api/mcp/cmm6phdel00020jpg5bjkj19d",
"headers": {
"Authorization": "Bearer cmm6phdel00020jpg5bjkj19d"
}
}
}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.
- 1mo ago First seen · 9 lines scan A f5dfbea78bad
google-ads is an MCP server published in the GitHub repository alifanov/scopegate (18 stars, last pushed yesterday), 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
swiss-transport-mcp
MCP server for Swiss public transport – OJP journey planner, real-time departures, disruptions, occupancy, ticket prices, train formations and open data from opentransportdata.swiss. Runs locally from the swiss-transport-mcp Python package.
chronicle-mcp
Local MCP server to sync, clean, and index AI chat logs locally. Saves up to 40% context tokens. Runs locally from the chronicle-mcp-server Python package.
zuckerbot
CLI + MCP server for ZuckerBot — manage, audit and generate Meta ad campaigns from Claude or any AI agent. Runs locally from the zuckerbot-mcp npm package. Needs 1 environment variable to run.
github
Lets the agent work with GitHub: search code, read and create issues and pull requests, and manage repositories through the GitHub API. Runs locally from the @modelcontextprotocol/server-github npm package.
compactprompt
Easy-to-use prompt & data compression for LLM workflows. Runs locally from the compactprompt Python package.
docs-to-ai
MCP server "docs-to-ai" as configured in dorianmeric/docs-to-ai. Runs locally from the docs-to-ai Python package.