# Token Safety (Base) (remote · token-safety-mcp.restockalarm.workers.dev)

Base token safety: one-call verdict, risk score, rug check, holders, momentum. x402 + free demo.

- Trust score: 63/100 (medium)
- Change this week: +1
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- remote · `token-safety-mcp.restockalarm.workers.dev`: 63/100 (this document), [markdown](https://verifymcp.io/servers/dev-workers-restockalarm-token-safety-mcp-token-safety/token-safety-mcp.md), [page](https://verifymcp.io/servers/dev-workers-restockalarm-token-safety-mcp-token-safety/token-safety-mcp)

## Channel facts

- Endpoint: `https://token-safety-mcp.restockalarm.workers.dev/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.1.0`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, 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.

- **Endpoint Security**: 46/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation not fully verified: no authorisation is required to call this server, and 5 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.
  - HTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 65/100
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 849 tokens (~169/item across 5 items; 5 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 38/100
  - Stability check failed: schema churn in the 17 days we've observed: 1 tool removals, 0 breaking changes, 0 auth/transport breaks, 0 additions.
- **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 5 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 6 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 Token Safety (Base) MCP server?

Token Safety (Base) is a hosted endpoint at https://token-safety-mcp.restockalarm.workers.dev/mcp, so there is nothing to install locally. 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 --transport http dev-workers-restockalarm-token-safety-mcp-token- 'https://token-safety-mcp.restockalarm.workers.dev/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "dev-workers-restockalarm-token-safety-mcp-token-": {
      "url": "https://token-safety-mcp.restockalarm.workers.dev/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "dev-workers-restockalarm-token-safety-mcp-token-": {
      "type": "http",
      "url": "https://token-safety-mcp.restockalarm.workers.dev/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.dev-workers-restockalarm-token-safety-mcp-token-]
url = "https://token-safety-mcp.restockalarm.workers.dev/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "dev-workers-restockalarm-token-safety-mcp-token-": {
      "type": "remote",
      "url": "https://token-safety-mcp.restockalarm.workers.dev/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add dev-workers-restockalarm-token-safety-mcp-token- --url 'https://token-safety-mcp.restockalarm.workers.dev/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  dev-workers-restockalarm-token-safety-mcp-token-:
    url: "https://token-safety-mcp.restockalarm.workers.dev/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "dev-workers-restockalarm-token-safety-mcp-token-": {
      "Transport": "http",
      "Url": "https://token-safety-mcp.restockalarm.workers.dev/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add dev-workers-restockalarm-token-safety-mcp-token- -t streamable-http -u 'https://token-safety-mcp.restockalarm.workers.dev/mcp'
```

### Other

```json
{
  "mcpServers": {
    "dev-workers-restockalarm-token-safety-mcp-token-": {
      "type": "http",
      "url": "https://token-safety-mcp.restockalarm.workers.dev/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## 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-04 (score 63, +1)

No change was recorded against any check on this day. Stability & Change Management went from 31 to 35.

### 2026-11-01 (score 62, +1)

No change was recorded against any check on this day. Stability & Change Management went from 21 to 25.

### 2026-10-30 (score 61, −1)

- [functional regression] Schema quality: 134 → 169
- [cosmetic] “holder_check” reworded the description of “address”
- [cosmetic] “momentum_score” reworded the description of “address”
- [cosmetic] “rug_check” reworded the description of “address”
- [cosmetic] “token_risk” reworded the description of “address”
- [cosmetic] “token_verdict” reworded the description of “address”

### 2026-10-29 (score 62, 0)

- [security] The server rewrote its instructions, which are the text every model session reads
- [security] Tool “holder_check” rewrote its description, which is the text the model reads
- [security] Tool “rug_check” rewrote its description, which is the text the model reads
- [security] Tool “token_risk” rewrote its description, which is the text the model reads
- [security] Tool “token_verdict” rewrote its description, which is the text the model reads
- [functional regression] Schema quality: pass → fail

### 2026-10-28 (score 62, +1)

No change was recorded against any check on this day. Stability & Change Management went from 8 to 11.

### 2026-10-27 (score 61, −2)

- [security regression] Stability: 0.23 → fail
- [security regression] A breaking change shipped without a version bump: still 1.0.0
- [security regression] Tool “token_safety_demo” was removed
- [security] The server rewrote its instructions, which are the text every model session reads
- [security] Tool “token_verdict” rewrote its description, which is the text the model reads

### 2026-10-24 (score 63, +1)

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

### 2026-10-22 (score 62, +1)

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

## MCP tools (5)

### `token_verdict` (~167 tokens)

One-call verdict for an ERC-20 on Base: runs token risk (incl. holder concentration), rug-pull and momentum checks plus contract flags (proxy, blacklist, pause, selfdestruct, own on-chain sell simulation) and returns avoid / high_risk / caution / low_risk with a one-line English summary. Use once before buying or listing an unknown Base token. $0.01 via x402. Not investment advice.

Input parameters:

- `address` (string): ERC-20 contract address on Base (0x + 40 hex). Tool calls are paid via x402 with or without it; if omitted, the paid call returns the AERO example with example=true. Free look without payment: GET ht…

### `token_risk` (~141 tokens)

Risk score 0-100 (higher = riskier) for an ERC-20 on Base: derived liquidity view, holder concentration, sell-blocked/tax flags from our own on-chain sell simulation. Use before buying or listing an unknown Base token. $0.01 via x402. Not investment advice.

Input parameters:

- `address` (string): ERC-20 contract address on Base (0x + 40 hex). Tool calls are paid via x402 with or without it; if omitted, the paid call returns the AERO example with example=true. Free look without payment: GET ht…

### `rug_check` (~139 tokens)

Rug-pull check for an ERC-20 on Base: rug_pull true/false, confidence and 5 signals (liquidity removal, wash trading, LP lock, owner wallet, sell tax from our own sell simulation). Use before buying a new Base token. $0.02 via x402.

Input parameters:

- `address` (string): ERC-20 contract address on Base (0x + 40 hex). Tool calls are paid via x402 with or without it; if omitted, the paid call returns the AERO example with example=true. Free look without payment: GET ht…

### `holder_check` (~119 tokens)

PAUSED: holder_check answers paused without asking for payment and is never charged (its top-holder source was a third-party API we no longer use). For holder concentration use token_risk (holder_concentration).

Input parameters:

- `address` (string): ERC-20 contract address on Base (0x + 40 hex). Tool calls are paid via x402 with or without it; if omitted, the paid call returns the AERO example with example=true. Free look without payment: GET ht…

### `momentum_score` (~131 tokens)

Momentum score 0-100 for an ERC-20 on Base from 24 h volume, volume vs liquidity and price change, with confidence low/medium/high. Null for stablecoins. Use to rank Base tokens by activity. $0.02 via x402.

Input parameters:

- `address` (string): ERC-20 contract address on Base (0x + 40 hex). Tool calls are paid via x402 with or without it; if omitted, the paid call returns the AERO example with example=true. Free look without payment: GET ht…

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/dev-workers-restockalarm-token-safety-mcp-token-safety/token-safety-mcp#diagnostics

## Score history

- 2026-11-05: 63
- 2026-11-04: 63
- 2026-11-03: 62
- 2026-11-02: 62
- 2026-11-01: 62
- 2026-10-31: 61
- 2026-10-30: 61
- 2026-10-29: 62
- 2026-10-28: 62
- 2026-10-27: 61
- 2026-10-26: 63
- 2026-10-25: 63
- 2026-10-24: 63
- 2026-10-23: 62
- 2026-10-22: 62
- 2026-10-21: 61
- 2026-10-20: 61
- 2026-10-19: 60

## Common questions

### What is the Token Safety (Base) MCP server?

Token Safety (Base) is an MCP server listed in the public MCP registry as dev.workers.restockalarm.token-safety-mcp/token-safety. Base token safety: one-call verdict, risk score, rug check, holders, momentum. x402 + free demo. This page covers its hosted endpoint (https://token-safety-mcp.restockalarm.workers.dev/mcp).

### Is the Token Safety (Base) MCP server safe to use?

Token Safety (Base) scores 63 out of 100 on VerifyMCP. 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 Safety (Base) MCP server expose?

Token Safety (Base) exposes 5 tools: token_verdict, token_risk, rug_check, holder_check, momentum_score. Their descriptions and schemas cost roughly 697 tokens of context every time the server is loaded.

### Does the Token Safety (Base) MCP server require authentication?

No. We connected to Token Safety (Base) without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the Token Safety (Base) MCP server still maintained?

Token Safety (Base) 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.

## Links

- Remote endpoint: https://token-safety-mcp.restockalarm.workers.dev/mcp
- Website: https://product-katalog.restockalarm.workers.dev/token-safety
- Changelog RSS feed: https://verifymcp.io/servers/dev-workers-restockalarm-token-safety-mcp-token-safety/token-safety-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/dev-workers-restockalarm-token-safety-mcp-token-safety/token-safety-mcp.json
- HTML version of this page: https://verifymcp.io/servers/dev-workers-restockalarm-token-safety-mcp-token-safety/token-safety-mcp