RugSnare runs on your own machine — the client starts it, so there is no endpoint to ping. 271 installs a week from npm. Last commit 8 Nov 2026.
Pin MCP tool contracts by sha-256; catch silent drift, rug pulls and bait-and-switch in CI.
We read the source, 5 h ago · rules 995398eba69f
What this server is able to do. For an MCP server this is often the job itself — a terminal server runs commands because that is what it is for. Listed so you know what you are plugging in, not as an accusation.
const child = spawn(command, args, {
const pkgDir = path.join(dir, server.name);
{ id: 'R03', weight: 3, test: /\.(ssh\/id_rsa|\.env|aws_secret|api_key|credentials?\.(json|yml|txt))/i, desc: 'response references credentials or private keys' },
Found in continuous integration, deployment or infrastructure files, or in a neighbouring package of the same monorepo. None of this is installed when you add the server: it describes how the project is built and released. We list it because a leaked key in a build pipeline is still a real problem, but it is not something this server does on your machine.
d.text((x, 155), "and rm -rf", font=f_big, fill=RED)
{"A02", 3, regexp.MustCompile(`(?i)\.(ssh|id_rsa|id_ed25519|aws_secret|api_key|\.env|credentials?)`)},
document.getElementById('scanArchive').innerHTML = card('#fef2f2,#dc2626', 'Archive unavailable: ' + esc(a.error));
Is this your server and something here is wrong? Tell us — corrections are free and do not require a plan.
We found places where it runs commands, builds paths or queries from values it is given. None of that is a flaw by itself — it becomes one when the code changes, and code changes quietly between releases. We re-read it on every one.
This server runs on your own machine — install it with the package manager and the client starts it for you. Package name taken from the official registry entry.
claude mcp add rugsnare -- npx -y rugsnare
{
"mcpServers": {
"rugsnare": {
"command": "npx",
"args": [
"-y",
"rugsnare"
]
}
}
}
[mcp_servers.rugsnare]
command = "npx"
args = ["-y", "rugsnare"]
{
"mcpServers": {
"rugsnare": {
"command": "npx",
"args": [
"-y",
"rugsnare"
]
}
}
}
{
"servers": {
"rugsnare": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"rugsnare"
]
}
}
}
MCP server for compare-cli: contract version diff/redline and a drift gate as agent tools.
package-lock.json for MCP trust: catch MCP rug-pulls, tool poisoning, and leaked secrets.
MCP server to scan smart contracts on Base for honeypots, rug pulls, and vulnerabilities.
A2A & MCP Pre-Flight Security: SHA-256 tool schema rug-pull detection and liveness grades.
Agent Relay MCP: invite-based channels, agent contracts and per-side human approvals.
Transparent audit proxy for MCP servers: logs every tool call, flags poisoning and rug pulls.
Catch TypeScript API and OpenAPI contract drift in AI-generated code, then revalidate it in CI.
Agent control plane for DCC and engine hosts: one MCP endpoint, one tool contract.
Answers built from our own checks of this server.