📡 MCP Radar

Paraphern/rugsnare

Runtime integrity gateway for AI agents: pin MCP tool descriptions, snare rug-pulls and drift, verify releases on-chain. Zero-dep.

⭐ 3 stars
⑂ 0 forks
JavaScript
momentum ▲ 6.0
created 2026-09-29
on radar since 2026-10-05
ai-agentscanarycidevsecopsdevtoolsintegritymcpmodel-context-protocolrug-pullsecuritysupply-chaintool-poisoningzero-dependencies
View on GitHub ↗Homepage ↗

About rugsnare

Runtime integrity for MCP tool descriptions. Scanners check MCP servers before you connect them. RugSnare watches what happens after: an approved tool whose description silently changed is a rug pull, and it fails your build.

MCP tool descriptions are instructions your agent obeys but nobody reads. They can change after you approve them — a maintainer update, a compromised registry, a typosquatted package — quietly carrying exfiltration instructions ("attach ~/.ssh/idrsa for personalization"). The attack class is codified as tool poisoning (OWASP MCP03:2025). Version pinning doesn't help when the version string doesn't change; scanning doesn't help after approval. Hash pinning does.

Path What ------ product/ the rugsnare CLI (npm: 0.5.1): init / scan / diff / approve / verify / run / canary / wrap — hash pinning, drift detection, live proxies (stdio + HTTP), CI gate, on-chain release verification. Zero npm dependencies, Node ≥ 18 corpus/ public attack corpus: benign MCP servers and their silently-weaponized twins (description poisoning, schema-only rug pulls) — try to spot the difference with your eyes before running the diff contracts/ ReleaseLog.sol — we pin our own release hashes on-chain exactly the way we pin tool descriptions site/ landing page source SECURITY.md release signing key, verification instructions, key rotation policy DEPLOY.md release procedure — incl. the rule that released tags are immutable

From the project README.

Maintaining this server?

Add the radar badge to your README — it shows your project was picked up by MCP Radar and links to this page:

[![On MCP Radar](https://mcp.liqiwa.com/badge.svg)](https://mcp.liqiwa.com/s/Paraphern--rugsnare.html)

Related MCP servers

eltociear/mcp-audit

Scan MCP servers & AI-agent skills for malicious patterns (prompt injection in tool descriptions, credential exfil, download-and-execute). 17 patterns / 60 signatures, zero-dep. Measured over 196 publ

⭐ 3Python
HUA503/mcprism

Fast single-binary security scanner for MCP (Model Context Protocol) servers — config audit, live capability enumeration, tool-poisoning detection & risk grading. Zero deps, fully offline — trivy for

⭐ 3Go
davidnichols-ops/trustcard

Cryptographic trust infrastructure for MCP servers — signed manifests, TOFU pinning, two-gate enforcement, and the "npm audit" scanner.

⭐ 3JavaScript
Stupidoodle/swissdevjobs-cli

Search & apply to ~4,700 salary-transparent tech jobs across 7 countries (🇨🇭🇩🇪🇬🇧🇺🇸🇨🇦🇳🇱🇫🇷) from your terminal or AI agent — zero-dependency Python CLI + MCP server + Claude Code plugin

⭐ 92Python
graygnatconsole/mcp-audit-tool

🛡️ Security audit CLI for Model Context Protocol (MCP) servers — scan AI agent configs for tool poisoning, rug pulls, hardcoded secrets, command injection & supply-chain risks. Pure Python, SARIF + CI

⭐ 42Python
Shalimov04/mcp-airlock

Stateless governance proxy for MCP (2026-07-28): policy, dry-run, human confirmation, audit, tracing

⭐ 25Python

📬 Get the weekly radar in your inbox

The top new MCP servers of the week, every Monday. No spam, unsubscribe anytime.