verdix
OfficialRelated Servers
Alternatives to verdix
No user-submitted related servers found.
Related Servers
- FlicenseAqualityCmaintenanceAgent-Level Transaction Safety Oracle. Before an AI agent signs a blockchain transaction, it returns a SAFE/UNSAFE verdict with a SENTINEL Score (AAA-D) and risk flags. Pay-per-call $0.005 USDC via x402 on Base.1-
- FlicenseNot gradedqualityDmaintenancePay-per-use AI security and research tools for autonomous agents on Base, enabling honeypot detection, risk assessment, wallet analysis, and yield optimization via the x402 protocol.1-
- FlicenseNot gradedqualityDmaintenanceProvides counterparty risk checks for any EVM address, returning malicious-history flags, tiered risk scoring, and plain-language summaries via x402 payment.-
- FlicenseNot gradedqualityCmaintenanceAI-synthesized 3-bullet DeFi risk dossier for any Base wallet. Pre-trade counterparty vetting for MEV and arbitrage bots via x402 ($0.10 USDC per query).-
- AlicenseNot gradedqualityCmaintenanceEnables 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.MIT

AgentRisk MCPofficial
AlicenseAqualityCmaintenanceEnables AI agents on Base to call a check_token_risk tool before trading, providing honeypot detection, LP-lock verification, brand impersonation checks, and live sell simulation across Uniswap V2/V3/V4 and Aerodrome with a clear risk score and should-trade decision.12 npmMIT
TDQS
Scored across 6 tools
check_address_risk takes a tier parameter and is functionally identical to the three pinned tier variants (quick, standard, deep) and largely overlaps lite. The descriptions explicitly acknowledge this equivalence, but four+ tools that reach the same verdict for the same address still create real misselection risk.
All tools use consistent snake_case with a predictable check_address_risk_<tier> family plus get_pricing. The base tool omits the tier suffix, a minor deviation, but overall the pattern is clear and readable.
Six tools is a reasonable scope for a single-purpose screening service. However, the four near-duplicate risk-check tools inflate the count where one parameterized tool plus get_pricing would suffice.
The domain is EVM/Base address screening, and the surface covers the lite→deep tiers plus pricing disclosure and payment config, which fits the stated purpose. Gaps like batch/multi-address screening or other chains exist but are minor for the declared scope.