# Token Risk (npm · @pipeworx/mcp-token-risk)

Token Risk — rug-pull / honeypot screening for crypto tokens.

- Trust score: 80/100 (high trust)
- Change this week: 0
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- remote · `gateway.pipeworx.io`: 63/100, [markdown](https://verifymcp.io/servers/pipeworx-io-token-risk/token-risk-mcp.md), [page](https://verifymcp.io/servers/pipeworx-io-token-risk/token-risk-mcp)
- npm · `@pipeworx/mcp-token-risk`: 80/100 (this document), [markdown](https://verifymcp.io/servers/pipeworx-io-token-risk/pipeworx-mcp-token-risk.md), [page](https://verifymcp.io/servers/pipeworx-io-token-risk/pipeworx-mcp-token-risk)

## Channel facts

- Registry: `npm`
- Package: `@pipeworx/mcp-token-risk`
- Version: `0.2.0`
- 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-11-05.

- **Supply Chain Security**: 100/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.
  - No production dependencies, so there is no dependency health to assess.
- **Provenance & Transparency**: 97/100
  - Source repository is publicly reachable at the declared URL.
  - Cryptographically verified build provenance (signed, bound to pipeworx-io/mcp-token-risk).
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 6 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 68/100
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 396 tokens (~198/item across 2 items; 2 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 0/100
  - Stability not yet verified: not enough scan history yet (needs a 30-day window).
- **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 2 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.

**Unverified: 1 category.** A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.

## Install

### How do I install the Token Risk MCP server?

Token Risk runs locally as an npm package, launched with npx -y @pipeworx/mcp-token-risk. 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 pipeworx-io-token-risk -- npx -y @pipeworx/mcp-token-risk
```

### Cursor

```json
{
  "mcpServers": {
    "pipeworx-io-token-risk": {
      "command": "npx",
      "args": [
        "-y",
        "@pipeworx/mcp-token-risk"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "pipeworx-io-token-risk": {
      "command": "npx",
      "args": [
        "-y",
        "@pipeworx/mcp-token-risk"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add pipeworx-io-token-risk -- npx -y @pipeworx/mcp-token-risk
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "pipeworx-io-token-risk": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "@pipeworx/mcp-token-risk"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add pipeworx-io-token-risk --command npx --arg -y --arg @pipeworx/mcp-token-risk
```

### Hermes

```yaml
mcp_servers:
  pipeworx-io-token-risk:
    command: "npx"
    args: ["-y", "@pipeworx/mcp-token-risk"]
```

### Netclaw

```json
{
  "McpServers": {
    "pipeworx-io-token-risk": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "@pipeworx/mcp-token-risk"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add pipeworx-io-token-risk -t stdio -c npx -a -y @pipeworx/mcp-token-risk
```

### Other

```json
{
  "mcpServers": {
    "pipeworx-io-token-risk": {
      "command": "npx",
      "args": [
        "-y",
        "@pipeworx/mcp-token-risk"
      ]
    }
  }
}
```

## 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-11-05 (score 80, 0)

- [functional regression] Security disclosure: unverified → fail

### 2026-11-04 (score 80, 0)

- [functional regression] Security disclosure: fail → unverified

### 2026-10-31 (score 80, 0)

- [functional regression] Security disclosure: unverified → fail

### 2026-10-29 (score 80)

First indexed and scored.

## MCP tools (2)

### `token_risk_evm` (~222 tokens)

Rug-pull / honeypot / scam RISK SCREENING for an EVM token (Ethereum, BSC, Base, Arbitrum, Polygon, Optimism, Avalanche, and more). Pass the token CONTRACT ADDRESS and the chain. Detects honeypots (can you actually sell?), buy/sell tax, mintable supply, hidden/renounceable owner, owner-can-change-balances, blacklist/whitelist controls, proxy/upgradeable code, unverified source, and holder concentration — the standard rug-pull red flags. Returns a computed red_flags[] list plus the raw GoPlus Security facts. Keyless, live on-chain. Use before buying/interacting with any token, or for "is $TOKEN a scam / honeypot / safe?".

Input parameters:

- `chain` (string): Chain name (ethereum, bsc, base, arbitrum, polygon, optimism, avalanche, …) or a numeric GoPlus chain_id. Default ethereum.
- `contract_address` (string, required): The token contract address (0x...).

### `token_risk_solana` (~122 tokens)

Rug-pull / scam RISK SCREENING for a Solana SPL token. Pass the token MINT address. Detects active mint authority (supply can be inflated), freeze authority (your balance can be frozen), closable/mutable-metadata flags, transfer fees/hooks, and holder + LP concentration. Returns a computed red_flags[] list plus the raw GoPlus Security facts. Keyless, live on-chain. Use for "is this Solana token safe / a rug?".

Input parameters:

- `contract_address` (string, required): The SPL token mint address.

## Diagnostics

Captured diagnostic sections: Provenance, Dependencies. The full working is on the page: https://verifymcp.io/servers/pipeworx-io-token-risk/pipeworx-mcp-token-risk#diagnostics

## Score history

- 2026-11-05: 80
- 2026-11-04: 80
- 2026-11-03: 80
- 2026-11-02: 80
- 2026-11-01: 80
- 2026-10-31: 80
- 2026-10-30: 80
- 2026-10-29: 80

## Common questions

### What is the Token Risk MCP server?

Token Risk is an MCP server listed in the public MCP registry as io.github.pipeworx-io/token-risk. Token Risk, rug-pull / honeypot screening for crypto tokens. This page covers its npm package (@pipeworx/mcp-token-risk).

### Is the Token Risk MCP server safe to use?

Token Risk scores 80 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 November 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 Token Risk MCP server expose?

Token Risk exposes 2 tools: token_risk_evm, token_risk_solana. Their descriptions and schemas cost roughly 344 tokens of context every time the server is loaded.

### Is the Token Risk MCP server still maintained?

Token Risk is still listed as active in the MCP registry. We last reached this channel on 5 November 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 Token Risk MCP server under?

Token Risk 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/@pipeworx/mcp-token-risk
- Socket report: https://socket.dev/npm/package/@pipeworx/mcp-token-risk
- Repository: https://github.com/pipeworx-io/mcp-token-risk
- Website: https://pipeworx.io/packs/token-risk
- Changelog RSS feed: https://verifymcp.io/servers/pipeworx-io-token-risk/pipeworx-mcp-token-risk.xml
- Changelog JSON feed: https://verifymcp.io/servers/pipeworx-io-token-risk/pipeworx-mcp-token-risk.json
- HTML version of this page: https://verifymcp.io/servers/pipeworx-io-token-risk/pipeworx-mcp-token-risk