token-verdict-mcp
Related Servers
Alternatives to token-verdict-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceEnables AI agents to access pay-per-call onchain and URL safety APIs over MCP, covering transaction explanations, token approval checks, address inspection, contract risk heuristics, URL safety, gas snapshots, ENS resolution, calldata decoding, and wallet portfolio data. Payments are handled per call in USDC on Base via x402, with no signup or API key required.1MIT
- AlicenseAqualityCmaintenanceEnables MCP-capable AI agents to make pay-per-call Solana data requests (snapshots, risk checks, token reports, health, balances, transactions, trending pairs) with automatic USDC settlement over x402.5MIT
- AlicenseAqualityCmaintenanceEnables AI assistants to call pay-per-call x402 endpoints on Base mainnet using the caller's own USDC wallet, covering single and batch token risk checks, the latest BTC radar signal, project info, and a free health probe. Payments are EIP-3009 signed with a configurable per-call spending cap, and any quote with an unexpected payee, network, or asset is refused before payment.5MIT
- AlicenseAqualityCmaintenanceEnables AI agents to check an EVM address on Base for risk (safe, caution, danger) before sending funds, with reasons, paid per call via x402 from the user's own wallet.7309 npm1MIT
- AlicenseNot gradedqualityCmaintenanceChecks token contract safety for honeypot, tax, proxy, blacklist, ownership risks, and returns a risk score, enabling rug-pull protection for agents via pay-per-call x402 micropayments.MIT
- AlicenseNot gradedqualityCmaintenanceEnables AI agents to request a sourced, verdict-free case file for a Solana token mint over MCP, returning on-chain facts such as authorities, creator wallet age, insider networks, and metadata-injection flags. Payments per check can be settled with x402.Apache 2.0
TDQS
Scored across 1 tool
There is only one tool, so there is no possibility of selecting the wrong one. Its purpose—fetching a pre-trade risk verdict for a token address—is stated unambiguously.
The name token_verdict uses clean snake_case and mirrors the backing service name, but it is a noun phrase rather than the verb_noun pattern typical of action-oriented tool sets. With only one tool there is no inconsistency to speak of, just a minor stylistic deviation.
The server wraps a single paid x402 endpoint ($0.02 USDC per call), so one tool is defensible and each tool does earn its place. However, a one-tool surface is thin and sits at the borderline of the 1-2 tool range.
For the narrow stated purpose—pre-trade risk assessment—the tool returns everything needed: verdict, 0-100 score, six weighted signals, analyst commentary, and raw market data. Minor gaps exist (no batch/multi-token lookup, no way to enumerate supported chains beyond the description), but agents can work around these with the documented chain argument.