io.github.4hmetuyar/rug-pull-detector
NPM · @GUARDBEE/MCP-RUG-PULL-DETECTOR
Baselines an MCP server's tools and detects tool-definition changes after approval
Available components
Last scanned (5 hours ago)
Scores higher than 60% of npm servers
Category Security
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. How we score → Why this is hard to score →
Supply Chain Security98
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- 31 of 95 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 3 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability74
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 393 tokens (~131/item across 3 items; 3 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management63
- Stability observed for 19 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 3 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 17 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 60 to 63. That category is still filling its 30-day observation window: 18 days of observed history at the previous scan, 19 at this one. The score rises as the window fills, whether or not the server changes.
- 15 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 53 to 57. That category is still filling its 30-day observation window: 16 days of observed history at the previous scan, 17 at this one. The score rises as the window fills, whether or not the server changes.
- 13 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 47 to 50. That category is still filling its 30-day observation window: 14 days of observed history at the previous scan, 15 at this one. The score rises as the window fills, whether or not the server changes.
- 11 Oct 26 +2
No change was recorded against any check on this day. Stability & Change Management went from 30 to 43. That category is still filling its 30-day observation window: 9 days of observed history at the previous scan, 13 at this one. The score rises as the window fills, whether or not the server changes.
- 7 Oct 26 +4
- Stability: unverified → 0.30 ▲ functional
- 29 Sept 26 +15
- Malware scan: unverified → pass ▲ security
- 28 Sept 26 55
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 17 Oct 2026 · Analysed npm/@guardbee/mcp-rug-pull-detector@0.2.1
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Background: How many MCP packages publish verified provenance →
Dependencies 95 packages
| Packages resolved | 95 |
|---|---|
| Stale | 31 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
baseline_server ~167
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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) |
No output schema declared.
No examples provided.
check_server ~206
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).
| Name | Type | Req | Description |
|---|---|---|---|
| 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) |
No output schema declared.
No examples provided.
list_baselines ~20
List every server this scanner has a stored baseline for
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
How do I install the io.github.4hmetuyar/rug-pull-detector MCP server?
io.github.4hmetuyar/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.
npm · @guardbee/mcp-rug-pull-detector
claude mcp add 4hmetuyar-rug-pull-detector -- npx -y @guardbee/mcp-rug-pull-detector
What is the io.github.4hmetuyar/rug-pull-detector MCP server?
io.github.4hmetuyar/rug-pull-detector is an MCP server listed in the public MCP registry as io.github.4hmetuyar/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.4hmetuyar/rug-pull-detector MCP server safe to use?
io.github.4hmetuyar/rug-pull-detector scores 79 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 17 October 2026. It declares no install or post-install scripts. 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.4hmetuyar/rug-pull-detector MCP server expose?
io.github.4hmetuyar/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.4hmetuyar/rug-pull-detector MCP server still maintained?
io.github.4hmetuyar/rug-pull-detector is still listed as active in the MCP registry. We last reached this channel on 17 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.4hmetuyar/rug-pull-detector MCP server under?
io.github.4hmetuyar/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.