ObsidianCorps Umami Analytics
Umami v3 MCP for Cloud or self-hosted analytics, with read-only, privacy-conscious defaults.
The current version, v0.1.2, was published to the official MCP registry on 2026-09-03. It is distributed as @obsidiancorps/umami-mcp on npm, filed under Analytics by this index, and declares 7 environment variables. Removals and unreachable sources are measured across every server this index tracks, contract drift across the servers that answer in consecutive snapshots; the index's current counts put this record in context.
Using ObsidianCorps Umami Analytics in Claude, Cursor, Gemini CLI, Cline, or Zed?
MCP tool contracts can change remotely with no version bump. The mcpindex gate pins each contract and HOLDs the call when it drifts-before your agent acts. Zero credentials. This is not the package install for this server itself (use Install this server for that).
Rewrites your MCP host config so each server launches behind the gate. Inspect first: curl -fsSL https://mcpindex.ai/install.sh | less
uv tool install mcpindex-gate && mcpindex-config-wireSemantic screen found no manipulation pattern in the description. Conformance probe not yet run.
mcpindex.integrity.descriptionpassINFOevidence“Tool provides read‑only analytics with privacy‑conscious defaults.”via static_description
- - Semantic screen only - the deterministic conformance probe has not run on this server
- - Confidence is reported but not yet calibrated (v1)
- - Screen reads the tool description, not the live behavior
- - advisory
- - registry description only no input schema
- - screen model 8b
Semantic screen: an LLM judge reads the tool description for hidden instructions (status PARTIAL). A pass means the description is not lying, not that the tool is safe: a high-capability tool with an honest description still warrants caution. The deterministic conformance probe has not been run on this server yet, so the screen here is semantic-only. Posture: advisory. Confidences are reported but not yet calibrated (calibrated=false at v1). Full verdict history is not shown on this page.
Own this server? Test a description on the public screen → It is a separate check from the verdict above, so the two can differ.
That verdict was true at screening time (snapshot 2026-11-20).
Contracts can change after screening, with no version bump. The gate pins ObsidianCorps Umami Analytics’s tool contracts on first sight and holds any silent change before your agent acts - the check that keeps being true on Tuesday.
See your first HOLD in 2 minutes →
Related: how to trust an MCP server · screen before install · silent contract drift
People vet a server before wiring it in. One line on your project site or docs answers that with an independent record: screening verdict, registry provenance, contract drift history. It stays current as new screens and drift events land.
[Independent trust record for ObsidianCorps Umami Analytics](https://mcpindex.ai/server/io-github-obsidiancorps-umami-mcp) - screening verdict, registry provenance, and contract drift monitoring.<a href="https://mcpindex.ai/server/io-github-obsidiancorps-umami-mcp">Independent trust record for ObsidianCorps Umami Analytics</a> - screening verdict, registry provenance, and contract drift monitoring.A live verdict badge for your README or listing. It reflects the current screen, links back here, and updates when the verdict does.
[](https://mcpindex.ai/server/io-github-obsidiancorps-umami-mcp)<a href="https://mcpindex.ai/server/io-github-obsidiancorps-umami-mcp"><img src="https://mcpindex.ai/api/v1/badge/io-github-obsidiancorps-umami-mcp" alt="mcpindex verdict" height="20" /></a>UMAMI_API_KEYUmami Cloud API key. Configure this or one self-hosted authentication mode.
UMAMI_BASE_URLBase URL of a self-hosted Umami instance, for example https://analytics.example.com.
UMAMI_TOKENPre-issued self-hosted Umami token. Use with UMAMI_BASE_URL instead of login credentials.
UMAMI_USERNAMESelf-hosted Umami username. Use with UMAMI_BASE_URL and UMAMI_PASSWORD.
UMAMI_PASSWORDSelf-hosted Umami password. Use with UMAMI_BASE_URL and UMAMI_USERNAME.
UMAMI_TWO_FACTOR_SECRETOptional Base32 TOTP setup secret for automatic Umami 3.3+ two-factor login.
UMAMI_DEFAULT_WEBSITE_IDOptional default website UUID used when a tool call does not select a website.
Social media for brands: editorial plans, on-brand images, scheduling, publishing and analytics.
Post your videos to your socials now or on a schedule, read analytics, and swap AI characters in.
Schedule and publish posts on 13 social networks, answer comments and DMs, and read analytics.