Skills/PyPI/microsoft-clarity-mcp

microsoft-clarity-mcp@0.1.5

CAUTION· static only

Publisher claims: "FastMCP server for Microsoft Clarity: behavioral UX diagnostics, rage clicks, dead clicks, quick backs, excessive scroll, and JavaScript errors." Observed in sandbox: static analysis only — behavior not yet observed.

Registry PyPI (MCP server)Publisher surendranb · publishing for 539 daysInstalls 0Last detonated 3d ago
What would fix thisWatchDispute verdict

Coverage

Static only; nothing was run yet.

The label rests on the code, the instruction files and the publisher. The honeypot run replaces this verdict when it completes.

Before you give it your token

It will ask for
CLARITY_API_TOKENCLARITY_TOKENConfiguration, not credentials: ANTIGRAVITY_SESSION, CLARITY_CACHE_DIR, CLARITY_CACHE_PATH, CLARITY_CACHE_TTL, CLARITY_INTERNAL, CLARITY_TELEMETRY, CLAUDE_CODE, CLAUDE_PROJECT_DIR, CONDA_PREFIX, CURSOR_SESSION, CURSOR_TRACE, GEMINI_CLI, VIRTUAL_ENV, VSCODE_PID
Where it talks to
no vendor host named in the codeAlso microsoft.com, clarity.ms, githubusercontent.com, builditwithai.xyz, workers.dev — not the publisher's domain; check what for before connecting.
What the honeypot saw
nothing has run yet
What we could not test
everything: the server has not run yet

Run it before you trust it. Nothing has run yet: the code was read, the server was not. `vet-skills try` runs this exact version in the honeypot in about a minute.

Never paste a credential into a chat, a ticket or a report, including ours. How the guard holds it.

Is [email protected] safe to install?

KillerSkills analysed it statically (a sandbox run is pending) on 2026-11-11 and scored it 68/100 (Caution). It is not known to be malicious, but it has behaviour or code a security policy should decide on before install. Notable findings: Credential pass-through configuration; Credential pass-through configuration. Summary: static analysis only — behavior not yet observed.

Behavior trace

Queued for honeypot run · static analysis only
t+CategoryObserved action

This version has not been detonated yet. The score above counts behavior as unknown (50/100), so it cannot read Verified until the honeypot run completes and replaces this verdict.

Static findings

HIGH
Credential pass-through configurationsrc/microsoft_clarity_mcp/server.py:567 · Credential pass-through configuration — agent relays sensitive credentials"4. Set environment variable CLARITY_API_TOKEN=<token> or pass token parameter directly.\n"Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.
AST02
HIGH
Credential pass-through configurationsrc/microsoft_clarity_mcp/client.py:72 · Credential pass-through configuration — agent relays sensitive credentials"4. Set environment variable CLARITY_API_TOKEN=<token> or pass token parameter directly.\n"Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.
AST02

Cost to the agent

Instructions loaded
≈77 tok
1 file · 23 in bundle

Tokens estimated at four characters each. Skills load their instruction text when triggered; the figure is what that costs.

Known vulnerabilities

No advisories in OSV for microsoft-clarity-mcp@0.1.5 as of 3d ago. This is the package itself, not its dependencies.

What would make this Verified

12 points to 80 · weights: behavior 45%, static 25%, prompt 15%, publisher 15%
  1. Unclaimed publisher≈ +8 on the totalClaim surendranb: a verified publisher gets +50 on publisher trust. It is free and usually instant with GitHub sign-in.
  2. Credential pass-through configuration≈ +4 on the totalStop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.
Publish a new version to PyPI, then queue it here. Not your skill? Claim the handle to get verdict changes by email.Claim surendranbPropose a patch to the maintainer