Token Verdict
MCP server for Token Verdict — pay-per-call token risk verdicts over x402 ($0.02 USDC on Base)
Install
Add this to your client's MCP configuration (Claude Desktop: claude_desktop_config.json; Cursor: .cursor/mcp.json; VS Code and others use the same "mcpServers" shape).
token-verdict-mcpclaude mcp add token-verdict -e 'AGENT_PRIVATE_KEY=<your agent_private_key>' -e 'AGENT_KEY_FILE=<AGENT_KEY_FILE>' -e 'TOKEN_VERDICT_URL=<TOKEN_VERDICT_URL>' -e 'TOKEN_VERDICT_MAX_AMOUNT_UNITS=20000' -- uvx token-verdict-mcp==0.1.2
{
"mcpServers": {
"token-verdict": {
"command": "uvx",
"args": [
"token-verdict-mcp==0.1.2"
],
"env": {
"AGENT_PRIVATE_KEY": "<your agent_private_key>",
"AGENT_KEY_FILE": "<AGENT_KEY_FILE>",
"TOKEN_VERDICT_URL": "<TOKEN_VERDICT_URL>",
"TOKEN_VERDICT_MAX_AMOUNT_UNITS": "20000"
}
}
}
}
Environment variables
AGENT_PRIVATE_KEYsecret EVM private key (0x...) of a wallet holding USDC on Base. Used locally to sign the x402 EIP-3009 authorization. For paid calls.AGENT_KEY_FILEPath to a file containing that key (alternative to AGENT_PRIVATE_KEY).TOKEN_VERDICT_URLService base URL override (default: production).TOKEN_VERDICT_MAX_AMOUNT_UNITSSpend guard per call in USDC micro-units (default 20000 = $0.02, the known price). The client refuses to sign anything priced above it.
Documentation
From the project's README on GitHub, refreshed weekly. Links open on GitHub.
Token Verdict — agent distribution wrappers
Native tool wrappers for Token Verdict, the pay-per-call token risk screen for AI agents ($0.02 USDC per call on Base, via the x402 protocol).
Token Verdict's buyers are other agents. These packages put the service on the shelves agents actually shop from, in the formats they call natively — payment handled by each agent's own wallet, with a spend guard at the known price:
| Package | Stack | What it gives an agent |
|---|---|---|
mcp/ | Python · MCP (stdio) | A token_verdict tool in any MCP host (Claude Desktop, Cursor, custom runtimes), paying via an operator-configured EVM signer. |
agentkit/ | TypeScript · Coinbase AgentKit | A token_verdict action in any AgentKit agent, paying from the agent's EvmWalletProvider. |
Both wrap the same real contract — POST /v1/verdict:
{ "address": "0x2821d96B5FC81aEC3763340b375a846a89A3Ec1b", "chain": "base" }
→ { token, verdict: SOLID|CAUTION|DANGER, score (0–100), signals (six
weighted market-structure signals), take, market }.
Both implement the standard x402 v2 exact-scheme flow (402 → sign an
EIP-3009 USDC authorization → retry with PAYMENT-SIGNATURE), the same
flow used for the service's live cataloging payment; the service settles
through its PayAI facilitator server-side. Neither package contains or
transmits any private key: keys stay in the operator's environment /
wallet provider, and every test payment is mocked — the test fixtures
are the real 402 challenge captured from production (2026-10-23)
and the service engine's own published example verdict.
Service source: QuincyGB/token-verdict
(discovery manifest at /.well-known/x402, agent docs at /skill.md).
MIT licensed.
Frequently asked questions
What is Token Verdict?
MCP server for Token Verdict — pay-per-call token risk verdicts over x402 ($0.02 USDC on Base)
How do I install Token Verdict?
It runs on your machine. In Claude Code: claude mcp add token-verdict -e 'AGENT_PRIVATE_KEY=<your agent_private_key>' -e 'AGENT_KEY_FILE=<AGENT_KEY_FILE>' -e 'TOKEN_VERDICT_URL=<TOKEN_VERDICT_URL>' -e 'TOKEN_VERDICT_MAX_AMOUNT_UNITS=20000' -- uvx token-verdict-mcp==0.1.2. For other clients, paste the JSON configuration from this page into their MCP settings.
Does Token Verdict need an API key?
Yes. It expects AGENT_PRIVATE_KEY, which you set in its configuration.
Is Token Verdict open source?
Yes. Its code is on GitHub under the MIT license.
Who maintains Token Verdict?
It is published by QuincyGB. AI.tn lists it but does not maintain or endorse it.
From the official MCP Registry. Listing is not an endorsement: review a server's code and permissions before giving it access to your data.