Model Context Protocol server for Rollbar
Nothing to run from here
Yandex Metrika is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
94/100
trust score
435
downloads a day
local
runs on your machine
13
tools declared
What it does
Read-only Yandex Metrika (Яндекс Метрика) analytics: verifiable reports, comparisons and exports.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user devcrabs-inc-yandex-metrika-mcp '--' npx -y @dev-crabs/yandex-metrika-mcp
# 2 — ask your agent for something these tools do
# metrika_status, metrika_connect, metrika_disconnect and 10 more
Yandex Metrika costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Publishernot claimed
DIAll 1 server
devcrabs-inc1 server
1 category
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Installation
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. This one runs on your machine: your client starts Yandex Metrika as a process under your own user, with your files and your network, so the tool surface below is what it can do to your computer rather than to a server somewhere else. Its scan result is on the Security tab — read the surface before you approve it.
Claude Codedeclared by this listing
This is a public server: you run it yourself and this marketplace is not in the path. You need Node.js — the current LTS (24) is the safe choice; npx comes with it. Claude Code registers it in one command; --scope user makes it available in every project. The '--' is in quotes so that PowerShell passes it on.
claude mcp add --scope user devcrabs-inc-yandex-metrika-mcp '--' npx -y @dev-crabs/yandex-metrika-mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
Free on mcprush, and it runs from its publisher’s own package: this marketplace is not in the path, so there is no key of ours to hold and no card to add.
What it asks of you
Nothing is required, but it can take YM_MCP_CLIENT_ID (Optional: your own Yandex OAuth app client ID (public PKCE client, no secret).), YANDEX_METRIKA_TOKEN (Optional: an existing OAuth token with metrika:read, for headless setups.) if you want to set them.
What it writes
One config entry your client uses to start the process locally. A local server runs with your file system and your network, which is why it is priced without metering.
What you approve
13 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
Read from its source code. A server that builds its tool list when it starts can list more tools than this.
Shows Yandex Metrika connections (connection_id values) and their state, export jobs, capabilities and the next step. Call it first; works before any Yandex sign-in.
No parameter schema on file.
Signs in to Yandex Metrika in the browser (read-only access). Returns a one-time local login_url for the user to open; no token or code ever passes through the chat. Pass connection_id to renew an expired connection. Afterwards call metrika_status to get the new connection_id.
No parameter schema on file.
Disconnects a Yandex Metrika connection on this computer: cancels its exports, deletes its token and clears its cache. Data already shown in the chat cannot be recalled. Revoking app access inside Yandex is a separate step for the user.
No parameter schema on file.
Lists Yandex Metrika (Яндекс Метрика) counters, i.e. tracked websites, available through a connection: ID, name, site, time zone and access level. Pass the ID as counter_id to other tools.
No parameter schema on file.
Shows a Yandex Metrika counter's settings (time zone, status, access) and its goals with IDs. Call before goal reports. Goal names can repeat, so always refer to goals by ID.
No parameter schema on file.
Lists the Yandex Metrika report fields this server supports: kind='presets' (ready-made reports), 'metrics' (with unit and aggregation rules, e.g. users must never be summed), 'dimensions' or 'periods'. No API call.
No parameter schema on file.
Runs a Yandex Metrika traffic or goal report for one period: a preset (overview, acquisition, landing_pages, devices, geography, goals) or explicit metrics/dimensions, with filters, sorting and paging (max 200 rows per call; use metrika_export_report for everything). Returns API totals, rows, data…
No parameter schema on file.
Compares Yandex Metrika traffic between two periods (e.g. week over week) under identical conditions (same counter, metrics, filters, time zone): baseline, current, absolute and percent change, plus percentage points for rates; a zero baseline gives a null percent. Optional dimensions compare…
No parameter schema on file.
Shows Yandex Metrika metric dynamics in day, week or month buckets with exact calendar boundaries in the counter time zone (weekly series must start on a Monday). Flags buckets that include today or are clipped by the period. Optional dimensions return top-N segment series. Default: last 28…
No parameter schema on file.
Exports all rows of a Yandex Metrika report to a CSV or JSON file in the background and returns a job. Requires idempotency_key; the same key returns the same job. To continue an interrupted export pass only connection_id and resume_job_id. Poll metrika_get_job until completed, then read with…
No parameter schema on file.
Shows the state, progress, errors and result files of a Yandex Metrika export job.
No parameter schema on file.
Cancels a Yandex Metrika export job and removes its temporary files. Safe to repeat. Already finished files are not deleted.
No parameter schema on file.
Reads a finished Yandex Metrika export file in chunks (up to 32 KiB, cut at line boundaries). Takes an artifact_id, never a path or URL.
No parameter schema on file.
Free
$0 forever
- Every tool, no call limit
- No card, and mcprush charges nothing for it
- Source published under MIT
- Runs on your machine — nothing of it reaches our gateway
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install Yandex Metrika or to call it, at any volume.
Call allowance · this installenforced at the gateway
Monthly allowance, in calls
—
—
Alert at 80% · then the tool returns a normal MCP error
Used this month: —
ATrust score 94 / 100
Release 1.0.0 · scanned 10 Nov 2026
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
Threat score100
Client score94
Findings2 threat · 0 capability
Capabilityhigh
Coveragesource
Verificationsource
Surface digest57bad78a1507ac0cc7e65c423455cacb701bee0a2fcfc99c278e56f542d65a5b
Score vectorthreat 100 → client 94
| Term | Level | What it prices | Points |
|---|---|---|---|
| capability-exposure | high | capability blast radius (high) — client exposure if the model is manipulated | −6 |
| verification-discount | source | publisher verification (provenance) — cryptographic build provenance ties the artifact to its source | −0 |
| coverage-honesty | source | inspection depth (source) — how much of the target the scan could see | −0 |
score = clamp(round(threatScore − E_cap − E_ver − E_cov), 0, 100). No model, no opinion, no network call at scoring time: the same methodology version against the same bytes always produces this number, and every line above is a field of the report rather than a summary of it.
What the scan could actually read
A grade is only as meaningful as its coverage, so the scanner publishes its own depth before it publishes its result.
Tool surfacenot available
Implementation sourceread
Package metadataread
Live transportnot available
No tools were enumerated, so prompt-injection, capability and toxic-flow analysis had no tool surface to inspect. To grade a package’s real runtime tools, scan the running server: --command "npx -y <package>".
Capability — what it could do if the model were manipulated
Tags derived from each tool’s schema and the implementation, not from what the tool calls itself. high is the level these add up to.
| Tool | Capability tags | Why the tag was assigned |
|---|---|---|
| No per-tool rows for this release — see the note below. | ||
can execute shell commands or code
Toxic-flow graph
The lethal trifecta, checked as a graph rather than as a checklist: untrusted input, a sensitive source and an external sink have to meet before there is a path worth worrying about.
The public result for this release does not print the flow graph, so there is nothing to show here. That is not the same as "no paths were found": what the scan did read is above, under coverage.
Supply chain and provenance
Integrityfirst-seen
Surface digest57bad78a1507ac0c
Scanned2026-11-10
This is the first scan of this surface here, so there is nothing yet to compare it against.
Every result on this tab comes from one deterministic pass over the published package — offline, rule by rule, and auditable line by line above. Same methodology version, same bytes, same score.
Release history
Always latest — the install command names no version, so it installs the newest release when it runs; the current release on file is 1.0.0. Pin a release below and the command asks for exactly that one.
1.0.0
undated
latestNo release note was published with this version.
—
no reviews yet
Who can review
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Sign in to write one
Any signed-in account that does not publish Yandex Metrika can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
No reviews yet
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.