io.github.MCPKit-RU/yandex-metrika-mcp

MCPKit — Yandex Metrica MCP

Is the MCPKit MCP server down? No. It is up and needs auth (HTTP 401), probed 2026-11-12.

Analyze Yandex Metrica traffic and conversions in ChatGPT with read-only access.

needs auth probed 2026-11-14 · unchanged since 2026-11-12 · HTTP 401 · Bearer

Streamable HTTP error: Error POSTing to endpoint:

Endpoint: https://mcpkit.ru/mcp-yandex-metrika/mcp (streamable-http)
Host: mcpkit.ru
Getting access: OAuth with dynamic client registration. A client such as Claude Code, Cursor or npx mcpcost auth https://mcpkit.ru/mcp-yandex-metrika/mcp registers itself and opens the consent page; the publisher has nothing to set up for you.
Authorization server mcpkit.ru, PKCE S256, grants authorization_code, refresh_token.
Scopes metrika:mcp.
Read from the server's public OAuth metadata, without a token. Method.
Website: https://mcpkit.ru/mcp-yandex-metrika?utm_source=official_mcp_registry&utm_medium=mcp_registry&utm_campaign=yandex_metrika
Registry: active, updated 2026-11-08 · registry entry

More servers

Other registry entries on mcpkit.ru.

MCPKit — Yandex Direct MCP io.github.MCPKit-RU/yandex-direct-mcp · needs auth
MCPKit — Yandex Wordstat MCP io.github.MCPKit-RU/yandex-wordstat-mcp · needs auth

Servers that mention metrika.

Yandex Metrika MCP io.github.expremiental/yandex-metrika-mcp · alive
Kontekstolog — Yandex Direct, Metrika & Wordstat online.kontekstolog/mcp-yandex · needs auth
Vibe Marketolog — landing A/B tests and Yandex Direct ru.vibemarketolog/vibemarketolog · needs auth
io.github.dontsovcmc/yandex-metrika · needs mcp<2
Yandex Analytics io.github.nozikov/yandex-mcp · alive
Yandex Metrika MCP io.github.stufently/yandex-metrika-mcp · alive
yandex-metrika-mcp io.github.theYahia/yandex-metrika-mcp · alive
SEO Tools: Yandex.Metrica io.github.antohins/seo-tools-mcp-metrika · alive

The result of the latest probe, the tool count and the token cost. The feed has an entry for every probe that changed them.

Stops answering, comes back, tool set or cost changes. One confirmation mail first, a stop link in every mail.

The server answers HTTP 401 to an unauthenticated initialize, so the probe cannot list its tools. That is correct for a private server. Some public servers answer initialize and tools/list without credentials and ask for auth on tool calls only; those get a token count here.

Fixed something? Probe it now, with the same steps as the daily run. This page updates with the next daily run.