# @stufently/yandex-metrika-mcp

MCP server for Yandex Metrika API — web analytics, traffic, audience data

- **Type:** MCP server
- **Trust:** 60/100 (B), scored on the package rubric
- **Verification:** community-indexed — nobody has claimed this listing
- **Version:** 2.2.0
- **Author:** stufently
- **License:** MIT
- **npm:** @stufently/yandex-metrika-mcp
- **Source:** https://github.com/stufently/yandex-mcp
- **Compatible clients:** claude-code, cursor, copilot, gemini (basis: transport)

## Trust

60/100 (B), scored on the package rubric
- Publisher verified: no
- Install scripts: nothing suspicious found
- Prompt-injection scan: not run
- Obfuscation scan: not run
- Evidence age: 1 day

## Security scan

- **Status:** clean
- **Scanned:** 2026-10-16T00:21:28.777Z
- **Version scanned:** 2.2.0
- **CVEs:** none found by OSV at scan time

## Tools

12 declared. Statically extracted from the shipped source — a floor on the surface, not a census.
- `get-counters` — List all Metrika counters (sites).
- `get-counter` — Get details for a specific Metrika counter.
- `get-goals` — Get goals for a Metrika counter.
- `create-counter`
- `delete-counter` — Delete a Metrika counter. IRREVERSIBLE: the counter and all its collected statistics are lost permanently.
- `get-traffic-summary` — Get traffic summary: visits, users, pageviews, bounce rate, avg duration.
- `get-traffic-sources` — Get traffic breakdown by source.
- `get-geography` — Get traffic breakdown by country and city.
- `get-devices` — Get traffic breakdown by device, browser, or OS.
- `get-popular-pages` — Get most visited pages.
- `get-search-phrases` — Get top search phrases driving traffic.
- `get-report` — Run a custom Metrika report with arbitrary metrics and dimensions.

## Install

**Verdict: review** — Installable, but 1 thing to check first: No publisher has proved control of this listing; it is indexed, not vouched for.
**Cautions** (coverage gaps and advisories — never blocking)
- No publisher has proved control of this listing; it is indexed, not vouched for.
**Config** (claude-code):
```json
"{\n  \"mcpServers\": {\n    \"yandex-metrika\": {\n      \"command\": \"npx\",\n      \"args\": [\n        \"-y\",\n        \"@stufently/yandex-metrika-mcp\"\n      ],\n      \"env\": {\n        \"YANDEX_METRIKA_TOKEN\": \"<YOUR_YANDEX_METRIKA_TOKEN>\"\n      }\n    }\n  }\n}"
```
**Credentials it will ask for** (names only — Forge never holds a value):
- `YANDEX_METRIKA_TOKEN` — Yandex Metrika Token (required)
Placeholders only. Forge never holds, brokers, or transmits a credential value — replace each <YOUR_NAME> in your own config file. Do not send a value back to Forge; no Forge endpoint accepts one.
- This entry needs 1 credential (1 required). The generated config carries placeholders, so it will fail in the editor rather than at runtime if they are left unset.

## Blast radius

Extensive blast radius — deletes data; holds an api key.
- Floor 52, ceiling 52 (tier: extensive)
- This is impact, not likelihood. A high radius is not a defect: a filesystem server is supposed to write files. It is never part of the trust score.

## Machine-readable views of this entry

- Signed JSON: https://forgeregistry.com/api/v1/packages/%40stufently%2Fyandex-metrika-mcp
- Install plan: https://forgeregistry.com/api/v1/packages/%40stufently%2Fyandex-metrika-mcp/install-plan
- Alternatives: https://forgeregistry.com/api/v1/alternatives/%40stufently%2Fyandex-metrika-mcp
- HTML page: https://forgeregistry.com/registry/%40stufently%2Fyandex-metrika-mcp
- MCP: POST https://forgeregistry.com/api/mcp → `forge_get_package` / `forge_install_plan`

## About this document

Generated by Forge (https://forgeregistry.com) — a compact rendering of the same record served, signed, at the JSON URL above. Trust and scan facts are the registry's own measurements; anything Forge did not measure is named as unmeasured rather than omitted.