# Base Token Verdict (remote · tokenverdict-al6bxcngia-ue.a.run.app)

Base token verdict: GO/HOLD/BLOCK decision + score on any Base token address. $0.02/call via x402.

- Trust score: 72/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-21

## Components

- remote · `tokenverdict-al6bxcngia-ue.a.run.app`: 72/100 (this document), [markdown](https://verifymcp.io/servers/theharrisontruong-web-tokenverdict/tokenverdict-al6bxcngia-ue.md), [page](https://verifymcp.io/servers/theharrisontruong-web-tokenverdict/tokenverdict-al6bxcngia-ue)

## Channel facts

- Endpoint: `https://tokenverdict-al6bxcngia-ue.a.run.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**: 71/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 584 tokens (~292/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**: 13/100
  - Stability observed for 4 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **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 current MCP spec version (2026-07-28).

## Install

### How do I install the Base Token Verdict MCP server?

Base Token Verdict is a hosted endpoint at https://tokenverdict-al6bxcngia-ue.a.run.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 theharrisontruong-web-tokenverdict 'https://tokenverdict-al6bxcngia-ue.a.run.app/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "theharrisontruong-web-tokenverdict": {
      "url": "https://tokenverdict-al6bxcngia-ue.a.run.app/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "theharrisontruong-web-tokenverdict": {
      "type": "http",
      "url": "https://tokenverdict-al6bxcngia-ue.a.run.app/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.theharrisontruong-web-tokenverdict]
url = "https://tokenverdict-al6bxcngia-ue.a.run.app/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "theharrisontruong-web-tokenverdict": {
      "type": "remote",
      "url": "https://tokenverdict-al6bxcngia-ue.a.run.app/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add theharrisontruong-web-tokenverdict --url 'https://tokenverdict-al6bxcngia-ue.a.run.app/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  theharrisontruong-web-tokenverdict:
    url: "https://tokenverdict-al6bxcngia-ue.a.run.app/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "theharrisontruong-web-tokenverdict": {
      "Transport": "http",
      "Url": "https://tokenverdict-al6bxcngia-ue.a.run.app/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add theharrisontruong-web-tokenverdict -t streamable-http -u 'https://tokenverdict-al6bxcngia-ue.a.run.app/mcp'
```

### Other

```json
{
  "mcpServers": {
    "theharrisontruong-web-tokenverdict": {
      "type": "http",
      "url": "https://tokenverdict-al6bxcngia-ue.a.run.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 72, +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.

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

- [functional improvement] Stability: unverified → 0.03

### 2026-11-17 (score 70)

First indexed and scored.

## MCP tools (2)

### `token_verdict` (~415 tokens)

Full Base token verdict for a token contract address. Pulls free public onchain data (Base RPC, DexScreener, GoPlus token security) and runs 10 weighted checks: contract code present, honeypot / cannot-sell flags, mintable supply and hidden owner, owner control surface (proxy, pausable transfers, modifiable taxes, ownership take-back, self-destruct), buy/sell taxes, holder concentration (top-10 share), liquidity depth across Base DEX pairs, liquidity locked/burned share, 24h trading activity, and token age. Returns machine-readable JSON LED BY A FAIL-CLOSED TRADE DECISION — GO / HOLD / BLOCK — plus a one-line plain-language verdict, a 0-100 score, an A-F grade, a risk level, the top flags, per-check pass/partial/fail/unknown with evidence, a token block (name, symbol, supply, holder count), a market block (price, liquidity, 24h volume/txns, main pair, age), the decision basis, and a per-source status map. FAIL-CLOSED: if any key data source fails or returns nothing, the decision can never be GO; if two or more fail, it is BLOCK. HONEST LIMITS: a point-in-time snapshot — liquidity, holders, and flags can change within minutes on young tokens; checks that cannot be evaluated return unknown, never guesses; this is a mechanical risk scan, not financial advice. Cost: $0.02 USDC on Base per call, paid via x402 — the caller's agent pays from its owner's approved wallet; no API key needed. Use this as a pre-trade screen before buying or quoting any Base token.

Input parameters:

- `address` (string, required): Base token contract address (0x-prefixed, 40 hex chars), e.g. 0x4ed4E862860beD51a9570b96d89aF5E1B0Efefed

### `token_verdict_lite` (~169 tokens)

FREE lite Base token verdict for a token contract address. Runs the same 10 checks as token_verdict but returns top-line results only: the GO / HOLD / BLOCK decision, the one-line verdict, 0-100 score, A-F grade, risk level, and the top 3 flag titles — detail is capped (no per-check evidence, no market block). Use this to triage whether a token deserves the full token_verdict report, or call token_verdict directly for the complete evidence-backed scan.

Input parameters:

- `address` (string, required): Base token contract address (0x-prefixed, 40 hex chars), e.g. 0x4ed4E862860beD51a9570b96d89aF5E1B0Efefed

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/theharrisontruong-web-tokenverdict/tokenverdict-al6bxcngia-ue#diagnostics

## Score history

- 2026-11-21: 72
- 2026-11-20: 72
- 2026-11-19: 71
- 2026-11-18: 71
- 2026-11-17: 70

## Common questions

### What is the Base Token Verdict MCP server?

Base Token Verdict is an MCP server listed in the public MCP registry as io.github.theharrisontruong-web/tokenverdict. Base token verdict: GO/HOLD/BLOCK decision + score on any Base token address. $0.02/call via x402. This page covers its hosted endpoint (https://tokenverdict-al6bxcngia-ue.a.run.app/mcp).

### Is the Base Token Verdict MCP server safe to use?

Base Token Verdict scores 72 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 Base Token Verdict MCP server expose?

Base Token Verdict exposes 2 tools: token_verdict, token_verdict_lite. Their descriptions and schemas cost roughly 584 tokens of context every time the server is loaded.

### Does the Base Token Verdict MCP server require authentication?

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

### Is the Base Token Verdict MCP server still maintained?

Base Token Verdict 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 Base Token Verdict MCP server?

VerifyMCP ran 13 checks on Base Token Verdict, 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://tokenverdict-al6bxcngia-ue.a.run.app/mcp
- Repository: https://github.com/theharrisontruong-web/agent-apis
- Website: https://tokenverdict-al6bxcngia-ue.a.run.app/
- Changelog RSS feed: https://verifymcp.io/servers/theharrisontruong-web-tokenverdict/tokenverdict-al6bxcngia-ue.xml
- Changelog JSON feed: https://verifymcp.io/servers/theharrisontruong-web-tokenverdict/tokenverdict-al6bxcngia-ue/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/theharrisontruong-web-tokenverdict/tokenverdict-al6bxcngia-ue.json
- HTML version of this page: https://verifymcp.io/servers/theharrisontruong-web-tokenverdict/tokenverdict-al6bxcngia-ue
