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/askads/mcp-vk-adsWrote 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/askads/mcp-vk-ads/mcp-vk-ads)<a href="https://agentmods.dev/mcp/askads/mcp-vk-ads/mcp-vk-ads"><img src="https://agentmods.dev/badge/mcp/askads/mcp-vk-ads/mcp-vk-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/askads/mcp-vk-ads/mcp-vk-ads"><img src="https://agentmods.dev/badge/mcp/askads/mcp-vk-ads/mcp-vk-ads.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
mcp-vk-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 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
{
"mcp-vk-ads": {
"command": "npx",
"args": [
"-y",
"mcp-vk-ads"
],
"env": {
"VK_ADS_TOKEN": "",
"VK_ADS_LANG": "ru",
"VK_ADS_TIMEOUT_MS": "60000",
"VK_ADS_MAX_RETRIES": "3",
"VK_ADS_API_BASE": "https://ads.vk.com/api"
}
}
}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 · 16 lines scan A 48c64c995c2d
mcp-vk-ads is an MCP server published in the GitHub repository askads/mcp-vk-ads (6 stars, last pushed 20d 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
mcp-yandex-direct
MCP server for Yandex Direct API v5: manage PPC campaigns, ads, keywords, and statistics. Runs locally from the mcp-yandex-direct npm package. Needs 4 environment variables to run.
mcp-server
Kadam advertising platform — manage ads, campaigns, creatives, audiences and stats. Runs locally from the @kadam-net/mcp-server npm package. Needs 2 environment variables to run.
mcp-yandex-audience
MCP server for Yandex Audience API: segments (CRM, lookalike, pixel), pixels, grants. Runs locally from the mcp-yandex-audience npm package. Needs 4 environment variables to run.
synter-ads
Model Context Protocol (MCP) server for AI agents to manage ad campaigns across Google, Meta, LinkedIn, Microsoft, Reddit, TikTok, and more. Create campaigns, adjust budgets, generate creatives, and pull performance data through natural conversation. Runs locally from the @synterai/mcp-server npm package. Needs 1…
seo
Spot keyword demand rising or fading. Trend volume and growth signals. Free key at trendsmcp.ai. Remote server at seo.api.trendsmcp.ai.
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.