verdix
OfficialRelated Servers
Alternatives to verdix
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceEnables AI agents to run honeypot and owner-power safety checks on Base tokens and to read wallet ETH and USDC balances, with every answer sourced from real chain data and paid per call in USDC via x402.MIT
- 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 gradedqualityFmaintenanceProvides counterparty risk checks for any EVM address, returning malicious-history flags, tiered risk scoring, and plain-language summaries via x402 payment.-
- FlicenseNot gradedqualityDmaintenanceAI-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).-
- 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
TDQS
Scored across 7 tools
Four tools (check_address_risk, check_address_risk_quick, check_address_risk_standard, check_address_risk_deep) all perform the same pre-send address screen on Base and differ only by price tier, while the generic tool can already select a tier. The descriptions explicitly address this redundancy and explain when to use each, which prevents the set from being genuinely confusing, but the boundaries are still overlapping by design.
All risk-screening tools follow a consistent snake_case check_address_risk[_tier] pattern, and check_address_poisoning fits the same verb_noun convention. get_pricing is the only different verb, which is appropriate for its free utility role.
Seven tools is a reasonable size for a focused address-risk API and keeps the surface manageable. However, the three tier-pinned wrappers largely duplicate the generic check_address_risk tool, so the set is slightly larger than strictly necessary.
The surface covers the core lifecycle: free poisoning lookup, lite/quick/standard/deep screening, a flexible tiered tool, and pricing/wallet status. Minor gaps remain, such as batch screening or explicit supported-chain discovery, but the main pre-send workflows are covered.