io.github.BoxLab-Ltd/yandex-metrica-mcp
NPM · YANDEX-METRICA-MCP · SCANNED SEP 20
Query Yandex Metrica analytics — reports, trends, metadata and raw log exports — via an AI agent.
Available components
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security98
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- 31 of 96 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency100
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to BoxLab-Ltd/yandex-metrica-mcp). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 60 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability65
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 3301 tokens (~275/item across 12 items; 12 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management93
- Stability observed for 28 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 12 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 12 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
How do I install the io.github.BoxLab-Ltd/yandex-metrica-mcp server?
io.github.BoxLab-Ltd/yandex-metrica-mcp runs locally as an npm package, launched with npx -y yandex-metrica-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · yandex-metrica-mcp
claude mcp add boxlab-ltd-yandex-metrica-mcp -- npx -y yandex-metrica-mcp
{
"mcpServers": {
"boxlab-ltd-yandex-metrica-mcp": {
"command": "npx",
"args": [
"-y",
"yandex-metrica-mcp"
]
}
}
} {
"servers": {
"boxlab-ltd-yandex-metrica-mcp": {
"command": "npx",
"args": [
"-y",
"yandex-metrica-mcp"
]
}
}
} codex mcp add boxlab-ltd-yandex-metrica-mcp -- npx -y yandex-metrica-mcp
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"boxlab-ltd-yandex-metrica-mcp": {
"type": "local",
"command": [
"npx",
"-y",
"yandex-metrica-mcp"
],
"enabled": true
}
}
} openclaw mcp add boxlab-ltd-yandex-metrica-mcp --command npx --arg -y --arg yandex-metrica-mcp
mcp_servers:
boxlab-ltd-yandex-metrica-mcp:
command: "npx"
args: ["-y", "yandex-metrica-mcp"] {
"McpServers": {
"boxlab-ltd-yandex-metrica-mcp": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"yandex-metrica-mcp"
]
}
}
} assistant mcp add boxlab-ltd-yandex-metrica-mcp -t stdio -c npx -a -y yandex-metrica-mcp
{
"mcpServers": {
"boxlab-ltd-yandex-metrica-mcp": {
"command": "npx",
"args": [
"-y",
"yandex-metrica-mcp"
]
}
}
} Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 19 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.
- 17 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.
- 15 Sept 26 −3
- Stability: pass → 0.77 functional
- 14 Sept 26 0
- Stability: 0.97 → pass security
- 13 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 11 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.
- 9 Sept 26 −2
- Stability: pass → 0.83 functional
- 8 Sept 26 0
- Stability: 0.97 → pass security
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 20 Sept 2026 · Analysed npm/yandex-metrica-mcp@0.3.0
Provenance Verified
A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.
| Result | Verified |
|---|---|
| Ecosystem | npm |
| Reason | Verified |
| Discovered via | Registry attestation endpoint |
| Source repo | BoxLab-Ltd/yandex-metrica-mcp |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/BoxLab-Ltd/yandex-metrica-mcp/.github/workflows/release.yml@refs/tags/v0.3.0 |
| Rekor log index | 2212214588 |
| Predicate type | https://slsa.dev/provenance/v1 |
| Subject digest | sha512:f54ec5dd4cef91d07e5736567b93ed650356976d9649cb935c3872838ac768cf04df083ebe6f5580b5612f2cfbd51bb576f311ea7efad78c97dbe51eb |
Background: How many MCP packages publish verified provenance →
Dependencies 96 packages
| Packages resolved | 96 |
|---|---|
| Stale | 31 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
describe_counter Describe Metrica counter ~195
Read a single counter's configuration — settings, goals, segments, filters, operations and access grants — choosing sections with `include`. The goals section returns the goal ids needed to build conversion metrics (ym:s:goal<id>reaches / conversionRate) in run_report, so call this with include=["goals"] before any conversion question. To list the account's counters, use get_metadata. Read-only.
| Name | Type | Req | Description |
|---|---|---|---|
| counterId | integer | – | Yandex Metrica counter id. Optional if YANDEX_METRIKA_COUNTER_ID is configured. |
| fullResponse | boolean | – | If true, return the full raw objects with every field. Default false: a curated subset to save context. |
| include | array | – | Which configuration sections to return. Default ["settings","goals"]. "goals" gives the goal ids needed for conversion metrics in run_report; "grants" is a read-only access audit. |
No output schema declared.
No examples provided.
get_metadata Get Metrica metadata ~83
Discovery tool. Lists the counters available to your token plus a curated catalog of common dimensions and metrics (Metrica has no enumeration API), attribution options and Logs API fields. Call this before run_report or logs_request to use real field names and to find a counterId. For a counter's own goals, segments, filters or grants, use describe_counter. Read-only.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
login Sign in to Yandex ~108
Sign in to Yandex from here. Opens your browser to approve access; the code returns automatically over a local redirect, so this usually finishes in one call. If the local port is unavailable it returns a URL to approve and you then call submit_code with the code Yandex shows. Run this once (the token lasts ~1 year); needed before the data tools if you are not signed in yet.
| Name | Type | Req | Description |
|---|---|---|---|
| oob | boolean | – | Force the copy-paste flow instead of the automatic local redirect. |
No output schema declared.
No examples provided.
logs_clean Clean or cancel a Metrica log request ~92
Free the counter storage quota by cleaning a finished (processed) log request, or cancel one still being prepared. Dispatches by current status. Destructive: cleaned data must be requested again to download later.
| Name | Type | Req | Description |
|---|---|---|---|
| counterId | integer | – | Yandex Metrica counter id. Optional if YANDEX_METRIKA_COUNTER_ID is configured. |
| requestId | integer | yes | Log request id returned by logs_request. |
No output schema declared.
No examples provided.
logs_download Download Metrica raw logs ~226
Download prepared log data for a request_id (must be status="processed"; check logs_status). Default mode "sample" returns up to maxRows parsed rows inline — cheap and bounded. Mode "file" streams the FULL export to a file and returns its path plus a small preview; the raw content (potentially millions of rows) is never loaded into context. Read-only.
| Name | Type | Req | Description |
|---|---|---|---|
| counterId | integer | – | Yandex Metrica counter id. Optional if YANDEX_METRIKA_COUNTER_ID is configured. |
| maxRows | integer | – | sample mode only: max rows to return inline (default 100, max 1000). |
| mode | string | – | sample (default): return up to maxRows parsed rows inline — cheap, bounded, no file. file: stream the FULL export to a file and return its path plus a small preview. |
| outputPath | string | – | file mode only: absolute path to write the export to. Defaults to a file in the configured logs directory. |
| requestId | integer | yes | Log request id returned by logs_request. |
No output schema declared.
No examples provided.
logs_request Request Metrica raw logs ~380
Create a Yandex Metrica Logs API request for RAW, un-sampled rows (source="visits" sessions or "hits" events) over a date range. Checks feasibility, then queues preparation (takes minutes). Returns a request_id to poll with logs_status; then logs_download, then logs_clean. Discover field ids with get_metadata. Not read-only: preparing data consumes the counter storage quota.
| Name | Type | Req | Description |
|---|---|---|---|
| attribution | string | – | Attribution model for attribution-dependent fields: FIRST | LAST | LASTSIGN | CROSS_DEVICE_LAST_SIGNIFICANT | AUTOMATIC | ... Default LASTSIGN. |
| counterId | integer | – | Yandex Metrica counter id. Optional if YANDEX_METRIKA_COUNTER_ID is configured. |
| date1 | string | yes | Start date as a concrete YYYY-MM-DD (relative dates are not supported for logs). date2 must be earlier than today — the current day's data is not ready. |
| date2 | string | yes | End date as a concrete YYYY-MM-DD (relative dates are not supported for logs). date2 must be earlier than today — the current day's data is not ready. |
| fields | array | yes | Log field ids to export, e.g. ["ym:s:visitID","ym:s:dateTime","ym:s:startURL"]. All must share the source's prefix (ym:s: for visits, ym:pv: for hits). Discover valid ids with get_metadata (logs_fiel… |
| source | string | yes | Raw data source. "visits" = sessions (ym:s: fields); "hits" = page views/events (ym:pv: fields). Fields must match the source. |
| waitSeconds | integer | – | Optionally poll up to this many seconds for preparation to finish before returning (handy for small exports). Default 0 = return immediately; poll with logs_status afterwards. |
No output schema declared.
No examples provided.
logs_status Check Metrica log requests ~111
Inspect a Logs API request by request_id (status, parts, size, next step), or omit request_id to list all of the counter's log requests and current storage-quota usage. Poll this after logs_request until status="processed". Read-only.
| Name | Type | Req | Description |
|---|---|---|---|
| counterId | integer | – | Yandex Metrica counter id. Optional if YANDEX_METRIKA_COUNTER_ID is configured. |
| requestId | integer | – | Log request id to inspect. Omit to list all requests and current quota usage. |
No output schema declared.
No examples provided.
run_comparison Compare Metrica segments ~594
Compare two segments/periods (A vs B) for the same metrics and dimensions (/stat/v1/data/comparison). Returns per-metric values for A and B plus the absolute and percentage delta, computed server-side: delta = B − A (segment A is the baseline), delta_pct = (B − A) / A × 100. Defaults to last 7 days (B) vs the prior 7 days (A), so a positive delta means growth. Read-only.
| Name | Type | Req | Description |
|---|---|---|---|
| accuracy | string | – | Sampling accuracy: low | medium | high | full, or a 0..1 share. Use "full" for exact data. |
| counterId | integer | – | Yandex Metrica counter id. Optional if YANDEX_METRIKA_COUNTER_ID is configured. |
| date1A | string | – | Segment A start date as YYYY-MM-DD or relative (today, yesterday, NdaysAgo). |
| date1B | string | – | Segment B start date as YYYY-MM-DD or relative (today, yesterday, NdaysAgo). |
| date2A | string | – | Segment A end date as YYYY-MM-DD or relative (today, yesterday, NdaysAgo). |
| date2B | string | – | Segment B end date as YYYY-MM-DD or relative (today, yesterday, NdaysAgo). |
| dimensions | array | – | Dimension ids to group by, e.g. ["ym:s:lastsignTrafficSource"]. Max 10. Do not mix ym:s: and ym:pv: namespaces. |
| filtersA | string | – | Filter expression for segment A. |
| filtersB | string | – | Filter expression for segment B. |
| fullResponse | boolean | – | If true, include all dimension sub-fields (id, icons, …). Default false: only the dimension name and metric values are returned, to save context. |
| includeUndefined | boolean | – | Include rows where the first dimension value is undefined ("Not set"). Default false. |
| limit | integer | – | Rows per page (max 100000). Defaults to a small value to protect context. |
| metrics | array | yes | Metric ids, e.g. ["ym:s:visits","ym:s:users"]. Max 20. Discover valid ids with get_metadata. Do not mix ym:s: (visits) and ym:pv: (hits) namespaces in one call. |
| offset | integer | – | 1-based index of the first row to return, for pagination. Default 1. |
| preset | string | – | Named Metrica report preset (advanced); can substitute for metrics/dimensions. |
| sort | array | – | Sort fields; prefix a field with "-" for descending, e.g. ["-ym:s:visits"]. |
| timezone | string | – | Timezone offset for the report as ±hh:mm, e.g. "+03:00". Defaults to the counter timezone. |
No output schema declared.
No examples provided.
run_drilldown Drill down a Metrica report ~522
Return one level of a hierarchical (tree) report (/stat/v1/data/drilldown). Each row has an "expandable" flag; pass parentId with the path of dimension keys to expand deeper. Requires dimensions. Read-only.
| Name | Type | Req | Description |
|---|---|---|---|
| accuracy | string | – | Sampling accuracy: low | medium | high | full, or a 0..1 share. Use "full" for exact data. |
| counterId | integer | – | Yandex Metrica counter id. Optional if YANDEX_METRIKA_COUNTER_ID is configured. |
| date1 | string | – | Start date as YYYY-MM-DD or relative (today, yesterday, NdaysAgo). |
| date2 | string | – | End date as YYYY-MM-DD or relative (today, yesterday, NdaysAgo). |
| dimensions | array | – | Dimension ids to group by, e.g. ["ym:s:lastsignTrafficSource"]. Max 10. Do not mix ym:s: and ym:pv: namespaces. |
| filters | string | – | Metrica filter expression in native syntax, e.g. ym:s:regionCityName=='Moscow' AND ym:pv:URL=@'help'. |
| fullResponse | boolean | – | If true, include all dimension sub-fields (id, icons, …). Default false: only the dimension name and metric values are returned, to save context. |
| includeUndefined | boolean | – | Include rows where the first dimension value is undefined ("Not set"). Default false. |
| limit | integer | – | Rows per page (max 100000). Defaults to a small value to protect context. |
| metrics | array | yes | Metric ids, e.g. ["ym:s:visits","ym:s:users"]. Max 20. Discover valid ids with get_metadata. Do not mix ym:s: (visits) and ym:pv: (hits) namespaces in one call. |
| offset | integer | – | 1-based index of the first row to return, for pagination. Default 1. |
| parentId | array | – | Path from the tree root as a list of dimension keys. Omit for the top level. |
| preset | string | – | Named Metrica report preset (advanced); can substitute for metrics/dimensions. |
| sort | array | – | Sort fields; prefix a field with "-" for descending, e.g. ["-ym:s:visits"]. |
| timezone | string | – | Timezone offset for the report as ±hh:mm, e.g. "+03:00". Defaults to the counter timezone. |
No output schema declared.
No examples provided.
run_report Run Metrica report ~498
Query a Yandex Metrica table report (/stat/v1/data): one or more metrics grouped by dimensions over a date range, with optional filter and sort. Read-only. Use get_metadata first to discover valid metric/dimension ids and the account counters.
| Name | Type | Req | Description |
|---|---|---|---|
| accuracy | string | – | Sampling accuracy: low | medium | high | full, or a 0..1 share. Use "full" for exact data. |
| counterId | integer | – | Yandex Metrica counter id. Optional if YANDEX_METRIKA_COUNTER_ID is configured. |
| date1 | string | – | Start date as YYYY-MM-DD or relative (today, yesterday, NdaysAgo). |
| date2 | string | – | End date as YYYY-MM-DD or relative (today, yesterday, NdaysAgo). |
| dimensions | array | – | Dimension ids to group by, e.g. ["ym:s:lastsignTrafficSource"]. Max 10. Do not mix ym:s: and ym:pv: namespaces. |
| filters | string | – | Metrica filter expression in native syntax, e.g. ym:s:regionCityName=='Moscow' AND ym:pv:URL=@'help'. |
| fullResponse | boolean | – | If true, include all dimension sub-fields (id, icons, …). Default false: only the dimension name and metric values are returned, to save context. |
| includeUndefined | boolean | – | Include rows where the first dimension value is undefined ("Not set"). Default false. |
| limit | integer | – | Rows per page (max 100000). Defaults to a small value to protect context. |
| metrics | array | yes | Metric ids, e.g. ["ym:s:visits","ym:s:users"]. Max 20. Discover valid ids with get_metadata. Do not mix ym:s: (visits) and ym:pv: (hits) namespaces in one call. |
| offset | integer | – | 1-based index of the first row to return, for pagination. Default 1. |
| preset | string | – | Named Metrica report preset (advanced); can substitute for metrics/dimensions. |
| sort | array | – | Sort fields; prefix a field with "-" for descending, e.g. ["-ym:s:visits"]. |
| timezone | string | – | Timezone offset for the report as ±hh:mm, e.g. "+03:00". Defaults to the counter timezone. |
No output schema declared.
No examples provided.
run_timeseries Metrica metrics over time ~442
Return metrics split into a time series (/stat/v1/data/bytime): each metric comes back as an array of values, one per interval (day/week/month/…) over the date range. Use for trends and charts. Optionally group by dimensions (topKeys rows). Read-only.
| Name | Type | Req | Description |
|---|---|---|---|
| accuracy | string | – | Sampling accuracy: low | medium | high | full, or a 0..1 share. Use "full" for exact data. |
| counterId | integer | – | Yandex Metrica counter id. Optional if YANDEX_METRIKA_COUNTER_ID is configured. |
| date1 | string | – | Start date as YYYY-MM-DD or relative (today, yesterday, NdaysAgo). |
| date2 | string | – | End date as YYYY-MM-DD or relative (today, yesterday, NdaysAgo). |
| dimensions | array | – | Dimension ids to group by, e.g. ["ym:s:lastsignTrafficSource"]. Max 10. Do not mix ym:s: and ym:pv: namespaces. |
| filters | string | – | Metrica filter expression in native syntax, e.g. ym:s:regionCityName=='Moscow' AND ym:pv:URL=@'help'. |
| fullResponse | boolean | – | If true, include all dimension sub-fields (id, icons, …). Default false: only the dimension name and metric values are returned, to save context. |
| group | string | – | Time interval granularity. Default day. |
| includeUndefined | boolean | – | Include rows where the first dimension value is undefined ("Not set"). Default false. |
| metrics | array | yes | Metric ids, e.g. ["ym:s:visits","ym:s:users"]. Max 20. Discover valid ids with get_metadata. Do not mix ym:s: (visits) and ym:pv: (hits) namespaces in one call. |
| timezone | string | – | Timezone offset for the report as ±hh:mm, e.g. "+03:00". Defaults to the counter timezone. |
| topKeys | integer | – | Max number of dimension rows to chart (max 30). Default 7. |
No output schema declared.
No examples provided.
submit_code Submit the Yandex sign-in code ~50
Complete a copy-paste sign-in started by login: pass the code Yandex showed you after you approved access.
| Name | Type | Req | Description |
|---|---|---|---|
| code | string | yes | The code shown on the Yandex page after you approved access. |
No output schema declared.
No examples provided.
What is the io.github.BoxLab-Ltd/yandex-metrica-mcp server?
io.github.BoxLab-Ltd/yandex-metrica-mcp is listed in the public MCP registry as io.github.BoxLab-Ltd/yandex-metrica-mcp. Query Yandex Metrica analytics, reports, trends, metadata and raw log exports, via an AI agent. This page covers its npm package (yandex-metrica-mcp).
Is the io.github.BoxLab-Ltd/yandex-metrica-mcp server safe to use?
io.github.BoxLab-Ltd/yandex-metrica-mcp scores 92 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 20 September 2026. It declares no install or post-install scripts. Its build provenance is signed and verified. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the io.github.BoxLab-Ltd/yandex-metrica-mcp server expose?
io.github.BoxLab-Ltd/yandex-metrica-mcp exposes 12 tools: login, submit_code, get_metadata, describe_counter, run_report, and 7 more. Their descriptions and schemas cost roughly 3,301 tokens of context every time the server is loaded.
Is the io.github.BoxLab-Ltd/yandex-metrica-mcp server still maintained?
io.github.BoxLab-Ltd/yandex-metrica-mcp is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the io.github.BoxLab-Ltd/yandex-metrica-mcp server under?
io.github.BoxLab-Ltd/yandex-metrica-mcp declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.