io.github.mikusnuz/umami
NPM · @MIKUSNUZ/UMAMI-MCP · SCANNED SEP 22
MCP server for Umami Analytics API v2 — websites, stats, events, reports, and realtime
Available components
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 Security98
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- 31 of 96 dependencies flagged as unhealthy. 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 186 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability84
- 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 Management97
- Stability observed for 29 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
Tool Safety75
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- 0 of 10 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 67 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
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
claude mcp add mikusnuz-umami -- npx -y @mikusnuz/umami-mcp
{
"mcpServers": {
"mikusnuz-umami": {
"command": "npx",
"args": [
"-y",
"@mikusnuz/umami-mcp"
]
}
}
} {
"servers": {
"mikusnuz-umami": {
"command": "npx",
"args": [
"-y",
"@mikusnuz/umami-mcp"
]
}
}
} codex mcp add mikusnuz-umami -- npx -y @mikusnuz/umami-mcp
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"mikusnuz-umami": {
"type": "local",
"command": [
"npx",
"-y",
"@mikusnuz/umami-mcp"
],
"enabled": true
}
}
} openclaw mcp add mikusnuz-umami --command npx --arg -y --arg @mikusnuz/umami-mcp
mcp_servers:
mikusnuz-umami:
command: "npx"
args: ["-y", "@mikusnuz/umami-mcp"] {
"McpServers": {
"mikusnuz-umami": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"@mikusnuz/umami-mcp"
]
}
}
} assistant mcp add mikusnuz-umami -t stdio -c npx -a -y @mikusnuz/umami-mcp
{
"mcpServers": {
"mikusnuz-umami": {
"command": "npx",
"args": [
"-y",
"@mikusnuz/umami-mcp"
]
}
}
} 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.
- 22 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 20 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.
- 18 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.
- 17 Sept 26 −3
- Stability: pass → 0.80 functional
- 16 Sept 26 0
- Stability: 0.97 → pass security
- 15 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 13 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.
- 11 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.
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 22 Sept 2026 · Analysed npm/@mikusnuz/umami-mcp@1.2.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 →
Dependencies 96 packages
| Packages resolved | 96 |
|---|---|
| Stale | 31 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
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 →
list_teams ~74
List all teams
| 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)
| 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
| 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
| 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
| 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)
| 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)
| 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)
| 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
| 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
| 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
| 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
| 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
| 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)
| 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
| 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 schema present but exposes no named parameters.
No output schema declared.
No examples provided.
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 API v2, websites, stats, events, reports, and realtime. 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 84 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 22 September 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 66 tools: list_websites, get_website, create_website, update_website, delete_website, and 61 more. Their descriptions and schemas cost roughly 3,575 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 22 September 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.