io.github.mikusnuz/umami

NPM · @MIKUSNUZ/UMAMI-MCP · SCANNED AUG 3

MCP server for Umami Analytics API v2 — websites, stats, events, reports, and realtime

Available components

+17 this week 70 70 Trust /100

Trust breakdown (6 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 →

Supply Chain Security87

No malware found by supply-chain analysis.Pass
Only part of the dependency tree could be resolved (95 of 99), so this covers what we could see, not the whole tree.Partial
No install/post-install scripts declared.Pass
Only part of the dependency tree could be resolved (95 of 99), 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 136 days ago).Pass
Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail

Schema Quality & AI Usability82

100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
AI-judged instruction clarity (good).Pass
Tool/resource definitions use about 3599 tokens (~52/item across 68 items; 66 tools + 2 resources), lean.Pass
Usage-examples check failed: none of the tools include examples. See how to fix → Fail

Stability & Change Management23

Stability observed for 7 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

Install

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 · @mikusnuz/umami-mcp

Claude Codex opencode OpenClaw Hermes Other

# add to Claude Code

claude mcp add mikusnuz-umami -- npx -y @mikusnuz/umami-mcp

# add to Codex CLI

codex mcp add mikusnuz-umami -- npx -y @mikusnuz/umami-mcp

// opencode.json

{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "mikusnuz-umami": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "@mikusnuz/umami-mcp"
      ],
      "enabled": true
    }
  }
}

# add to OpenClaw

openclaw mcp add mikusnuz-umami --command npx --arg -y --arg @mikusnuz/umami-mcp

# ~/.hermes/config.yaml

mcp_servers:
  mikusnuz-umami:
    command: "npx"
    args: ["-y", "@mikusnuz/umami-mcp"]

// mcp.json

{
  "mcpServers": {
    "mikusnuz-umami": {
      "command": "npx",
      "args": [
        "-y",
        "@mikusnuz/umami-mcp"
      ]
    }
  }
}

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.

3 Aug 26 +3
- Stability: unverified → 0.23 ▲ functional
2 Aug 26 +41
- Provenance: unverified → fail ▼ security
- Install scripts: unverified → pass ▲ security
- Known CVEs: unverified → partial ▲ security
- Malware scan: unverified → pass ▲ security
- Stability: Stability not yet verified: not enough scan history yet (needs a 30-day window). security
- Security disclosure: fail → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- Schema quality: 100 → unverified ▼ functional
- Schema quality: unverified → good ▲ functional
- MCP protocol: unverified → pass ▲ functional
- Maintenance: unverified → pass ▲ functional
- Dependency health: unverified → partial ▲ functional
- License: unverified → pass ▲ functional
- Licence: MIT functional
31 Jul 26 −27
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
30 Jul 26 +27
- Dependency health: partial → unverified ▼ functional
- Schema quality: unverified → 100 ▲ functional
- Tool coverage: unverified → 100 ▲ functional
28 Jul 26 −27
- Tool coverage: 100 → unverified ▼ functional
- Schema quality: 100 → unverified ▼ functional
- Dependency health: unverified → partial ▲ functional
27 Jul 26 53

First indexed and scored.

Show 4 earlier entries Hide earlier entries

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 3 Aug 2026 · Analysed npm/@mikusnuz/[email protected]

Provenance none

Ecosystem: npm · Outcome: none

Dependencies 95 packages

95 packages in the resolved dependency tree · 95 deprecated · 29 stale.

The dependency tree was only partially resolved, so these counts may be incomplete.

MCP tools — 66 exposed · ~3,575 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.

Tool Tokens

list_teams ~74

List all teams

Input Output Examples

Name	Type	Req	Description
orderBy	string	—	Field to order by (e.g. 'name', 'createdAt')
page	number	—	Page number (1-based)
pageSize	number	—	Results per page (default 10)
query	string	—	Search query to filter teams

No output schema declared.

No examples provided.

list_users ~76

List all users (admin only)

Input Output Examples

Name	Type	Req	Description
orderBy	string	—	Field to order by (e.g. 'username', 'createdAt')
page	number	—	Page number (1-based)
pageSize	number	—	Results per page (default 10)
query	string	—	Search query to filter users

No output schema declared.

No examples provided.

list_websites ~77

List all websites tracked in Umami

Input Output Examples

Name	Type	Req	Description
orderBy	string	—	Field to order by (e.g. 'name', 'domain')
page	number	—	Page number (1-based)
pageSize	number	—	Results per page (default 10)
query	string	—	Search query to filter websites

No output schema declared.

No examples provided.

remove_team_user ~38

Remove a user from a team

Input Output Examples

Name	Type	Req	Description
teamId	string	yes	Team UUID
userId	string	yes	User UUID to remove

No output schema declared.

No examples provided.

remove_team_website ~42

Remove a website from a team

Input Output Examples

Name	Type	Req	Description
teamId	string	yes	Team UUID
websiteId	string	yes	Website UUID to remove from the team

No output schema declared.

No examples provided.

reset_website ~34

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

Input Output Examples

Name	Type	Req	Description
websiteId	string	yes	Website UUID to reset

No output schema declared.

No examples provided.

run_report ~71

Execute a report by type and get results (funnel, retention, utm, goals, insights, revenue, journey, attribution)

Input Output Examples

Name	Type	Req	Description
parameters	object	yes	Report-specific parameters (varies by type)
type	string	yes	Report type to run
websiteId	string	yes	Website UUID

No output schema declared.

No examples provided.

send_event ~147

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

Input Output Examples

Name	Type	Req	Description
eventData	object	—	Custom event data as key-value pairs
eventName	string	—	Custom event name (omit for pageview)
hostname	string	yes	Hostname of the site (e.g. 'example.com')
language	string	—	Browser language (e.g. 'en-US')
referrer	string	—	Referrer URL
title	string	—	Page title
url	string	yes	URL path (e.g. '/checkout')
websiteId	string	yes	Website UUID (used as the 'website' field in payload)

No output schema declared.

No examples provided.

transfer_website ~43

Transfer website ownership to another user

Input Output Examples

Name	Type	Req	Description
userId	string	yes	Target user UUID to transfer ownership to
websiteId	string	yes	Website UUID to transfer

No output schema declared.

No examples provided.

update_my_password ~35

Update the current user's password

Input Output Examples

Name	Type	Req	Description
currentPassword	string	yes	Current password
newPassword	string	yes	New password

No output schema declared.

No examples provided.

update_report ~74

Update an existing saved report

Input Output Examples

Name	Type	Req	Description
description	string	—	Report description
name	string	—	Report name
parameters	object	—	Report-specific parameters (JSON object)
reportId	string	yes	Report UUID
type	string	—	Report type
websiteId	string	—	Website UUID

No output schema declared.

No examples provided.

update_team ~33

Update a team's name

Input Output Examples

Name	Type	Req	Description
name	string	yes	New team name
teamId	string	yes	Team UUID

No output schema declared.

No examples provided.

update_team_user ~54

Update a team member's role

Input Output Examples

Name	Type	Req	Description
role	string	yes	New role: 'team-owner' or 'team-member'
teamId	string	yes	Team UUID
userId	string	yes	User UUID

No output schema declared.

No examples provided.

update_user ~65

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

Input Output Examples

Name	Type	Req	Description
password	string	—	New password
role	string	—	New role: 'admin' or 'user'
userId	string	yes	User UUID
username	string	—	New username

No output schema declared.

No examples provided.

update_website ~61

Update an existing website's configuration

Input Output Examples

Name	Type	Req	Description
domain	string	—	New domain
name	string	—	New display name
shareId	string	—	Share ID (set to null to remove)
websiteId	string	yes	Website UUID

No output schema declared.

No examples provided.

verify_auth ~16

Verify the current authentication token is valid

Input Output Examples

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

On this page

Handy links

Scoring key

80+ high trust
60–79 medium
below 60 low

How we score

Score history · last 30 days

27 Jul 3 Aug