ulu-voi-mcp
Related Servers
Alternatives to ulu-voi-mcp
No user-submitted related servers found.
Related Servers
- AlicenseAqualityDmaintenanceAn MCP server that provides a semantic layer for the Voi ecosystem, translating raw blockchain data into human-readable information about protocols, applications, and assets. It enables users to identify contract roles, resolve enVoi names, and explore curated registry data for ecosystem services like HumbleSwap and Nautilus.10MIT
- AlicenseNot gradedqualityBmaintenanceEnables users to search the on-chain index of 378,000+ ERC-8004 agents and read Cybercentry verification results spanning token, code, media, web, and wallet dimensions.MIT
- AlicenseAqualityCmaintenanceProvides read-only access to public referral deals and codes, races and leaderboards, DeFi interface restriction data, x402 catalogs, cp0x facts, and open-source repository listings. Supports natural-language queries such as finding deals for a venue or checking interface restrictions by country.11MIT
- FlicenseNot gradedqualityBmaintenanceCross-chain decentralized Web3 identity protocol. Canonical naming resolvable across all EVM networks via Chainlink CCIP and EIP-3668.-
- AlicenseAqualityBmaintenanceEnables AI assistants and agents to check domain name availability and retrieve available USDT registration quotes through a public read-only domain search API. It does not support automated purchases, account credentials, or registrar actions.1MIT
- AlicenseNot gradedqualityDmaintenanceEnables AI assistants to interact with the Ethereum Name Service via natural language, supporting lookups, availability checks, pricing, subnames, and onchain records.15MIT
TDQS
Scored across 11 tools
Most tools target distinct resources (protocols, apps, assets, names) with different query strategies. Minor overlap exists between get_protocol and get_protocol_summary, and between get_protocol_contracts and get_contract_role, but descriptions clarify their different intents.
Tool names follow a consistent verb_noun pattern (get_protocols, identify_asset, search_assets, resolve_name). Slight inconsistency in that several verbs are used (get, identify, search, resolve, reverse_resolve) but within each verb group the pattern is uniform.
11 tools is well-scoped for a read-only ecosystem registry. Each tool serves a distinct query need without redundancy or bloat.
The tool set covers the core read operations for protocols, contracts, applications, assets, and enVoi names. Minor gaps exist such as no direct 'get all assets' or 'get contract details by ID' beyond role lookup, but the domain is well served overall.