# Token Risk Checker (remote · checker-production-40a5.up.railway.app)

Base token risk screen: rug-pull liquidity, honeypots, copycats. Pay per call via x402 (USDC).

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

## Components

- remote · `checker-production-40a5.up.railway.app`: 86/100 (this document), [markdown](https://verifymcp.io/servers/dimsum1232011-svg-token-risk-checker/checker-production-40a5.md), [page](https://verifymcp.io/servers/dimsum1232011-svg-token-risk-checker/checker-production-40a5)

## Channel facts

- Endpoint: `https://checker-production-40a5.up.railway.app/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.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-21.

- **Endpoint Security**: 74/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation.
  - HTTPS is enforced; there's no plaintext access path.
  - 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**: 78/100
  - AI-judged instruction clarity (excellent).
  - Tool/resource definitions use about 246 tokens (~123/item across 2 items; 2 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 100/100
  - No destabilizing schema changes in the last 30 days.
- **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 2 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 Risk Checker MCP server?

Token Risk Checker is a hosted endpoint at https://checker-production-40a5.up.railway.app/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 dimsum1232011-svg-token-risk-checker 'https://checker-production-40a5.up.railway.app/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "dimsum1232011-svg-token-risk-checker": {
      "url": "https://checker-production-40a5.up.railway.app/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "dimsum1232011-svg-token-risk-checker": {
      "type": "http",
      "url": "https://checker-production-40a5.up.railway.app/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.dimsum1232011-svg-token-risk-checker]
url = "https://checker-production-40a5.up.railway.app/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "dimsum1232011-svg-token-risk-checker": {
      "type": "remote",
      "url": "https://checker-production-40a5.up.railway.app/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add dimsum1232011-svg-token-risk-checker --url 'https://checker-production-40a5.up.railway.app/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  dimsum1232011-svg-token-risk-checker:
    url: "https://checker-production-40a5.up.railway.app/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "dimsum1232011-svg-token-risk-checker": {
      "Transport": "http",
      "Url": "https://checker-production-40a5.up.railway.app/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add dimsum1232011-svg-token-risk-checker -t streamable-http -u 'https://checker-production-40a5.up.railway.app/mcp'
```

### Other

```json
{
  "mcpServers": {
    "dimsum1232011-svg-token-risk-checker": {
      "type": "http",
      "url": "https://checker-production-40a5.up.railway.app/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-20 (score 86, +1)

- [security] Stability: 0.97 → pass

### 2026-11-18 (score 85, +1)

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

### 2026-11-16 (score 84, +1)

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

### 2026-11-14 (score 83, +1)

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

### 2026-11-12 (score 82, +1)

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

### 2026-11-10 (score 81, +1)

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

### 2026-11-07 (score 80, +1)

- [functional improvement] Endpoint reachability: unreachable → reachable

### 2026-11-06 (score 79, +1)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

## MCP tools (2)

### `check_token_risk` (~135 tokens)

Token risk report

Full risk report for a Base token, with an AI-written plain-English summary: whether the creator or launch wallet can pull the pool liquidity (incl. Uniswap V4), copycat tickers, launch platform (Clanker/Doppler/B20), honeypot and taxes, mint/pause/blacklist powers, upgradeable proxy, ownership and holders. Returns a 0-100 score, LOW/MEDIUM/HIGH level and per-check reasons. Automated risk screen, not a security audit.

Input parameters:

- `address` (string, required): Token contract address
- `chain` (string): Chain name; defaults to base

### `quick_token_risk` (~111 tokens)

Quick token risk check

Quick risk check for a Base token: the same checks as check_token_risk (creator-pullable liquidity, copycats, honeypot and taxes, owner powers, proxy, ownership, launch platform, holders) without the AI summary. Returns a 0-100 score, LOW/MEDIUM/HIGH level and per-check reasons. Automated risk screen, not a security audit.

Input parameters:

- `address` (string, required): Token contract address
- `chain` (string): Chain name; defaults to base

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/dimsum1232011-svg-token-risk-checker/checker-production-40a5#diagnostics

## Score history

- 2026-11-21: 86
- 2026-11-20: 86
- 2026-11-19: 85
- 2026-11-18: 85
- 2026-11-17: 84
- 2026-11-16: 84
- 2026-11-15: 83
- 2026-11-14: 83
- 2026-11-13: 82
- 2026-11-12: 82
- 2026-11-11: 81
- 2026-11-10: 81
- 2026-11-09: 80
- 2026-11-08: 80
- 2026-11-07: 80
- 2026-11-06: 79
- 2026-11-05: 78
- 2026-11-04: 78
- 2026-11-03: 78
- 2026-11-02: 77
- 2026-11-01: 77
- 2026-10-31: 76
- 2026-10-30: 76
- 2026-10-29: 75
- 2026-10-28: 75
- 2026-10-27: 74
- 2026-10-26: 74
- 2026-10-25: 73
- 2026-10-24: 73
- 2026-10-23: 73

## Common questions

### What is the Token Risk Checker MCP server?

Token Risk Checker is an MCP server listed in the public MCP registry as io.github.DIMSUM1232011-svg/token-risk-checker. Base token risk screen: rug-pull liquidity, honeypots, copycats. Pay per call via x402 (USDC). This page covers its hosted endpoint (https://checker-production-40a5.up.railway.app/mcp).

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

Token Risk Checker scores 86 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 Risk Checker MCP server expose?

Token Risk Checker exposes 2 tools: check_token_risk, quick_token_risk. Their descriptions and schemas cost roughly 246 tokens of context every time the server is loaded.

### Does the Token Risk Checker MCP server require authentication?

No. We connected to Token Risk Checker without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

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

Token Risk Checker is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

### What did VerifyMCP test on the Token Risk Checker MCP server?

VerifyMCP ran 13 checks on Token Risk Checker, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.

## Links

- Remote endpoint: https://checker-production-40a5.up.railway.app/mcp
- Website: https://checker-production-40a5.up.railway.app/docs
- Changelog RSS feed: https://verifymcp.io/servers/dimsum1232011-svg-token-risk-checker/checker-production-40a5.xml
- Changelog JSON feed: https://verifymcp.io/servers/dimsum1232011-svg-token-risk-checker/checker-production-40a5/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/dimsum1232011-svg-token-risk-checker/checker-production-40a5.json
- HTML version of this page: https://verifymcp.io/servers/dimsum1232011-svg-token-risk-checker/checker-production-40a5
