Microsoft Clarity is an open-source TypeScript library that records website interactions and layout changes so they can be analyzed as behavioral data and replayed as sessions. Website developers use its instrumentation, decoding, visualization, and browser-devtools components to understand how users navigate and interact with sites while emphasizing privacy and performance. The catalogue entries provide agent instructions and an MCP integration for working with Clarity.
Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
git clone --depth 1 https://github.com/microsoft/clarityInstalling this writes the configuration, not the program: `python3` runs a file from the repository, so clone it first and make the path in the command match where you put it.
Wrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/mcp/microsoft/clarity/git-clarity)<a href="https://agentmods.dev/mcp/microsoft/clarity/git-clarity"><img src="https://agentmods.dev/badge/mcp/microsoft/clarity/git-clarity/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/mcp/microsoft/clarity/git-clarity"><img src="https://agentmods.dev/badge/mcp/microsoft/clarity/git-clarity.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
git-clarity scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 1mo ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
What it actually says
{
"git-clarity": {
"command": "python3",
"args": [
"-m",
"mcp_server_git",
"--repository",
"."
]
}
}What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 1mo ago First seen · 11 lines scan A 83deb6233f97
git-clarity is an MCP server published in the GitHub repository microsoft/clarity (2,751 stars, last pushed yesterday), licensed MIT. Its token cost is not measured: an MCP server costs its tool schemas, not its config file. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other mcp servers, from other repositories
matrixscroll
MCP server for signed machine-action records, offline tool-surface checks, with device-agnostic custody and CNSA 2.0 Category 5 crypto (ML-DSA-87, ML-KEM-1024). Runs locally from the matrixscroll Python package.
gitee-mcp
MCP server "gitee-mcp" as configured in sandraschi/gitee-mcp. Runs locally from the gitee-mcp Python package.
gitpin
Prove and verify multi-repo claims at Git HEAD: path, line, full SHA, no index. Runs locally from the gitpin npm package. Needs 1 environment variable to run.
gitlab-mcp
A local MCP server for operating GitLab from the Cursor code editor. GitLab is a service for hosting code and managing software projects.
docs-langchain
MCP server "docs-langchain", hosted remotely at docs.langchain.com, as configured in langchain-ai/langchain.
component-explorer
MCP server "component-explorer" as configured in microsoft/vscode. Launched with npm exec --no -- component-explorer mcp -p ./test/componentFixtures/component-ex.