clarity-mcp-server@3.0.0
CAUTION· static onlyPublisher claims: "The official MCP server for Microsoft Clarity" Observed in sandbox: static analysis only — behavior not yet observed.
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
KEYRING_ACCESS_TOKEN_ACCOUNTOAUTH_CALLBACK_PATHConfiguration, not credentials: BOT_ACTIVITY_PATHS_TOOL- Where it talks to
- microsoft.com (its own)
- 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.
What changed since 2.0.1
vet-skills diff clarity-mcp-server 2.0.1 3.0.0This version reaches for something 2.0.1 did not: 2 new credential variables (KEYRING_ACCESS_TOKEN_ACCOUNT, OAUTH_CALLBACK_PATH). Compared from the two recorded runs, not from source.
- New credential variables
- KEYRING_ACCESS_TOKEN_ACCOUNT, OAUTH_CALLBACK_PATH
3.0.0 was not run in the sandbox (static only); the comparison covers what static analysis recorded only. Only one of the two runs produced a tool list; tools are not compared.
The guard can hold an update like this until someone approves it (runtime.on_change: hold). A change that only shows with a real credential, or on a path the run did not reach, is not in a trace and so not in this comparison.
Is [email protected] safe to install?
KillerSkills analysed it statically (a sandbox run is pending) on 2026-11-17 and scored it 71/100 (Caution). It is not known to be malicious, but it has behaviour or code a security policy should decide on before install. Summary: static analysis only — behavior not yet observed.
Behavior trace
Queued for honeypot run · static analysis onlyThis 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
// This is the CLI entry point for the npx executableFix: Pin versions and sources; vendor anything fetched at install time.No other findings across 3,175 lines in 47 files.
Cost to the agent
Tokens estimated at four characters each. Skills load their instruction text when triggered; the figure is what that costs.
Known vulnerabilities
Not checked against OSV yet; the weekly check has not reached this version.
What would make this Verified
9 points to 80 · weights: behavior 45%, static 25%, prompt 15%, publisher 15%- Unclaimed publisher≈ +8 on the totalClaim microsoft: a verified publisher gets +50 on publisher trust. It is free and usually instant with GitHub sign-in.
- npx invocation of non-well-known package≈ +2 on the totalPin versions and sources; vendor anything fetched at install time.