Umami (mikusnuz) MCP Server

@mikusnuz/umami-mcp npm v1.2.1

Published by @mikusnuz — no publish provenance, so origin is unverified, but the source is public: the repository link below is self-declared yet readable, so you can inspect the code before adopting it.

Full-coverage MCP server for Umami Analytics API v2

Trust grade
A
96/100
Last scanned get badge →
Trust
A · 96/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 = 96/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 − 4 = 96. 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
−1 publisher verification (public source) — no provenance, but the source is public and inspectable

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 66

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

  • get_pageviewsingests untrusted input
  • add_team_userno sensitive capability
  • add_team_websiteno sensitive capability
  • batch_eventsno sensitive capability
  • create_reportno sensitive capability
  • create_teamno sensitive capability
  • create_userno sensitive capability
  • create_websiteno sensitive capability
  • delete_reportno sensitive capability
  • delete_teamno sensitive capability
Show 56 more tools ↓
  • delete_userno sensitive capability
  • delete_websiteno sensitive capability
  • get_active_visitorsno sensitive capability
  • get_daterangeno sensitive capability
  • get_event_data_eventsno sensitive capability
  • get_event_data_fieldsno sensitive capability
  • get_event_data_statsno sensitive capability
  • get_event_data_valuesno sensitive capability
  • get_event_seriesno sensitive capability
  • get_event_valuesno sensitive capability
  • get_eventsno sensitive capability
  • get_meno sensitive capability
  • get_metricsno sensitive capability
  • get_my_teamsno sensitive capability
  • get_my_websitesno sensitive capability
  • get_realtimeno sensitive capability
  • get_reportno sensitive capability
  • get_sessionno sensitive capability
  • get_session_activityno sensitive capability
  • get_session_data_propertiesno sensitive capability
  • get_session_data_valuesno sensitive capability
  • get_session_propertiesno sensitive capability
  • get_session_statsno sensitive capability
  • get_sessionsno sensitive capability
  • get_sessions_weeklyno sensitive capability
  • get_shareno sensitive capability
  • get_statsno sensitive capability
  • get_teamno sensitive capability
  • get_team_userno sensitive capability
  • get_userno sensitive capability
  • get_user_teamsno sensitive capability
  • get_user_usageno sensitive capability
  • get_user_websitesno sensitive capability
  • get_websiteno sensitive capability
  • get_website_reportsno sensitive capability
  • heartbeatno sensitive capability
  • join_teamno sensitive capability
  • list_reportsno sensitive capability
  • list_team_usersno sensitive capability
  • list_team_websitesno sensitive capability
  • list_teamsno sensitive capability
  • list_usersno sensitive capability
  • list_websitesno sensitive capability
  • remove_team_userno sensitive capability
  • remove_team_websiteno sensitive capability
  • reset_websiteno sensitive capability
  • run_reportno sensitive capability
  • send_eventno sensitive capability
  • transfer_websiteno sensitive capability
  • update_my_passwordno sensitive capability
  • update_reportno sensitive capability
  • update_teamno sensitive capability
  • update_team_userno sensitive capability
  • update_userno sensitive capability
  • update_websiteno sensitive capability
  • verify_authno 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
v1.2.1 latest A 96/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 · 96/100
Markdown (GitHub README)
[![MCP Trust Score](https://mcptrustchecker.com/registry/mikusnuz-umami-mcp/badge.svg)](https://mcptrustchecker.com/registry/mikusnuz-umami-mcp)
HTML
<a href="https://mcptrustchecker.com/registry/mikusnuz-umami-mcp"><img src="https://mcptrustchecker.com/registry/mikusnuz-umami-mcp/badge.svg" alt="MCP Trust Score" height="20"></a>
Prefer shields.io styling? Point it at https://mcptrustchecker.com/registry/mikusnuz-umami-mcp/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 @mikusnuz/umami-mcp --online

Use the free API → How scoring works

Other implementations of Umami 4

Independent packages implementing the same tool, scanned with the same engine. Compare all 5 side by side →

More in API Development