# orbit Token Risk (remote · token-risk.orbit-builder.workers.dev)

Rug check & honeypot flags for Base/Solana tokens. Free preview; full $0.0009/token via x402.

- Trust score: 55/100 (low)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-10-23

## Components

- remote · `token-risk.orbit-builder.workers.dev`: 55/100 (this document), [markdown](https://verifymcp.io/servers/dev-workers-orbit-builder-token-risk-token-risk/token-risk.md), [page](https://verifymcp.io/servers/dev-workers-orbit-builder-token-risk-token-risk/token-risk)

## Channel facts

- Endpoint: `https://token-risk.orbit-builder.workers.dev/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.2.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-10-23.

- **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 2 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**: 55/100
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 568 tokens (~284/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**: 87/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 60% 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: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.

## Install

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

orbit Token Risk is a hosted endpoint at https://token-risk.orbit-builder.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-orbit-builder-token-risk-token-risk 'https://token-risk.orbit-builder.workers.dev/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "dev-workers-orbit-builder-token-risk-token-risk": {
      "url": "https://token-risk.orbit-builder.workers.dev/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "dev-workers-orbit-builder-token-risk-token-risk": {
      "type": "http",
      "url": "https://token-risk.orbit-builder.workers.dev/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.dev-workers-orbit-builder-token-risk-token-risk]
url = "https://token-risk.orbit-builder.workers.dev/mcp"
```

### opencode

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

### OpenClaw

```bash
openclaw mcp add dev-workers-orbit-builder-token-risk-token-risk --url 'https://token-risk.orbit-builder.workers.dev/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  dev-workers-orbit-builder-token-risk-token-risk:
    url: "https://token-risk.orbit-builder.workers.dev/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "dev-workers-orbit-builder-token-risk-token-risk": {
      "Transport": "http",
      "Url": "https://token-risk.orbit-builder.workers.dev/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add dev-workers-orbit-builder-token-risk-token-risk -t streamable-http -u 'https://token-risk.orbit-builder.workers.dev/mcp'
```

### Other

```json
{
  "mcpServers": {
    "dev-workers-orbit-builder-token-risk-token-risk": {
      "type": "http",
      "url": "https://token-risk.orbit-builder.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-10-23 (score 55)

First indexed and scored.

## MCP tools (2)

### `check_token` (~170 tokens)

Token risk check (rug check, honeypot, scam token, memecoin / pump.fun safety) for one Base or Solana token. Free tool: returns risk_level, pass/warn/fail counts and 4 headline flags with raw values, plus the x402 URL for the full report ($0.0009 USDC on Base: GET /v1/check?token=chain:address; cheapest single-token x402 risk check we've found, vs $0.00098-$0.02 for others we checked, Oct 23 2026).

Input parameters:

- `address` (string): token contract (Base) or mint (Solana)
- `chain` (string)
- `token` (string): chain:address, e.g. solana:<mint> or base:0x...

### `check_token_risk` (~106 tokens)

Same as check_token with explicit chain + address: free token risk preview (rug check / honeypot / scam screen) for one Base or Solana token. Full report via x402: $0.0009 per token (GET /v1/check) or $0.015 for 1-10 tokens (POST /v1/risk).

Input parameters:

- `address` (string, required): token contract (Base) or mint (Solana)
- `chain` (string, required)

## Diagnostics

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

## Score history

- 2026-10-23: 55

## Common questions

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

orbit Token Risk is an MCP server listed in the public MCP registry as dev.workers.orbit-builder.token-risk/token-risk. Rug check & honeypot flags for Base/Solana tokens. Free preview; full $0.0009/token via x402. This page covers its hosted endpoint (https://token-risk.orbit-builder.workers.dev/mcp).

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

orbit Token Risk scores 55 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 orbit Token Risk MCP server expose?

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

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

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

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

orbit Token Risk is still listed as active in the MCP registry. We last reached this channel on 23 October 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-risk.orbit-builder.workers.dev/mcp
- Website: https://token-risk.orbit-builder.workers.dev/
- Changelog RSS feed: https://verifymcp.io/servers/dev-workers-orbit-builder-token-risk-token-risk/token-risk.xml
- Changelog JSON feed: https://verifymcp.io/servers/dev-workers-orbit-builder-token-risk-token-risk/token-risk.json
- HTML version of this page: https://verifymcp.io/servers/dev-workers-orbit-builder-token-risk-token-risk/token-risk