Is the gh:chopratejas/headroom MCP server safe to use?
Independent trust grade F (55/100). Static analysis of github.com/chopratejas/headroom. Stdio/source-distributed — no remote endpoint; runtime behavior not measured. wmcp.sh continuously watches gh:chopratejas/headroom for tool drift and rug-pulls. The grade is free and identical whether or not the operator pays.
Spec / packaging20%35
no clear MCP signals found
no tools detected in sampled source
Security (OWASP MCP)30%50
source not retrievable — graded on repo metadata only
Maintenance / popularity20%80
153 releases — actively versioned
153 published releases
Tool hygiene15%55
Transparency / provenance15%55
✓ public GitHub repo
license/stars unavailable (GitHub API rate-limited) — graded on source + releases
Findings
INFO Static analysis of github.com/chopratejas/headroom. Stdio/source-distributed — no remote endpoint; runtime behavior not measured.
We re-grade gh:chopratejas/headroom on a schedule and alert your Slack/webhook the moment its tools change or its grade drops — rug-pull insurance for the connection.
Share this report card
A 1200×630 card with the grade + audit — drop it in a post, Slack, or your repo.
A live badge — it re-verifies itself and shows current stability. Static scorecards can't. Paste it in your README or site to show users you're independently audited.
<a href="https://wmcp.sh/mcp/grade/gh%3Achopratejas%2Fheadroom"><img src="https://wmcp.sh/mcp/grade/gh%3Achopratejas%2Fheadroom/badge.svg" alt="MCP Trust Grade F · wmcp.sh"></a>
Agents: check this before connecting
Add the wmcp.sh trust oracle as an MCP server and call grade_mcp_server / check_mcp_drift in your agent's pre-connection gate:
https://wmcp.sh/mcp/trust
How this grade is computed. An open, independent rubric — Spec conformance (20%), Security mapped to the OWASP MCP Top 10 (30%), Reliability (20%), Tool hygiene (15%), Transparency (15%) — run by connecting to the server and inspecting its real MCP surface. The grade is free and identical whether or not the operator pays. v1 uses static + spec signals from a single connection; continuous uptime, real latency, and annotation-truthing (declared readOnly vs observed behavior) layer on via the wmcp.sh proxy.