MCP server for Yandex Metrika API — web analytics, traffic, audience data
Inferred from the transports this listing declares (stdio). A client not listed here hasn’t been ruled out — it just isn’t something Forge can confirm.
YANDEX_METRIKA_TOKENAPI keyrequiredOAuth token for Yandex Metrika (metrika:read; metrika:write for counter tools)
Declared by the author in the official MCP registry. Forge does not store, broker, or ever see these values — the config below is scaffolded with placeholders you fill in locally.
Verification confirms publisher identity (repo ownership), not code safety. The security scan covers known CVEs and suspicious install scripts.
Read out of the source npm actually ships, at scan time. The package was never executed. Tools registered dynamically at runtime, or hidden inside bundled or minified code, can be missed — so this is a floor on the tool surface, not a complete census of it.
get-countersList all Metrika counters (sites).List all Metrika counters (sites).
No input schema was published for this tool.
get-counterGet details for a specific Metrika counter.Get details for a specific Metrika counter.
No input schema was published for this tool.
get-goalsGet goals for a Metrika counter.Get goals for a Metrika counter.
No input schema was published for this tool.
create-counterNo description publishedThis tool published no description. Forge does not invent one.
delete-counterprivilegedDelete a Metrika counter. IRREVERSIBLE: the counter and all its collected statistics are lost permanently.Delete a Metrika counter. IRREVERSIBLE: the counter and all its collected statistics are lost permanently.
No input schema was published for this tool.
get-traffic-summaryGet traffic summary: visits, users, pageviews, bounce rate, avg duration.Get traffic summary: visits, users, pageviews, bounce rate, avg duration.
No input schema was published for this tool.
get-traffic-sourcesGet traffic breakdown by source.Get traffic breakdown by source.
No input schema was published for this tool.
get-geographyGet traffic breakdown by country and city.Get traffic breakdown by country and city.
No input schema was published for this tool.
get-devicesGet traffic breakdown by device, browser, or OS.Get traffic breakdown by device, browser, or OS.
No input schema was published for this tool.
get-popular-pagesGet most visited pages.Get most visited pages.
No input schema was published for this tool.
get-search-phrasesGet top search phrases driving traffic.Get top search phrases driving traffic.
No input schema was published for this tool.
get-reportRun a custom Metrika report with arbitrary metrics and dimensions.Run a custom Metrika report with arbitrary metrics and dimensions.
No input schema was published for this tool.
11 of 12 tools published a description.
Tool names and descriptions are written by the publisher and shown verbatim as inert text. They are the strings an MCP client passes to a model, so Forge scans them for prompt-injection patterns — any finding appears with the security scan above. “Privileged” is a keyword match on the tool name, not an audit of what the tool does: a benign-sounding name can still do anything.
MCP server for Yandex Metrika API — web analytics, traffic, audience data
Linked names open Forge’s index of every entry observed exposing that tool. Browse all indexed tools.
The crawl stopped at the depth-4 limit. Anything below that level was never resolved.
The crawl stopped at the 60-package limit. The rest of the tree was never resolved.
36 more resolved packages are not drawn here (display cap: 24). Every dependency carrying an advisory is drawn regardless of the cap. Full inventory (CycloneDX SBOM)
54 declared dependencies never landed in the tree. They are missing from Forge's resolution, not from the package.
+42 more not listed. The counts by reason above cover all of them.
Not followed: peerDependencies. This tree covers runtime dependencies only, so anything those pull in was never resolved.