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., "@UluVoiMCP What is the purpose of Voi application 29090?"
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: UluAlgorandMCP
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 |
| 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 |
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
Aramid Bridge — cross-chain bridge
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 the static enVoi name registry by pattern. For live search, use UluCoreMCP's envoi tools.
Inputs: pattern (required).
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
Scored across 10 tools
Each tool has a clearly distinct purpose with no overlap: get_contract_role focuses on contract roles, get_protocol and get_protocol_summary provide different levels of protocol detail, get_protocol_contracts lists contracts, get_protocols lists protocols, identify_application and identify_asset handle different resource types, and the name tools (resolve_name, reverse_resolve_address, search_names) are clearly scoped to static registry operations. An agent can easily distinguish between them based on their specific targets.
All tools follow a consistent verb_noun pattern with snake_case, using verbs like 'get', 'identify', 'resolve', 'reverse_resolve', and 'search' paired with specific nouns (e.g., contract_role, protocol, protocols, application, asset, name, address). This predictability makes it easy for an agent to understand the action and target from the name alone.
With 10 tools, the count is well-scoped for the domain of Voi ecosystem information and static name registry operations. Each tool serves a unique function, covering protocol discovery, contract details, asset/application identification, and name resolution without redundancy, making the set efficient and focused.
The tool set provides comprehensive coverage for querying Voi protocols, contracts, assets, applications, and static name registry data, with clear CRUD-like operations (e.g., get, list, identify, resolve). A minor gap exists as the server defers live name resolution to another MCP server (UluCoreMCP), but this is explicitly noted and does not hinder core functionality, allowing agents to work around it.
MCP server connecting AI agents to non-custodial staking data across 130+ networks.
Hosted MCP server for live Bittensor chain reads and self-custodial on-chain writes.
Hosted MCP server for AI-driven data ops. Create apps, manage schemas, and CRUD structured data.
Capability registry for the agentic economy. Semantic search over verified MCP server listings.