Yandex Direct (askads) MCP Server

mcp-yandex-direct npm v1.5.1

Published by askads — no publish provenance, so origin is unverified, but the source is public: the repository link below is self-declared yet readable, so you can inspect the code before adopting it.

MCP server for the Yandex Direct API v5 — manage PPC campaigns, ad groups, ads, keywords and pull statistics from AI agents.

Trust grade
A
99/100
Last scanned get badge →
Trust
A · 99/100
Adoption risk for you: the threat score, then adjusted down for blast radius, publisher verification and how much the scan could see. Deterministic; every point is auditable.
Capability
Minimal
Blast radius if it went rogue — what the server’s tools could reach. Independent of trust.
Coverage
Source
How much the scan could actually inspect. Shallow coverage is stated, never hidden.
Share this Trust Score
𝕏 Share LinkedIn Reddit
A Why this grade threat 100 − adoption risk = 99/100

The grade answers one question — how safe is this server for you to adopt — so it is computed in two auditable stages. Nothing below is an opinion or an LLM's guess; every line is a real term the deterministic engine applied, and the same input always yields the same number.

1. Threat score — 100 − 0 = 100. What the published surface and source actually contain:

The deterministic scan raised no scored threat in the surface it inspected — the threat score stayed at 100. Capability observations and advisory notes are recorded but never lower it.

2. Client adoption risk — 100 − 1 = 99. Three small, subtract-only factors that reflect your risk in adopting it — a clean scan proves less on a powerful, unverified or barely-inspectable package, so the grade says so plainly:

PointsAdoption-risk factor
−1 publisher verification (public source) — no provenance, but the source is public and inspectable

Capability observations and info notes are shown under Findings but never scored. Open any row's finding below for the file, line and evidence behind a deduction.

Findings 0

✓ No findings. The scan raised nothing on this surface — see Coverage for how deep it could look.

Tools 44

Each tool and what it can reach — statically extracted from the published source.

  • ad_actionno sensitive capability
  • add_bid_modifierno sensitive capability
  • add_calloutsno sensitive capability
  • add_keywordsno sensitive capability
  • auth_statusno sensitive capability
  • campaign_actionno sensitive capability
  • create_ad_groupno sensitive capability
  • create_sitelinks_setno sensitive capability
  • create_text_adno sensitive capability
  • create_text_campaignno sensitive capability
Show 34 more tools ↓
  • create_vcardno sensitive capability
  • delete_ad_groupsno sensitive capability
  • delete_bid_modifiersno sensitive capability
  • delete_calloutsno sensitive capability
  • delete_sitelinksno sensitive capability
  • delete_vcardsno sensitive capability
  • finish_loginno sensitive capability
  • get_account_infono sensitive capability
  • get_ad_imagesno sensitive capability
  • get_ad_videosno sensitive capability
  • get_balanceno sensitive capability
  • get_bid_modifiersno sensitive capability
  • get_calloutsno sensitive capability
  • get_creativesno sensitive capability
  • get_dictionariesno sensitive capability
  • get_quotano sensitive capability
  • get_regionsno sensitive capability
  • get_sitelinksno sensitive capability
  • get_statisticsno sensitive capability
  • get_vcardsno sensitive capability
  • keyword_actionno sensitive capability
  • list_ad_groupsno sensitive capability
  • list_adsno sensitive capability
  • list_campaignsno sensitive capability
  • list_keywordsno sensitive capability
  • logoutno sensitive capability
  • raw_requestno sensitive capability
  • set_bid_modifiersno sensitive capability
  • set_keyword_bidsno sensitive capability
  • start_loginno sensitive capability
  • update_ad_groupno sensitive capability
  • update_campaignno sensitive capability
  • update_text_adno sensitive capability
  • upload_ad_imageno sensitive capability

What this scan could not see

Versions 5

Scan history per published version. The engine is deterministic — the same version always yields the same score, so a changed score means the package itself changed.

VersionScoreFindingsEngineScanned
v1.5.1 latest A 99/100 0 1.13.0 2026-09-07
v1.4.1 A 99/100 0 1.12.1 2026-08-18
v1.4.0 A 99/100 0 1.12.1 2026-08-10
v1.3.0 A 99/100 0 1.12.1 2026-08-07
v1.2.0 A 99/100 0 1.12.1 2026-08-05

Embed this score

Show this server's live Trust Score in your README, docs or website. The badge is served straight from the registry and updates automatically after every rescan — no API key needed. It links back to this page, so anyone who sees the grade can also read the findings behind it instead of taking a number on faith.

MCP Trust Score: A · 99/100
Markdown (GitHub README)
[![MCP Trust Score](https://mcptrustchecker.com/registry/mcp-yandex-direct/badge.svg)](https://mcptrustchecker.com/registry/mcp-yandex-direct)
HTML
<a href="https://mcptrustchecker.com/registry/mcp-yandex-direct"><img src="https://mcptrustchecker.com/registry/mcp-yandex-direct/badge.svg" alt="MCP Trust Score" height="20"></a>
Prefer shields.io styling? Point it at https://mcptrustchecker.com/registry/mcp-yandex-direct/badge.json via https://img.shields.io/endpoint?url=…

Verify this score yourself

The score above is reproducible: the same package version always yields the same result. Run it locally or over the free API — no account, no LLM, fully deterministic.

npx mcptrustchecker scan mcp-yandex-direct --online

Use the free API → How scoring works

Other implementations of Yandex Direct 1

Independent packages implementing the same tool, scanned with the same engine. Compare all 2 side by side →

More in Communication & Collaboration