yandex-metrika-mcp (IlyaVorozhbit/yandex-metrika-mcp) is an MCP server listed on the M8ven Trust Index. It scores 62 out of 100, grade C. It declares 52 tools. No publisher has claimed this listing.

Back to MCP Trust IndexM8ven
C
Caution
62/100

yandex-metrika-mcp

Enables AI assistants to retrieve comprehensive analytics data from Yandex Metrika accounts, including traffic, content, e-commerce, and user demographics.

→ IlyaVorozhbit/yandex-metrika-mcp· listed on glama

Caution. Specific findings reduced this grade. They are listed on the page. Grades reflect the full trust pyramid: code, verification depth, and reputation. New projects cap at C until adoption is earned.

How we verified

Code Verified⚡ Live Monitored: not connected

Verified is a snapshot. Live keeps it current, and builds your track record.

⚡ Connect GitHub → continuous verification on every pushwhy connect →

Who stands behind it

IlyaVorozhbit

Source: Glama

Is this your MCP?

Claim it to get a verified publisher badge, a free copy of our full audit findings, and direct contact for any high-priority issues we find. Or connect your repo for our deepest verification, Live Monitored: read-only, revoke anytime. What we access →

⚡ Connect GitHub for Live Monitored

Install from

Glamanot scored here

The grade above is for the source repository. Registries can serve a different version, so we mark the ones we were not able to read.

// key findings
⚠️
Known vulnerabilities in dependencies: 3 high
Affects packages this MCP installs at runtime. Upgrade or remove the affected dependency.
✅
No credential exfiltration, no sensitive file access, no obfuscation
Static analysis found nothing flowing your secrets to unexpected places.
✅
Open source with a license and README
Anyone can audit the code, the license is declared, and the publisher documents what it does.
🔐
You'll be asked for 1 credential: YANDEX_API_KEY
These are read from process.env at runtime. Make sure you trust where they’ll be sent.
// tools this server exposes26 tools

These names and descriptions are the publisher's own, read from the source code. We print them as written. Our assessment is the findings above, not this list.

get_account_info

Get account info from Yandex Metrika

get_visits

Get visits from Yandex Metrika. If date not provided, will return visits for the last 7 days.

sources_summary

Get sources summary report from Yandex Metrika. If date not provided, will return data for the last 7 days.

sources_search_phrases

Get search phrases report from Yandex Metrika. Returns data about search queries and browser information.

get_browsers_report

Get browsers report from Yandex Metrika without accounting for browser version.

get_content_analytics_sources

Get content analytics sources report from Yandex Metrika. Shows sources from which users were taken to website articles.

get_content_analytics_categories

Get content analytics categories report from Yandex Metrika. Shows overall statistics by category.

get_content_analytics_authors

Get content analytics authors report from Yandex Metrika. Shows statistics on the authors of website articles.

get_content_analytics_topics

Get content analytics topics report from Yandex Metrika. Shows statistics on the topics of website articles.

get_traffic_sources_types

Get data on different types of traffic sources (organic, direct, referral).

get_search_engines_data

Get number of sessions and users from search engines with optional filters.

get_regional_data

Get number of sessions and users for specific regions.

get_page_depth_analysis

Get number of sessions where users viewed more than specified number of pages.

get_goals_conversion

Get number of users and conversion rates for specified goals.

get_user_demographics

Get user demographics and engagement by device category.

get_device_analysis

Get user behavior by browser and operating system.

get_page_performance

Get pageviews by URL path (hit-level ym:pv: dimension). Bounce rate/duration not available per-page — those are session-level metrics only, use get_visits for site-wide values.

get_organic_search_performance

Get organic search performance by search engine and query.

get_new_users_by_source

Get which traffic sources are most effective in acquiring new users.

get_mobile_vs_desktop

Compare traffic and engagement metrics between mobile and desktop users.

get_geographical_organic_traffic

Analyze the geographical distribution of organic traffic.

get_yandex_direct_experiment

Get bounce rate for a specific Yandex Direct experiment.

get_content_analytics_articles

Get report on the number of article views on the website, grouped by article.

get_data_by_time

Get data for a specific period of time, grouped by time (day, week, month, quarter, year).

get_ecommerce_performance

Get e-commerce performance by product category and region. Provides insights into product performance (purchases, revenue) broken down by product category and geographical region.

get_conversion_rate_by_source_and_landing

Get conversion rate analysis by traffic source and landing page. Helps understand which traffic sources drive the most conversions to specific landing pages.

// known CVEs in dependencies3 high

Disclosed vulnerabilities in this server's declared npm dependencies (via OSV). Whether each is reachable depends on the installed versions.

high@modelcontextprotocol/sdk@1.16.0GHSA-345p-7cg4-v4c7

@modelcontextprotocol/sdk has cross-client data leak via shared server/transport instance reuse

high@modelcontextprotocol/sdk@1.16.0GHSA-8r9q-7v3j-jr4g

Anthropic's MCP TypeScript SDK has a ReDoS vulnerability

high@modelcontextprotocol/sdk@1.16.0GHSA-w48q-cv73-mx4w

Model Context Protocol (MCP) TypeScript SDK does not enable DNS rebinding protection by default

Depend on this server? Get alerted when its CVEs change.Watch this server free →
// environment variables
To run this server yourself, you supply these values. They go in your own MCP client configuration and stay on your machine. The secret label means the value is sensitive, not that the server mishandles it.
🔐 secretYANDEX_API_KEYclaude mcp add yandex-metrika -e =your_token_here -- node /path/to/yandex-metrika-mcp/build/index.js
// quality suggestions

Tool annotations

No tools have read-only/destructive annotations

Add readOnlyHint or destructiveHint annotations to every tool so hosts can warn users before invoking.

All four hints declared on every tool

52/52 tools missing one or more hints — get_account_info (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); get_visits (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); sources_summary (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint), +49 more. OpenAI's directory rejects tools where any of the four hints are missing or non-boolean.

For every tool, set all four hints (readOnlyHint, destructiveHint, idempotentHint, openWorldHint) to explicit true/false values that match the handler’s actual behaviour.

Tests exist

No test files found

Add tests that exercise each declared tool.

Production dependencies are patched

0 critical, 3 high severity in production deps — @modelcontextprotocol/sdk@1.16.0 (high), @modelcontextprotocol/sdk@1.16.0 (high)

Run npm audit fix, or upgrade the affected packages to a non-vulnerable version.

Claim the listing to review these findings one by one and send us a correction where you disagree, straight to the team. Claiming also means we tell you when the grade moves, and reach you first if we find anything urgent.

// full audit trail
The findings above are the summary. The full trail, every check we ran, each deduction, the network hosts observed and the dependency advisories, goes to verified publishers, along with an alert whenever a new one lands. Verified publishers can also review each finding and dispute it in one click. Publisher corrections have sharpened several of our checks this month, because the maintainer knows the codebase better than any scanner.
// improvement guidance — verified publishers only
We have 4 concrete improvements we can share with the publisher of this MCP. Each comes with specific guidance to raise the trust score.
// embed badge in your README
[![M8ven Verified](https://m8ven.ai/badge/mcp/ilyavorozhbit/yandex-metrika-mcp?variant=verified)](https://m8ven.ai/mcp/ilyavorozhbit/yandex-metrika-mcp)
Shows verification status without the grade. Want the grade badge instead? Remove ?variant=verified from the URL.
commit: 574d23fd3ec4b15b5f73b69ceea602b5a9046e9e
code hash: 73e72010801a9c10dfaa42d63f7f124ff7dca96b81b37c1313d9813fcc5942dd
view raw JSON →
Check MCPs from inside your assistant
Tool Check · MCP

Vetting this one by hand? Tool Check is an MCP that scores other MCPs. Add it once and ask Claude, ChatGPT, or any MCP client to grade a server, surface CVEs, check the publisher, and suggest safer alternatives — before you install.

https://m8ven.ai/api/mcp/tool-check
check_toolsearch_toolscompare_toolsrecommend_alternativescheck_publisherreport_concern
How to add it →Free · no account needed · works in any MCP client