Skip to content
MCP server

Rug Pull Detector

Baseline an MCP server's tools and flag any definition that changes after you approve it

Runs locallyStatus and history
Install
Pricing
Open source
Platforms
CLI, macOS, Windows
Runs
Locally
Version
0.4.2
Listing updated
today

Similar MCP servers

About Rug Pull Detector

Rug Pull Detector is an open-source MCP server for security. It runs locally on your machine and is started by your AI client.

A rug pull is when an MCP server shows one tool definition at approval time and quietly serves another later. This detector is itself an MCP client: it connects to the target over stdio or Streamable HTTP, calls the real tools/list, and stores a SHA-256 hash and full snapshot of each tool, much like an SSH client remembering host keys.

The hash covers name, description, input schema, output schema and annotations such as readOnlyHint and destructiveHint, so flipping a safety hint counts as drift. On a later check, a changed existing tool is reported as critical, a new tool as medium and a removed one as low, with before-and-after description text. Each check_server run also applies a tool-poisoning catalogue scan to the live list, even on first sight, and auto-captures a baseline if none exists unless you pass --no-auto-baseline.

Baselines live as JSON under .guardbee/tool-baselines/, keyed by the label you give them, so renaming how you invoke a server starts a new baseline. The README is clear it detects drift in the presented tool list, not malicious behaviour that was always there, and that stdio targets are spawned, so only point it at servers you intend to run.

Install

Run in a terminal

claude mcp add rug-pull-detector -- npx -y @guardbee/mcp-rug-pull-detector

Add to claude_desktop_config.json

{
  "mcpServers": {
    "rug-pull-detector": {
      "command": "npx",
      "args": [
        "-y",
        "@guardbee/mcp-rug-pull-detector"
      ]
    }
  }
}
Install in CursorOpens Cursor, which asks you to confirm. Or add it by hand:

Add to ~/.cursor/mcp.json

{
  "mcpServers": {
    "rug-pull-detector": {
      "command": "npx",
      "args": [
        "-y",
        "@guardbee/mcp-rug-pull-detector"
      ]
    }
  }
}
Install in VS CodeOpens VS Code, which asks you to confirm. Or add it by hand:

Add to .vscode/mcp.json

{
  "servers": {
    "rug-pull-detector": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "@guardbee/mcp-rug-pull-detector"
      ]
    }
  }
}

Add to ~/.codeium/windsurf/mcp_config.json

{
  "mcpServers": {
    "rug-pull-detector": {
      "command": "npx",
      "args": [
        "-y",
        "@guardbee/mcp-rug-pull-detector"
      ]
    }
  }
}

Add to your client's MCP settings (most use this shape)

{
  "mcpServers": {
    "rug-pull-detector": {
      "command": "npx",
      "args": [
        "-y",
        "@guardbee/mcp-rug-pull-detector"
      ]
    }
  }
}

Using several servers? Build one config file with the MCP config generator.

Tools this server provides (3)

Taken from the project documentation; the running server may differ.

baseline_server
Connects to a server and stores its current tools as the trusted baseline.
check_server
Connects to a server and diffs its current tools against the stored baseline.
list_baselines
Lists every server with a stored baseline.

What it does

Trust-on-first-use baselines
Store a hash and snapshot of every tool the server presents.
Drift reporting
Flags changed, added and removed tools with graded severity.
Annotation-aware hashing
Changes to hints like destructiveHint are caught, not only wording.
Poisoning scan on live tools
Runs a tool-poisoning catalogue scan on every check.
Flexible targets
Point at a stdio command, a URL, or a named server in a config file.
SARIF output
Produces SARIF 2.1.0 for CI use.

Good for

  • Record a baseline right after reviewing a new MCP server
  • Re-check a third-party server before each work session
  • Run a scheduled job that fails when tool definitions drift
  • Review exactly which description text changed after a version bump
  • Gate a CI pipeline on critical drift findings

Pricing

Open source

MIT licensed

Rug Pull Detector FAQ

What does it detect?

Changes in the tool list a server presents, not malicious behaviour inside a tool that was always there.

Where are baselines stored?

In `.guardbee/tool-baselines/` by default, one JSON file per server; use --baseline-dir to change it.

Is it safe to point at any server?

Not blindly. Stdio targets are spawned as commands, so use it only on servers you intend to run.

What licence is it under?

MIT, according to the README.

Is Rug Pull Detector free?

Yes. Rug Pull Detector is open source, so you can use and self-host it for free.

How do I add Rug Pull Detector to Claude Code?

Run this command in your terminal: claude mcp add rug-pull-detector -- npx -y @guardbee/mcp-rug-pull-detector

What are the best alternatives to Rug Pull Detector?

The closest alternatives to Rug Pull Detector are REA, AiSOC, redamon, x64dbg-mcp-server and Agent Roast.

Where this comes from

  • Description: written from the project's README.
  • Install steps: from the official MCP Registry entry.

How AIPoweredBot checks servers