Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

io.github.mikusnuz/umami

NPM · @MIKUSNUZ/UMAMI-MCP

MCP server for Umami Analytics v3 — analytics, boards, links, pixels, reports, replay, and more

Available components

0 this week 76 Trust /100

Last scanned (15 hours ago)

Scores higher than 53% of npm servers

Category Data and Analytics

Trust breakdown (7 categories)

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 Security81
  • No malware found by supply-chain analysis.Pass
  • CVE check failed: a known high-severity CVE affects zod 3.25.76, a direct dependency. A fixed version is available. View diagnostics → Fail
  • No install/post-install scripts declared.Pass
  • 31 of 93 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
Schema Quality & AI Usability74
  • 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
  • AI-judged instruction clarity (fair).Partial
  • Tool/resource definitions use about 7715 tokens (~57/item across 135 items; 133 tools + 2 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
  • No destabilizing schema changes in the last 30 days.Pass
Tool Coverage83
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 49% of tool parameters carry a description.Partial
Tool Safety75
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • 0 of 19 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "delete_website" implies "delete" and declares no destructiveHint at all, which the MCP spec reads as destructive by default. See how to fix → Fail
  • An AI judge read all 134 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
What we tested

Checks we ran (16)

  • Malware scan
  • Known CVEs
  • Install scripts
  • Dependency health
  • Source repository
  • Provenance
  • License
  • Maintenance
  • Security disclosure
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Does not apply to this package (2)

  • Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
  • Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.

The score does not measure everything. What the score does not measure →

Changelog

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.

  • 9 Nov 26 +5
    • Source repository: unverified → pass ▲ security
  • 8 Nov 26 −4
    • Provenance: pass → unverified ▼ security
    • Stability: 0.97 → pass security
  • 6 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.

  • 4 Nov 26 0
    • Stability: fail → 0.87 functional
  • 29 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 82 to 86.

  • 28 Oct 26 −1

    No change was recorded against any check on this day. Stability & Change Management went from 86 to 82.

  • 24 Oct 26 −5
    • CVE-2023-54404 affects this package: high ▼ security
    • Known CVEs: pass → fail ▼ security
  • 20 Oct 26 0
    • Malware scan: unverified → pass ▲ security
Diagnostics

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 21 Nov 2026 · Analysed npm/@mikusnuz/umami-mcp@2.1.1

Provenance No attestation

The registry publishes no build provenance for this version, so there is nothing to verify.

Result No attestation
Ecosystem npm

Background: How many MCP packages publish verified provenance →

Vulnerabilities 1 finding
ID CVE Severity Vector Fix available
GHSA-mrhx-c7xc-m3w5 CVE-2023-54404 high CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H yes

Background: What a vulnerability scan can and cannot prove →

Dependencies 93 packages
Packages resolved 93
Stale 31
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 133 exposed · ~7,691 tokens

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 →

Tool Tokens
list_team_pixels ~63

List tracking pixels belonging to a team

NameTypeReqDescription
orderBystring––
pageinteger––
pageSizeinteger––
searchstring––
sortDescendingboolean––
teamIdstringyes–

No output schema declared.

No examples provided.

list_team_users ~61

List all members of a team

NameTypeReqDescription
pagenumber–Page number (1-based)
pageSizenumber–Results per page
searchstring–Search query to filter members
teamIdstringyesTeam UUID

No output schema declared.

No examples provided.

list_team_websites ~80

List all websites that belong to a team

NameTypeReqDescription
orderBystring––
pagenumber–Page number (1-based)
pageSizenumber–Results per page
searchstring–Search query to filter websites
sortDescendingboolean––
teamIdstringyesTeam UUID

No output schema declared.

No examples provided.

list_teams ~70

List all teams

NameTypeReqDescription
orderBystring–Field to order by (e.g. 'name', 'createdAt')
pagenumber–Page number (1-based)
pageSizenumber–Results per page (default 10)
sortDescendingboolean––

No output schema declared.

No examples provided.

list_users ~84

List all users (admin only)

NameTypeReqDescription
orderBystring–Field to order by (e.g. 'username', 'createdAt')
pagenumber–Page number (1-based)
pageSizenumber–Results per page (default 10)
searchstring–Search query to filter users
sortDescendingboolean––

No output schema declared.

No examples provided.

list_website_shares ~48

List shares created for a website

NameTypeReqDescription
pageinteger––
pageSizeinteger––
searchstring––
websiteIdstringyes–

No output schema declared.

No examples provided.

list_websites ~98

List all websites tracked in Umami

NameTypeReqDescription
includeTeamsboolean–Include team-accessible websites
orderBystring–Field to order by (e.g. 'name', 'domain')
pagenumber–Page number (1-based)
pageSizenumber–Results per page (default 10)
searchstring–Search query to filter websites
sortDescendingboolean––

No output schema declared.

No examples provided.

remove_team_user ~38

Remove a user from a team

NameTypeReqDescription
teamIdstringyesTeam UUID
userIdstringyesUser UUID to remove

No output schema declared.

No examples provided.

reset_user_two_factor ~35

Reset a user's 2FA enrollment and backup codes (self-hosted admin only)

NameTypeReqDescription
userIdstringyes–

No output schema declared.

No examples provided.

reset_website ~34

Reset a website by removing all its analytics data (irreversible)

NameTypeReqDescription
websiteIdstringyesWebsite UUID to reset

No output schema declared.

No examples provided.

run_report ~75

Execute a current Umami v3 report and return its result

NameTypeReqDescription
filtersobject–Current Umami filter object; use {} for no filters
parametersobjectyesReport-specific parameters (varies by type)
typestringyesReport type to run
websiteIdstringyesWebsite UUID

No output schema declared.

No examples provided.

send_event ~222

Send a custom event or pageview to Umami (useful for server-side tracking)

NameTypeReqDescription
distinctIdstring–Stable user identifier
eventDataobject–Custom event data as key-value pairs
eventNamestring–Custom event name (omit for pageview)
hostnamestringyesHostname of the site (e.g. 'example.com')
ipstring–Client IP for trusted server-side collection
languagestring–Browser language (e.g. 'en-US')
referrerstring–Referrer URL
screenstring–Screen dimensions (e.g. 1920x1080)
tagstring–Event tag
timestampinteger–Unix timestamp in seconds
titlestring–Page title
urlstringyesURL path (e.g. '/checkout')
userAgentstring–Client user agent
websiteIdstringyesWebsite UUID (used as the 'website' field in payload)

No output schema declared.

No examples provided.

send_identify ~70

Attach custom session data or a distinct ID through Umami's public collection API

NameTypeReqDescription
dataobjectyesSession properties
distinctIdstring–Your stable user identifier
hostnamestring––
urlstring––
websiteIdstringyesWebsite UUID

No output schema declared.

No examples provided.

send_link_or_pixel_event ~67

Send a public collection event for a tracked link or pixel

NameTypeReqDescription
dataobject––
entityIdstringyes–
entityTypestringyes–
hostnamestring––
namestring––
urlstring––

No output schema declared.

No examples provided.

send_performance ~91

Send Core Web Vitals through Umami's public collection API

NameTypeReqDescription
clsnumber––
fcpnumber––
hostnamestringyesWebsite hostname
inpnumber––
lcpnumber––
ttfbnumber––
urlstringyesPage URL or path
websiteIdstringyesWebsite UUID

No output schema declared.

No examples provided.

set_global_two_factor_requirement ~33

Require or stop requiring 2FA globally (self-hosted admin only)

NameTypeReqDescription
requiredbooleanyes–

No output schema declared.

No examples provided.

set_replay_saved ~55

Save or unsave a session replay (name is used when saving)

NameTypeReqDescription
isSavedbooleanyes–
namestring––
replayIdstringyes–
websiteIdstringyes–

No output schema declared.

No examples provided.

set_team_two_factor_requirement ~45

Require or stop requiring 2FA for a team (self-hosted owner/manager only)

NameTypeReqDescription
requiredbooleanyes–
teamIdstringyes–

No output schema declared.

No examples provided.

set_user_two_factor_requirement ~43

Require or stop requiring 2FA for a user (self-hosted admin only)

NameTypeReqDescription
requiredbooleanyes–
userIdstringyes–

No output schema declared.

No examples provided.

transfer_website ~58

Transfer a website to a user or team using the current Umami transfer endpoint

NameTypeReqDescription
destinationIdstringyesTarget user or team UUID
destinationTypestringyes–
websiteIdstringyesWebsite UUID to transfer

No output schema declared.

No examples provided.

update_annotation ~75

Replace an annotation's date, note and all-day flag (Umami 3.4+)

NameTypeReqDescription
allDayboolean––
annotationIdstringyes–
date–yesISO date (YYYY-MM-DD) or timestamp with timezone
notestringyes–
websiteIdstringyes–

No output schema declared.

No examples provided.

update_board ~50

Update an Umami board

NameTypeReqDescription
boardIdstringyes–
descriptionstring––
namestring––
parametersobject––
typestring––

No output schema declared.

No examples provided.

update_link ~42

Update a tracked link

NameTypeReqDescription
linkIdstringyes–
namestring––
slugstring––
urlstring––

No output schema declared.

No examples provided.

update_my_password ~55

Update the current user's password (self-hosted Umami only; Cloud API keys cannot call this route)

NameTypeReqDescription
currentPasswordstringyesCurrent password
newPasswordstringyesNew password (minimum 8 characters)

No output schema declared.

No examples provided.

update_pixel ~35

Update a tracking pixel

NameTypeReqDescription
namestring––
pixelIdstringyes–
slugstring––

No output schema declared.

No examples provided.

update_report ~74

Update an existing saved report

NameTypeReqDescription
descriptionstring–Report description
namestringyesReport name
parametersobjectyesReport-specific parameters (JSON object)
reportIdstringyesReport UUID
typestringyesReport type
websiteIdstringyesWebsite UUID

No output schema declared.

No examples provided.

update_segment ~52

Update a saved segment or cohort

NameTypeReqDescription
namestringyes–
parametersobjectyes–
segmentIdstringyes–
typestringyes–
websiteIdstringyes–

No output schema declared.

No examples provided.

update_share ~42

Update a managed share

NameTypeReqDescription
namestringyes–
parametersobjectyes–
shareIdstringyes–
slugstringyes–

No output schema declared.

No examples provided.

update_team ~47

Update a team's name or access code

NameTypeReqDescription
accessCodestring–New access code
namestring–New team name
teamIdstringyesTeam UUID

No output schema declared.

No examples provided.

update_team_user ~46

Update a team member's role

NameTypeReqDescription
rolestringyesNew team role
teamIdstringyesTeam UUID
userIdstringyesUser UUID

No output schema declared.

No examples provided.

update_user ~58

Update a user's username, password, or role (admin only)

NameTypeReqDescription
passwordstring–New password
rolestring–New role
userIdstringyesUser UUID
usernamestring–New username

No output schema declared.

No examples provided.

update_website ~77

Update an existing website's configuration

NameTypeReqDescription
domainstring–New domain
namestring–New display name
replayConfigobject–Session replay and heatmap collection settings
shareIdstring|null–Share ID (set to null to remove)
websiteIdstringyesWebsite UUID

No output schema declared.

No examples provided.

verify_auth ~16

Verify the current authentication token is valid

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

Install

How do I install the io.github.mikusnuz/umami MCP server?

io.github.mikusnuz/umami runs locally as an npm package, launched with npx -y @mikusnuz/umami-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 · @mikusnuz/umami-mcp

# add to Claude Code
claude mcp add mikusnuz-umami -- npx -y @mikusnuz/umami-mcp
Common questions

What is the io.github.mikusnuz/umami MCP server?

io.github.mikusnuz/umami is an MCP server listed in the public MCP registry as io.github.mikusnuz/umami. MCP server for Umami Analytics v3, analytics, boards, links, pixels, reports, replay, and more. This page covers its npm package (@mikusnuz/umami-mcp).

Is the io.github.mikusnuz/umami MCP server safe to use?

io.github.mikusnuz/umami scores 76 out of 100 on VerifyMCP. We recorded 1 known advisory against it as of 21 November 2026. It declares no install or post-install scripts. 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.mikusnuz/umami MCP server expose?

io.github.mikusnuz/umami exposes 133 tools: list_websites, get_website, create_website, update_website, delete_website, and 128 more. Their descriptions and schemas cost roughly 7,691 tokens of context every time the server is loaded.

Is the io.github.mikusnuz/umami MCP server still maintained?

io.github.mikusnuz/umami is still listed as active in the MCP registry. We last reached this channel on 21 November 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.mikusnuz/umami MCP server under?

io.github.mikusnuz/umami declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.

What did VerifyMCP test on the io.github.mikusnuz/umami MCP server?

VerifyMCP ran 16 checks on io.github.mikusnuz/umami, covering Malware scan, Known CVEs, Install scripts, Dependency health and 12 more. Endpoint Security and Transport & Reachability do not apply to an npm package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.