# io.github.GuardBee/rug-pull-detector (npm · @guardbee/mcp-rug-pull-detector)

Baselines an MCP server's tools and detects tool-definition changes after approval

- Trust score: 86/100 (high trust)
- Change this week: +6
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-10-25

## Components

- npm · `@guardbee/mcp-rug-pull-detector`: 86/100 (this document), [markdown](https://verifymcp.io/servers/guardbee-rug-pull-detector/guardbee-mcp-rug-pull-detector.md), [page](https://verifymcp.io/servers/guardbee-rug-pull-detector/guardbee-mcp-rug-pull-detector)

## Channel facts

- Registry: `npm`
- Package: `@guardbee/mcp-rug-pull-detector`
- Version: `0.3.3`
- Transport: `stdio`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-10-25.

- **Supply Chain Security**: 98/100
  - No malware found by supply-chain analysis.
  - No known CVEs affecting this package version or its production dependencies.
  - No install/post-install scripts declared.
  - 30 of 95 dependencies flagged as unhealthy.
- **Provenance & Transparency**: 100/100
  - Source repository is publicly reachable at the declared URL.
  - Cryptographically verified build provenance (signed, bound to GuardBee/guardbee-mcp).
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 2 days ago).
  - Publishes a security disclosure policy (SECURITY.md).
- **Schema Quality & AI Usability**: 74/100
  - AI-judged instruction clarity (good).
  - Tool/resource definitions use about 393 tokens (~131/item across 3 items; 3 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 37/100
  - Stability observed for 11 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 3 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### How do I install the io.github.GuardBee/rug-pull-detector MCP server?

io.github.GuardBee/rug-pull-detector runs locally as an npm package, launched with npx -y @guardbee/mcp-rug-pull-detector. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

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

### Cursor

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

### VS Code

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

### Codex

```bash
codex mcp add guardbee-rug-pull-detector -- npx -y @guardbee/mcp-rug-pull-detector
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "guardbee-rug-pull-detector": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "@guardbee/mcp-rug-pull-detector"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add guardbee-rug-pull-detector --command npx --arg -y --arg @guardbee/mcp-rug-pull-detector
```

### Hermes

```yaml
mcp_servers:
  guardbee-rug-pull-detector:
    command: "npx"
    args: ["-y", "@guardbee/mcp-rug-pull-detector"]
```

### Netclaw

```json
{
  "McpServers": {
    "guardbee-rug-pull-detector": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "@guardbee/mcp-rug-pull-detector"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add guardbee-rug-pull-detector -t stdio -c npx -a -y @guardbee/mcp-rug-pull-detector
```

### Other

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

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-10-25 (score 86, +1)

No change was recorded against any check on this day. Stability & Change Management went from 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-23 (score 85, +36)

- [security improvement] Injection markers: unverified → pass
- [functional improvement] Tool coverage: unverified → 100
- [functional improvement] MCP protocol: unverified → pass
- [functional improvement] Stability: unverified → 0.30

### 2026-10-22 (score 49, −31)

- [security regression] Known CVEs: pass → unverified
- [security regression] Tool safety: pass → unverified
- [security regression] Known CVEs: pass → partial
- [security] Stability: Stability not yet verified: we do not have a sandbox capture of the MCP schema this version of the package serves yet.
- [functional regression] Dependency health: 0.86 → unverified
- [functional regression] Capabilities: pass → unverified
- [functional regression] Tool coverage: 100 → unverified
- [functional improvement] Stability: unverified → 0.27
- [functional improvement] Security disclosure: fail → pass
- [functional] Dependency health: 0.86 → partial
- [functional] Package version: 0.2.2 → 0.3.3
- [functional] Package version: 0.2.2 → 0.3.2
- [functional] Package version: 0.2.2 → 0.3.1
- [functional] Package version: 0.2.2 → 0.3.0

### 2026-10-14 (score 80, +31)

- [security improvement] Injection markers: unverified → pass
- [security] First check of Judged manipulation: pass
- [security] Stability: Stability not yet verified: not enough scan history yet (needs a 30-day window).
- [functional improvement] Tool coverage: unverified → 100
- [functional improvement] MCP protocol: unverified → pass
- [functional] First check of Schema quality: fail
- [functional] First check of Destructive annotations: pass
- [functional] First check of Schema quality: pass
- [functional] First check of Schema quality: good
- [functional] First check of Tool coverage: 100

### 2026-10-13 (score 49)

First indexed and scored.

## MCP tools (3)

### `baseline_server` (~167 tokens)

Connect to an MCP server (stdio command or Streamable HTTP URL), read its current tools/list response, and store it as the trusted baseline for future drift checks. Call this once, right after you've reviewed and approved a server's tools.

Input parameters:

- `args` (array): Arguments for the stdio command
- `command` (string): Command to spawn for a stdio MCP server (e.g. "npx")
- `cwd` (string): Working directory for the spawned process
- `env` (object): Extra environment variables for the spawned process
- `label` (string): Stable identifier for this server, used to look up its baseline. Defaults to the command line or URL.
- `url` (string): URL of a Streamable HTTP MCP server (alternative to command/args)

### `check_server` (~206 tokens)

Connect to an MCP server and compare its current tools/list response against the stored baseline. A tool whose description, schema, or annotations changed since baseline is a 'rug pull' — approved once, silently different now. If no baseline exists yet, one is captured automatically (set autoBaseline=false to require an explicit baseline_server call first).

Input parameters:

- `args` (array): Arguments for the stdio command
- `autoBaseline` (boolean): Automatically capture a baseline if none exists yet (default: true)
- `command` (string): Command to spawn for a stdio MCP server (e.g. "npx")
- `cwd` (string): Working directory for the spawned process
- `env` (object): Extra environment variables for the spawned process
- `label` (string): Stable identifier for this server, used to look up its baseline. Defaults to the command line or URL.
- `url` (string): URL of a Streamable HTTP MCP server (alternative to command/args)

### `list_baselines` (~20 tokens)

List every server this scanner has a stored baseline for

## Diagnostics

Captured diagnostic sections: Provenance, Dependencies. The full working is on the page: https://verifymcp.io/servers/guardbee-rug-pull-detector/guardbee-mcp-rug-pull-detector#diagnostics

## Score history

- 2026-10-25: 86
- 2026-10-24: 85
- 2026-10-23: 85
- 2026-10-22: 49
- 2026-10-21: 80
- 2026-10-20: 80
- 2026-10-19: 80
- 2026-10-18: 80
- 2026-10-17: 80
- 2026-10-16: 80
- 2026-10-15: 80
- 2026-10-14: 80
- 2026-10-13: 49

## Common questions

### What is the io.github.GuardBee/rug-pull-detector MCP server?

io.github.GuardBee/rug-pull-detector is an MCP server listed in the public MCP registry as io.github.GuardBee/rug-pull-detector. Baselines an MCP server's tools and detects tool-definition changes after approval. This page covers its npm package (@guardbee/mcp-rug-pull-detector).

### Is the io.github.GuardBee/rug-pull-detector MCP server safe to use?

io.github.GuardBee/rug-pull-detector scores 86 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 25 October 2026. It declares no install or post-install scripts. Its build provenance is signed and verified. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

### What tools does the io.github.GuardBee/rug-pull-detector MCP server expose?

io.github.GuardBee/rug-pull-detector exposes 3 tools: baseline_server, check_server, list_baselines. Their descriptions and schemas cost roughly 393 tokens of context every time the server is loaded.

### Is the io.github.GuardBee/rug-pull-detector MCP server still maintained?

io.github.GuardBee/rug-pull-detector is still listed as active in the MCP registry. We last reached this channel on 25 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

### What licence is the io.github.GuardBee/rug-pull-detector MCP server under?

io.github.GuardBee/rug-pull-detector declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.

## Links

- npm package: https://www.npmjs.com/package/@guardbee/mcp-rug-pull-detector
- Socket report: https://socket.dev/npm/package/@guardbee/mcp-rug-pull-detector
- Repository: https://github.com/GuardBee/guardbee-mcp
- Changelog RSS feed: https://verifymcp.io/servers/guardbee-rug-pull-detector/guardbee-mcp-rug-pull-detector.xml
- Changelog JSON feed: https://verifymcp.io/servers/guardbee-rug-pull-detector/guardbee-mcp-rug-pull-detector.json
- HTML version of this page: https://verifymcp.io/servers/guardbee-rug-pull-detector/guardbee-mcp-rug-pull-detector