yandex-metrika-mcp
NPM · @THEYAHIA/YANDEX-METRIKA-MCP · SCANNED AUG 6
MCP server for Yandex Metrika — web analytics, counters, goals, traffic (Russia)
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 →
Supply Chain Security87
- No malware found by supply-chain analysis.Pass
- Known CVEs were checked across the 95 of 99 dependencies we could resolve, so this covers what we could see, not the whole tree.Partial
- No install/post-install scripts declared.Pass
- Dependency health was assessed across the 95 of 99 dependencies we could resolve, so this covers what we could see, not the whole tree. View diagnostics → Partial
Provenance & Transparency45
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 126 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability63
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 1552 tokens (~103/item across 15 items; 15 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management33
- Stability observed for 10 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
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.
npm · @theyahia/yandex-metrika-mcp
claude mcp add theyahia-yandex-metrika-mcp -- npx -y @theyahia/yandex-metrika-mcp
codex mcp add theyahia-yandex-metrika-mcp -- npx -y @theyahia/yandex-metrika-mcp
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"theyahia-yandex-metrika-mcp": {
"type": "local",
"command": [
"npx",
"-y",
"@theyahia/yandex-metrika-mcp"
],
"enabled": true
}
}
} openclaw mcp add theyahia-yandex-metrika-mcp --command npx --arg -y --arg @theyahia/yandex-metrika-mcp
mcp_servers:
theyahia-yandex-metrika-mcp:
command: "npx"
args: ["-y", "@theyahia/yandex-metrika-mcp"] {
"mcpServers": {
"theyahia-yandex-metrika-mcp": {
"command": "npx",
"args": [
"-y",
"@theyahia/yandex-metrika-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.
- 6 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 30 to 33. That category is still filling its 30-day observation window: 9 days of observed history at the previous scan, 10 at this one. The score rises as the window fills, whether or not the server changes.
- 5 Aug 26 +1
- CVE-2026-69207 no longer affects this package ▲ security
- Known CVEs: fail → partial ▲ security
- 4 Aug 26 0
- CVE-2026-69207 affects this package: medium ▼ security
- Known CVEs: partial → fail ▼ security
- 3 Aug 26 +30
- Provenance: unverified → fail ▼ security
- Install scripts: unverified → pass ▲ security
- Known CVEs: unverified → partial ▲ security
- Dependency health: unverified → partial ▲ functional
- License: unverified → pass ▲ functional
- Maintenance: unverified → pass ▲ functional
- MCP protocol: unverified → pass ▲ functional
- Stability: unverified → 0.23 ▲ functional
- Schema quality: unverified → good ▲ functional
- Licence: MIT functional
- 2 Aug 26 +10
- Malware scan: unverified → pass ▲ security
- Stability: Stability not yet verified: we do not have a sandbox capture of the MCP schema this version of the package serves yet. security
- Capabilities: pass → unverified ▼ functional
- 1 Aug 26 +5
- Stability: Stability not yet verified: not enough scan history yet (needs a 30-day window). security
- MCP protocol: unverified → pass ▲ functional
- 31 Jul 26 −25
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 27 Jul 26 46
First indexed and scored.
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 6 Aug 2026 · Analysed npm/@theyahia/[email protected]
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Dependencies 95 packages
| Packages resolved | 95 |
|---|---|
| Deprecated | 95 |
| Stale | 29 |
| Tree resolution | Partial |
The dependency tree was only partially resolved, so these counts may be incomplete.
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.
create_counter ~83
Create a new Yandex.Metrica counter for a website. Returns the new counter ID and tracking code. You need to install the tracking code on the site afterwards.
| Name | Type | Req | Description |
|---|---|---|---|
| mirrors | array | — | Mirror domains to track alongside the main site |
| name | string | yes | Counter display name |
| site | string | yes | Website domain (e.g. 'example.com') |
No output schema declared.
No examples provided.
create_goal ~133
Create a new conversion goal for a counter. Supports types: 'url' (page visit), 'number' (page count threshold), 'step' (multi-step funnel), 'action' (JavaScript event).
| Name | Type | Req | Description |
|---|---|---|---|
| conditions | array | — | Conditions array. Required for url, step, action goal types. |
| counter_id | number | yes | Counter ID to create the goal in |
| name | string | yes | Goal display name |
| type | string | yes | Goal type: 'url' (page visit), 'number' (page count), 'step' (multi-step funnel), 'action' (JS event) |
No output schema declared.
No examples provided.
delete_counter ~51
Permanently delete a Yandex.Metrica counter. This action is irreversible — all historical data for this counter will be lost.
| Name | Type | Req | Description |
|---|---|---|---|
| counter_id | number | yes | Counter ID to delete. This action is irreversible. |
No output schema declared.
No examples provided.
delete_goal ~50
Delete a conversion goal from a counter. Historical goal data in reports is preserved.
| Name | Type | Req | Description |
|---|---|---|---|
| counter_id | number | yes | Counter ID the goal belongs to |
| goal_id | number | yes | Goal ID to delete |
No output schema declared.
No examples provided.
export_logs ~159
Export raw visit or hit logs via the Logs API. Creates a log request and evaluates feasibility. Use source='visits' for session data, source='hits' for pageview data.
| Name | Type | Req | Description |
|---|---|---|---|
| counter_id | number | yes | ID счётчика Яндекс.Метрики |
| date1 | string | yes | Дата начала в формате YYYY-MM-DD |
| date2 | string | yes | Дата окончания в формате YYYY-MM-DD |
| fields | string | — | Поля через запятую. По умолчанию для visits: ym:s:date,ym:s:clientID,ym:s:lastTrafficSource,ym:s:visitDuration |
| source | string | — | Тип данных: visits (визиты) или hits (просмотры) |
No output schema declared.
No examples provided.
get_counter ~48
Get full details of a single Yandex.Metrica counter by ID, including configuration, code snippet status, and goals count.
| Name | Type | Req | Description |
|---|---|---|---|
| counter_id | number | yes | Counter ID to retrieve details for |
No output schema declared.
No examples provided.
get_report ~290
Flexible Yandex.Metrica reporting endpoint. Query any combination of metrics (ym:s:visits, ym:s:pageviews, ym:s:bounceRate, ym:s:avgVisitDurationSeconds, ym:s:users, ym:s:newUsers, etc.) with dimensions (ym:s:trafficSource, ym:s:searchEngine, ym:s:country, ym:s:browser, ym:s:deviceCategory, ym:s:date, etc.) over a date range. Supports filters and sorting.
| Name | Type | Req | Description |
|---|---|---|---|
| counter_id | number | yes | Yandex.Metrica counter ID |
| date1 | string | yes | Start date YYYY-MM-DD |
| date2 | string | yes | End date YYYY-MM-DD |
| dimensions | array | — | Dimensions array, e.g. ['ym:s:trafficSource', 'ym:s:browser', 'ym:s:country', 'ym:s:deviceCategory'] |
| filters | string | — | Filter expression, e.g. ym:s:trafficSource=='organic' |
| limit | number | — | Max rows to return (default 100) |
| metrics | array | yes | Metrics array, e.g. ['ym:s:visits', 'ym:s:pageviews', 'ym:s:bounceRate', 'ym:s:avgVisitDurationSeconds'] |
| sort | string | — | Sort field, prefix with '-' for descending, e.g. '-ym:s:visits' |
No output schema declared.
No examples provided.
get_report_comparison ~138
Compare metrics between two date periods (A vs B). Useful for week-over-week, month-over-month, or campaign before/after analysis.
| Name | Type | Req | Description |
|---|---|---|---|
| counter_id | number | yes | Yandex.Metrica counter ID |
| date1_a | string | yes | Period A start date YYYY-MM-DD |
| date1_b | string | yes | Period B start date YYYY-MM-DD |
| date2_a | string | yes | Period A end date YYYY-MM-DD |
| date2_b | string | yes | Period B end date YYYY-MM-DD |
| dimensions | array | — | Dimensions to group by |
| metrics | array | yes | Metrics to compare |
No output schema declared.
No examples provided.
get_report_drilldown ~131
Drill down into report data hierarchically. Start at top level, then pass parent_id to explore sub-dimensions (e.g., country -> city, traffic source -> campaign).
| Name | Type | Req | Description |
|---|---|---|---|
| counter_id | number | yes | Yandex.Metrica counter ID |
| date1 | string | yes | Start date YYYY-MM-DD |
| date2 | string | yes | End date YYYY-MM-DD |
| dimensions | array | yes | Dimensions for drill-down hierarchy |
| metrics | array | yes | Metrics to retrieve |
| parent_id | string | — | Parent row ID to drill into. Omit for top-level. |
No output schema declared.
No examples provided.
get_top_pages ~99
Top pages by pageviews for a counter. Returns URL, visits, pageviews, bounce rate, and avg duration for each page. Useful for content performance analysis.
| Name | Type | Req | Description |
|---|---|---|---|
| counter_id | number | yes | Yandex.Metrica counter ID |
| date1 | string | yes | Start date YYYY-MM-DD |
| date2 | string | yes | End date YYYY-MM-DD |
| limit | number | — | Number of pages to return (default 20) |
No output schema declared.
No examples provided.
get_traffic_sources ~82
Traffic sources breakdown — visits and users by source channel (organic search, direct, social, referral, ad). Quick way to see where traffic comes from.
| Name | Type | Req | Description |
|---|---|---|---|
| counter_id | number | yes | Yandex.Metrica counter ID |
| date1 | string | yes | Start date YYYY-MM-DD |
| date2 | string | yes | End date YYYY-MM-DD |
No output schema declared.
No examples provided.
get_traffic_summary ~82
Quick traffic overview for a counter over a date range. Returns visits, pageviews, unique users, bounce rate, and average visit duration in one call.
| Name | Type | Req | Description |
|---|---|---|---|
| counter_id | number | yes | Yandex.Metrica counter ID |
| date1 | string | yes | Start date YYYY-MM-DD |
| date2 | string | yes | End date YYYY-MM-DD |
No output schema declared.
No examples provided.
list_counters ~97
List all Yandex.Metrica counters available to the authenticated user. Returns counter ID, name, site URL, and status. Supports search filtering.
| Name | Type | Req | Description |
|---|---|---|---|
| field | string | — | Fields to return, comma-separated (e.g. 'name,site,status') |
| per_page | number | — | Results per page (default 100, max 10000) |
| search_string | string | — | Filter counters by name or site URL substring |
No output schema declared.
No examples provided.
list_goals ~51
List all goals configured for a Yandex.Metrica counter. Goals track conversions like page visits, button clicks, or multi-step funnels.
| Name | Type | Req | Description |
|---|---|---|---|
| counter_id | number | yes | Counter ID to list goals for |
No output schema declared.
No examples provided.
update_counter ~58
Update an existing Yandex.Metrica counter — change its name or site URL.
| Name | Type | Req | Description |
|---|---|---|---|
| counter_id | number | yes | Counter ID to update |
| name | string | — | New counter display name |
| site | string | — | New website domain |
No output schema declared.
No examples provided.