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 2mo 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.
- 2mo ago First seen · 16 lines scan A 48c64c995c2d
mcp-vk-ads is an MCP server published in the GitHub repository askads/mcp-vk-ads (11 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-31.
Other mcp servers, from other repositories
google-meta-ads-ga4-mcp
Google Ads, Meta Ads, SEO, GEO & GA4 MCP by Ryze AI - audits, reports, keywords, Search Console. Remote server at connector.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.
synter
Official Synter MCP server: AI agents run ads across 16 ad platforms, including Google, Meta, LinkedIn, Microsoft, Reddit, TikTok, X, Amazon, and StackAdapt. Free to read ($0/mo), then $20/month Solo for campaign creation, budget updates, creatives, and a. Runs locally from the @synterai/mcp-server npm package. Needs…
synter-ads
Run ads across 16 ad platforms from any MCP client. Hosted OAuth at mcp.synterai.com. Runs locally from the @synterai/mcp-server npm package. Needs 1 environment variable to run.
synter-ads
MCP server "synter-ads", hosted remotely at mcp.syntermedia.ai, as configured in Synter-Media-AI/amazon-ads-agent.
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.