Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type @ followed by the MCP server name and your instructions, e.g., "@ulu-voi-mcp what is HumbleSwap?"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
Voi ecosystem MCP server. Returns meaning, not raw chain data.
UluCoreMCP → chain primitives (blocks, accounts, transactions)
UluVoiMCP → Voi ecosystem meaning (protocols, identity, naming)
UluWalletMCP → signing
UluBroadcastMCP → broadcastingCore returns facts. Voi returns meaning.
Related MCP server: ENS MCP Server
Tool | Description |
| List all known Voi protocols, optionally filtered by type |
| Get detailed info about a specific protocol |
| List all contracts and assets for a protocol |
| Human-readable protocol summary |
| Identify what a Voi application ID is |
| Identify what a Voi asset ID is |
| Search known assets by symbol, category, protocol, or verified status |
| Get the role and purpose of a contract |
| Resolve an enVoi name from static registry |
| Reverse-resolve an address to known names |
| Search the name registry by pattern (with result limit) |
Curated registry files in data/:
protocols.json — protocol definitions (HumbleSwap, Nomadex, enVoi, Aramid, etc.)
applications.json — application ID → protocol, role, type mapping
assets.json — asset ID → name, symbol, category, protocol mapping
names.json — static well-known enVoi names
All registries are static JSON loaded at startup. For live data, use UluCoreMCP.
npm installnode index.js{
"mcpServers": {
"ulu-voi-mcp": {
"command": "node",
"args": ["/absolute/path/to/ulu-voi-mcp/index.js"]
}
}
}HumbleSwap — DEX (AMM pools)
Nomadex — DEX
SnowballSwap — DEX aggregator
enVoi — naming service
Nautilus — NFT marketplace
HighForge — NFT minting
DorkFi — lending protocol (deposits, borrowing, liquidations, WAD stablecoin)
Aramid Bridge — cross-chain bridge
NFT Navigator (Mimir) — indexer (ARC-200 tokens, ARC-72 NFTs, marketplace, DEX pools)
Kibisis — browser wallet
Voi Network — L1 blockchain
Static registry approach. The names.json file contains well-known enVoi names. For live resolution (on-chain lookups), use UluCoreMCP's envoi_resolve_address, envoi_resolve_name, and envoi_search tools.
Registries are static and curated — not all applications or assets are covered
Name resolution is from a static registry, not live on-chain lookups
No write operations — this is a read-only meaning layer
Pool list may become stale as new pools are created
Community tokens marked unverified may change status
Get the role and purpose of a specific contract on Voi (e.g. liquidity-pool, bridge, registry)
Inputs: appId (required).
Get detailed information about a specific Voi ecosystem protocol by ID
Inputs: protocolId (required).
List all known application contracts for a Voi protocol
Inputs: protocolId (required).
List all known Voi ecosystem protocols with type and description
Inputs: type.
Get a human-readable summary of a Voi protocol including its purpose, contracts, and assets
Inputs: protocolId (required).
Identify a Voi application by ID — returns protocol, role, type, and description if known
Inputs: appId (required).
Identify a Voi asset by ID — returns name, symbol, type, protocol, and category if known
Inputs: assetId (required).
Resolve an enVoi name (e.g. 'shelly.voi') to its address and metadata from the static registry. For live resolution, use UluCoreMCP's envoi tools.
Inputs: name (required).
Look up well-known enVoi names associated with a Voi address from the static registry. For live resolution, use UluCoreMCP's envoi tools.
Inputs: address (required).
Search known Voi assets by symbol, category, or protocol
Inputs: symbol, category, protocol, verified.
Search the static enVoi name registry by pattern. For live search, use UluCoreMCP's envoi tools.
Inputs: pattern (required), limit.
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
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.
Read-only lookup of verified crypto wallet addresses for domains, .cns and ENS names.
Discovery for the agent ecosystem: findable businesses, tools, knowledge, agent spaces, skills.
Machine-readable entity discovery with provenance, trust and verified source evidence.
Search VeChain documentation, query on-chain data, and fetch fee suggestions with direct links to…