RugSnare
Pin MCP tool descriptions by hash and fail CI when an approved tool silently changes
- Pricing
- Open source
- Platforms
- CLI, Linux, macOS
- Runs
- Locally
- Version
- 1.6.0
- Listing updated
- today
Similar MCP servers
About RugSnare
RugSnare is an open-source MCP server for security. It runs locally on your machine and is started by your AI client.
RugSnare is a command-line tool rather than a server your assistant calls. It reads your MCP client configs, records each tool's name, description and input schema as a canonical SHA-256 hash, and later re-checks the live servers. If anything has changed since you approved it, the diff command exits with an error, so a build can fail on a quiet edit to a tool description.
The README frames this as the gap between pre-install scanners and what happens afterwards, and reports an audit it ran in October 2026 that found 218 silent contract changes across popular npm MCP servers. Findings are graded as breaking, loosened, expanded or notation-only, so formatting churn is separated from a real parameter change.
Beyond the one-line GitHub Action it offers a live proxy for stdio servers with observe and enforce modes, signed pin files and a verification step against an on-chain release log. It has no npm dependencies and needs Node 18 or newer.
Install
Run in a terminal
claude mcp add rugsnare -- npx -y rugsnareAdd to claude_desktop_config.json
{
"mcpServers": {
"rugsnare": {
"command": "npx",
"args": [
"-y",
"rugsnare"
]
}
}
}Add to ~/.cursor/mcp.json
{
"mcpServers": {
"rugsnare": {
"command": "npx",
"args": [
"-y",
"rugsnare"
]
}
}
}Add to .vscode/mcp.json
{
"servers": {
"rugsnare": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"rugsnare"
]
}
}
}Add to ~/.codeium/windsurf/mcp_config.json
{
"mcpServers": {
"rugsnare": {
"command": "npx",
"args": [
"-y",
"rugsnare"
]
}
}
}Add to your client's MCP settings (most use this shape)
{
"mcpServers": {
"rugsnare": {
"command": "npx",
"args": [
"-y",
"rugsnare"
]
}
}
}Using several servers? Build one config file with the MCP config generator.
What it does
- Hash pinning
- Canonicalises and hashes each tool's name, description and schema, ignoring cosmetic reordering.
- Drift grading
- Labels changes as breaking, loosened, expanded or notation-only.
- CI gate
- A GitHub Action fails the build when a pinned contract changes.
- Live proxy
- Wraps a stdio server in observe or enforce mode to quarantine drifted tools.
- Signed pins
- Signs pins.json with Ed25519 and shows a badge reflecting the signature state.
- Zero dependencies
- Runs on Node 18 or newer without npm packages.
Good for
- Catch a tool description that changes after you approved it
- Add an MCP drift check to a pull request pipeline
- Review a field-level diff when a server updates
- Quarantine a changed tool during a live session
Pricing
Open source
RugSnare FAQ
How do I start?
Run npx rugsnare init, then scan to pin the current contracts and diff to check them.
What does it hash?
Each tool's name, description and input schema, plus prompts and resources.
What is the licence?
The README badge points to Apache-2.0.
What does it need?
Node 18 or newer; there are no npm dependencies.
Is RugSnare free?
Yes. RugSnare is open source, so you can use and self-host it for free.
How do I add RugSnare to Claude Code?
Run this command in your terminal: claude mcp add rugsnare -- npx -y rugsnare
What are the best alternatives to RugSnare?
The closest alternatives to RugSnare are REA, Context7, Chrome DevTools MCP, Codebase Memory and GitHub.
Where this comes from
- Description: written from the project's README.
- Install steps: from the official MCP Registry entry.


