Yandex Metrica MCP

io.github.askads/mcp-yandex-metricav1.3.1Analytics

MCP server for Yandex Metrica API: list counters, goals and pull web-analytics statistics.

In-path gate · all MCP tools

Using Yandex Metrica MCP in Claude, Cursor, Gemini CLI, Cline, or Zed?

MCP tool contracts can change remotely with no version bump. The mcpindex gate pins each contract and HOLDs the call when it drifts-before your agent acts. Zero credentials. This is not the package install for this server itself (use Install this server for that).

Install the mcpindex gate (one command)

Rewrites your MCP host config so each server launches behind the gate. Inspect first: curl -fsSL https://mcpindex.ai/install.sh | less

uv tool install mcpindex-gate && mcpindex-config-wire

Auditable install path →Watch it hold a drift →

Trust verdict · v1 advisory · method

REVIEWstatus: PARTIALfresh until 2026-08-23 03:00 UTC

screened 2026-07-24tier: scannedgranularity: description-levelsource: registry

Semantic screen found no manipulation pattern in the description. Conformance probe not yet run.

mcpindex.integrity.descriptionpassINFO

evidence“No malicious instructions found”via static_description

Limits of this verdict

- Semantic screen only - the deterministic conformance probe has not run on this server
- Confidence is reported but not yet calibrated (v1)
- Screen reads the tool description, not the live behavior
- advisory
- registry description only no input schema
- screen model 8b
- The registry listing (version, packages, links) changed after this screen ran - the description we assessed did not

Semantic screen: an LLM judge reads the tool description for hidden instructions (status PARTIAL). A pass means the description is not lying, not that the tool is safe: a high-capability tool with an honest description still warrants caution. The deterministic conformance probe has not been run on this server yet, so the screen here is semantic-only. Posture: advisory. Confidences are reported but not yet calibrated (calibrated=false at v1). Full verdict history is not shown on this page.

Own this server? Screen its description →

That verdict was true at screening time (snapshot 2026-08-11).

Contracts can change after screening, with no version bump. The gate pins Yandex Metrica MCP’s tool contracts on first sight and holds any silent change before your agent acts - the check that keeps being true on Tuesday.

See your first HOLD in 2 minutes →

Embed this badge

A live verdict badge for your README or listing. It reflects the current screen, links back here, and updates when the verdict does.

Markdown

[![mcpindex](https://mcpindex.ai/api/v1/badge/io-github-askads-mcp-yandex-metrica)](https://mcpindex.ai/server/io-github-askads-mcp-yandex-metrica)

HTML

<a href="https://mcpindex.ai/server/io-github-askads-mcp-yandex-metrica"><img src="https://mcpindex.ai/api/v1/badge/io-github-askads-mcp-yandex-metrica" alt="mcpindex verdict" height="20" /></a>

Environment variables

YANDEX_METRIKA_TOKEN

requiredsecret

Yandex Metrica OAuth token (scope metrika:read) — read access to analytics data. Treat it as a secret.

YANDEX_METRIKA_COUNTER_ID

Default Metrica counter id, used when a tool call omits counterId.

YANDEX_METRIKA_LANG

Language for API responses (ru, en, ...).

YANDEX_METRIKA_API_BASE

API root host. Override only for a proxy or a non-default endpoint.

YANDEX_METRIKA_TIMEOUT_MS

Per-request timeout in milliseconds.

YANDEX_METRIKA_MAX_RETRIES

Max retries for transient errors (429 rate limit, 5xx on reads).

MCP quality score · maturity, not trust · methodology

freshness

completeness

installability

documentation

stability

Alternatives in Analytics

AIOProductOS MCP

com.aioproductos/mcp

AIOProductOS: revenue, feedback, work and analytics on one customer record. 71 tools, 3 apps.

Appfigures

com.appfigures/mcp

Access your app analytics, ASO tools, and app market intelligence with Appfigures.

FinCore Agentic Commerce

io.github.athenalion/fincore-agentic-commerce

Agentic commerce with 58 MCP tools for product search, checkout, A2A negotiation, C-Suite analytics.

Install this server

Claude Desktop (claude_desktop_config.json)

{
  "mcpServers": {
    "mcp-yandex-metrica": {
      "command": "npx",
      "args": [
        "-y",
        "--",
        "mcp-yandex-metrica"
      ],
      "env": {
        "YANDEX_METRIKA_TOKEN": "<your-yandex_metrika_token>",
        "YANDEX_METRIKA_COUNTER_ID": "<yandex_metrika_counter_id>",
        "YANDEX_METRIKA_LANG": "ru",
        "YANDEX_METRIKA_API_BASE": "https://api-metrika.yandex.net",
        "YANDEX_METRIKA_TIMEOUT_MS": "60000",
        "YANDEX_METRIKA_MAX_RETRIES": "3"
      }
    }
  }
}

Cursor (.cursor/mcp.json)

{
  "mcpServers": {
    "mcp-yandex-metrica": {
      "command": "npx",
      "args": [
        "-y",
        "--",
        "mcp-yandex-metrica"
      ],
      "env": {
        "YANDEX_METRIKA_TOKEN": "<your-yandex_metrika_token>",
        "YANDEX_METRIKA_COUNTER_ID": "<yandex_metrika_counter_id>",
        "YANDEX_METRIKA_LANG": "ru",
        "YANDEX_METRIKA_API_BASE": "https://api-metrika.yandex.net",
        "YANDEX_METRIKA_TIMEOUT_MS": "60000",
        "YANDEX_METRIKA_MAX_RETRIES": "3"
      }
    }
  }
}

Cline (cline_mcp_settings.json)

npx -y -- mcp-yandex-metrica

Claude Code (claude mcp add)

claude mcp add --scope user mcp-yandex-metrica -- npx -y -- mcp-yandex-metrica

Gemini CLI (gemini mcp add)

gemini mcp add -s user mcp-yandex-metrica npx -y -- mcp-yandex-metrica

Verdict API

curl -s mcpindex.ai/api/v1/trust/server/io-github-askads-mcp-yandex-metrica

Free-tier verdict as JSON: decision + dimensions + severity. Call it from your agent before it invokes a tool it just discovered.

Details

version: v1.3.1
category: Analytics
verdict expires: 2026-08-23
quality: 95 / 100
operator: askads

Listing

Listed from the official MCP registry. Unclaimed by its maintainer. Maintainer? Email us →

Provenance

Each verdict is bound to a hash of the exact description it judged, so a re-crawl that changes the text produces a new record rather than silently inheriting this one. Verdict history is hash-chained and anchored to Bitcoin via OpenTimestamps (latest confirmed at block 961,958). Verify it yourself.

Links

Repository →Website →