Umami Compass MCP Server

umami-compass npm v0.5.1 Source verified

Published by webcredo — publish provenance cryptographically ties this package to that repository. That is proof of origin, not an official vendor package.

A secure, read-only MCP server for Umami Analytics 3.2+ — Cloud and self-hosted

Trust grade
A
97/100
Last scanned get badge →
Trust
A · 97/100
Adoption risk for you: the threat score, then adjusted down for blast radius, publisher verification and how much the scan could see. Deterministic; every point is auditable.
Capability
Moderate
Blast radius if it went rogue — what the server’s tools could reach. Independent of trust.
Coverage
Source
How much the scan could actually inspect. Shallow coverage is stated, never hidden.
Share this Trust Score
𝕏 Share LinkedIn Reddit
A Why this grade threat 100 − adoption risk = 97/100

The grade answers one question — how safe is this server for you to adopt — so it is computed in two auditable stages. Nothing below is an opinion or an LLM's guess; every line is a real term the deterministic engine applied, and the same input always yields the same number.

1. Threat score — 100 − 0 = 100. What the published surface and source actually contain:

The deterministic scan raised no scored threat in the surface it inspected — the threat score stayed at 100. Capability observations and advisory notes are recorded but never lower it.

2. Client adoption risk — 100 − 3 = 97. Three small, subtract-only factors that reflect your risk in adopting it — a clean scan proves less on a powerful, unverified or barely-inspectable package, so the grade says so plainly:

PointsAdoption-risk factor
−3 capability blast radius (moderate) — client exposure if the model is manipulated

Capability observations and info notes are shown under Findings but never scored. Open any row's finding below for the file, line and evidence behind a deduction.

Findings 0

✓ No findings. The scan raised nothing on this surface — see Coverage for how deep it could look.

Tools 42

Each tool and what it can reach — statically extracted from the published source.

  • get_pageviewsingests untrusted input
  • analyze_performance_portfoliono sensitive capability
  • analyze_release_impactno sensitive capability
  • compare_performance_breakdownno sensitive capability
  • compare_traffic_seriesno sensitive capability
  • compare_web_vitalsno sensitive capability
  • explain_traffic_changeno sensitive capability
  • get_active_visitorsno sensitive capability
  • get_event_seriesno sensitive capability
  • get_event_statsno sensitive capability
Show 32 more tools ↓
  • get_heatmapno sensitive capability
  • get_metricsno sensitive capability
  • get_performance_breakdownno sensitive capability
  • get_performance_cross_tabno sensitive capability
  • get_portfolio_overviewno sensitive capability
  • get_revenue_metricsno sensitive capability
  • get_revenue_statsno sensitive capability
  • get_route_group_performanceno sensitive capability
  • get_saved_reportno sensitive capability
  • get_server_infono sensitive capability
  • get_sessionno sensitive capability
  • get_session_activityno sensitive capability
  • get_session_statsno sensitive capability
  • get_web_vitalsno sensitive capability
  • get_websiteno sensitive capability
  • get_website_date_rangeno sensitive capability
  • get_website_statsno sensitive capability
  • list_eventsno sensitive capability
  • list_replaysno sensitive capability
  • list_saved_reportsno sensitive capability
  • list_segmentsno sensitive capability
  • list_sessionsno sensitive capability
  • list_websitesno sensitive capability
  • resolve_websiteno sensitive capability
  • run_attribution_reportno sensitive capability
  • run_breakdown_reportno sensitive capability
  • run_funnel_reportno sensitive capability
  • run_goal_reportno sensitive capability
  • run_journey_reportno sensitive capability
  • run_retention_reportno sensitive capability
  • run_utm_reportno sensitive capability
  • tracking_health_checkno sensitive capability

What this scan could not see

Versions 1

Scan history per published version. The engine is deterministic — the same version always yields the same score, so a changed score means the package itself changed.

VersionScoreFindingsEngineScanned
v0.5.1 latest A 97/100 0 1.13.0 2026-09-07

Embed this score

Show this server's live Trust Score in your README, docs or website. The badge is served straight from the registry and updates automatically after every rescan — no API key needed. It links back to this page, so anyone who sees the grade can also read the findings behind it instead of taking a number on faith.

MCP Trust Score: A · 97/100
Markdown (GitHub README)
[![MCP Trust Score](https://mcptrustchecker.com/registry/umami-compass/badge.svg)](https://mcptrustchecker.com/registry/umami-compass)
HTML
<a href="https://mcptrustchecker.com/registry/umami-compass"><img src="https://mcptrustchecker.com/registry/umami-compass/badge.svg" alt="MCP Trust Score" height="20"></a>
Prefer shields.io styling? Point it at https://mcptrustchecker.com/registry/umami-compass/badge.json via https://img.shields.io/endpoint?url=…

Verify this score yourself

The score above is reproducible: the same package version always yields the same result. Run it locally or over the free API — no account, no LLM, fully deterministic.

npx mcptrustchecker scan umami-compass --online

Use the free API → How scoring works

More in Cloud & DevOps