LeashIndex Get the report

Index / other

Yandex Direct MCP

io-github-askads-mcp-yandex-direct declares 44 capabilities across 44 tools, with 2 critical issues.

96/100 exposureHigh exposure

Manifest recorded 2026-10-15 from tools/list answered by the npm package mcp-yandex-direct@1.5.5 (published to npm as mcp-yandex-direct, listed in the official MCP registry as io.github.askads/mcp-yandex-direct 1.5.5), run in an isolated container with no network access and placeholder credentials. The date changes only when the manifest does. Not verified by a maintainer.

Issues

These describe what this server's manifest declares. A product can provide controls that MCP has no way to express — token revocation, an admin console, audit logs — and this page cannot see them. The absence of a declaration is not evidence that a control is absent.

critical · no-revocation · All 44 tools

44 of 44 tools declare no way for the customer to switch them off once granted. This applies to every tool because MCP has no field in which to declare a revocation mechanism; the product may provide one outside MCP that a manifest cannot show.

critical · irreversible-uncapped · 10 of 44 tools

10 tools are classified as irreversible and declare no limit.

high · no-expiry · All 44 tools

44 of 44 tools declare no expiry. This applies to every tool because MCP has no field in which to declare an expiry; the product may provide one outside MCP that a manifest cannot show.

high · no-audit-trail · All 44 tools

44 of 44 tools declare no record of their actions that the customer can read. This applies to every tool because MCP has no field in which to declare an audit requirement; the product may provide one outside MCP that a manifest cannot show.

high · uncapped-write · 15 of 44 tools

15 tools can modify data and declare no limit.

low · uncapped-read · 19 of 44 tools

19 tools can read data and declare no limit.

Declared capabilities

How each tool was read. declared means the server's own annotation said so — self-reported and unverified. inferred is from the tool's name. assumed means nothing indicated either way.

ToolRead asBasis
auth_statusread declared
start_loginread declared
finish_loginwrite assumed
logoutdestructive declared
get_account_inforead declared
get_balanceread declared
get_quotaread declared
list_campaignsread declared
create_text_campaignwrite inferred
campaign_actiondestructive declared
update_campaignwrite inferred
list_ad_groupsread declared
create_ad_groupwrite inferred
update_ad_groupwrite inferred
delete_ad_groupsdestructive declared
list_adsread declared
create_text_adwrite inferred
ad_actiondestructive declared
update_text_adwrite inferred
list_keywordsread declared
add_keywordswrite inferred
keyword_actiondestructive declared
set_keyword_bidswrite inferred
get_statisticsread declared
get_regionsread declared
get_dictionariesread declared
raw_requestdestructive declared
get_bid_modifiersread declared
add_bid_modifierwrite inferred
set_bid_modifierswrite inferred
delete_bid_modifiersdestructive declared
get_sitelinksread declared
create_sitelinks_setwrite inferred
delete_sitelinksdestructive declared
get_calloutsread declared
add_calloutswrite inferred
delete_calloutsdestructive declared
get_vcardsread declared
create_vcardwrite inferred
delete_vcardsdestructive declared
get_ad_imagesread declared
get_ad_videosread declared
get_creativesread declared
upload_ad_imagewrite inferred
Answering this question about your own agent? The self-serve stack report applies the same reading to your own stack or server and gives you a dated document you can hand to a customer's security review. It is generated in your browser, with nobody to wait for. Buying one does not change this page, its score or its place in the index — see Independence.
Maintain this server? If this page misreads your manifest, or your server has changed, submit its current tools/list response and it will be re-scored and dated. Corrections are published alongside the original, not in place of it.