fingers

Multiple tool families have fuzzy boundaries: five x402 tools (best_value/fair_price/leaderboard/profile/verdict) heavily overlap, address vetting is split across address_security/counterparty_check/deployer_check/deployer_reputation, and token/NFT safety is spread across token_security, rugcheck, rug_check, nft_security, and robinhood_token_safety. The verbose descriptions try to differentiate these, but an agent must parse extensive nuance to avoid mis-selection, and verify/check_instruction/x402_verdict all return proceed/caution verdicts.

All names are lowercase snake_case, and there are useful prefix families (robinhood_*, x402_*, nft_*, token_*, stock_*, deployer_*, wallet_*). However, conventions mix noun-phrases (address_security, collection_team) with verb phrases (verify, resolve_entity, check_instruction), the same concept is inconsistently named (token_security vs stock_safety), and rug_check vs rugcheck are near-identical names for different purposes.

50 tools is heavy even for the server's broad verification scope, which spans crypto, NFTs, stocks, Robinhood Chain, agents, and x402 payments. The x402 cluster alone accounts for 5 overlapping tools, and several Robinhood safety checks (honeypot_sim, token_safety, clones, movers, authenticity) could be consolidated. The scope justifies a large surface, but not this much redundancy.

For a read-only due-diligence/verification server, the coverage is remarkably complete: it handles the full trust lifecycle from pre-launch (address_security, deployer_check, domain_check, project_links) through live checks (token_security, nft_security, dex_token) to pre-payment (counterparty_check, tx_check, x402_verdict) and post-event (token_outcome, wallet_funds). It also covers adjacent domains (stocks via sec_filings/stock_safety, DeFi via defillama, agents via agent_card_check) with no obvious dead ends.