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., "@Vitruveo Chain Tools MCP check the latest Vitruveo block and network status"
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.
Read-only Vitruveo mainnet tools, chain ID 1490. Release candidate 0.2.0-rc.1. One existing viem-based core serves standard stdio and authenticated Streamable HTTP. No wallet, signing, broadcasts or contract writes. Not an independent security audit.
Node.js 22+. Extract the reviewed source archive to a stable folder.
Windows: npm.cmd ci --ignore-scripts, npm.cmd test. macOS/Linux: npm ci --ignore-scripts, npm test.
Configure your client to run node /absolute/path/src/stdio.js. It launches the server;
no separate HTTP process is required. Standard output is reserved for MCP messages.
The 16 tools cover network status, balances, blocks/receipts, history pages, view calls, event decoding, bounded scans, ERC-20/ERC-721 probes, ABI/proxy observations, logs, block-author observations, supply arithmetic and historical-data point probes.
Default RPC: https://rpc.vitruveo.ai; explorer: https://explorer.vitruveo.ai. The live release smoke checked only network status and explorer availability. All 16 tools were invoked through stdio and authenticated local HTTP against fixtures. Automated tests use local mock providers. GUI clients and hosted ChatGPT connections have not been tested; the compatibility table distinguishes preparation from verification.
Historical calls or minted/outstanding shares are not paid sales. Missing original records and provider retention limits must remain explicit. Never present capped scans as complete. URI/ABI/explorer data is untrusted, and metadata URLs are never fetched.
Optional HTTP: see installation documentation. Loopback requires a private token; remote binding additionally requires HTTPS/OAuth/JWKS configuration. This package does not provide hosting, accounts or an authorization server. Nothing was deployed.
MIT source license; installed dependency declarations and advisory results accompany the candidate. Source archives exclude dependencies and private investigation material. Independent community utility; no claim of Vitruveo Foundation endorsement.
Read one Blockscout page with exact pagination cursor (transactions, logs, transfers, token holdings, internal transactions).
Inputs: address (required), kind, filters, pageCursor.
Native VTRU balance, contract status, explorer metadata including NFTs and proxy info.
Inputs: address (required).
Read a block by number or latest.
Inputs: number.
Verify chain ID, RPC health, and current block.
Inputs: no named parameters.
Observe bytecode, EIP-1967 proxy slots and explorer ABI metadata.
Inputs: address (required), blockNumber.
Read at most 2000 blocks and 500 log records; explicit completeness.
Inputs: address (required), toBlock (required), fromBlock (required), topic, +1 more.
Decode raw event log entries with a supplied Solidity event signature.
Inputs: logs (required), eventSignature (required).
Point probes of historical block and state; never proof of complete archive coverage.
Inputs: address, blockNumber.
Native VTRU balance at a pinned block.
Inputs: address (required), blockNumber.
Read ERC-721 ownership and URI without fetching external metadata.
Inputs: address (required), tokenId (required), blockNumber.
Call any ABI-described view or pure method on an arbitrary contract, including proxies. No wallet signing.
Inputs: abi (required), address (required), functionName (required), args, +1 more.
Read caller-selected cap/outstanding/reserved getters at one block; never a paid-sales total.
Inputs: address (required), capFunction (required), reservedFunction (required), outstandingFunction (required), +1 more.
Paginate public address incoming/outgoing transactions, group decoded methods, optionally sum uint quantity for one method, and flag incomplete runs. NOT proof of sales.
Inputs: address (required), filter, maxPages, maxRecords, +2 more.
Read ERC-20 interface information and optional holder balance.
Inputs: address (required), holder, blockNumber.
Read transaction, receipt and Blockscout decoding by transaction hash.
Inputs: hash (required).
Sample block author fields; not proof of validator membership.
Inputs: sampleBlocks.
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
Scored across 16 tools
Several tools overlap: address_overview and native_balance both return native balance, address_history_page and scan_address_transactions both traverse address transactions, and contract_logs/decode_event_logs/historical_availability all touch logs or historical state. Descriptions add caveats and pinned-block distinctions, but an agent must read carefully to choose correctly.
All names use snake_case, which is consistent, but the convention is split between noun phrases (chain_status, block_details, token_info) and verb phrases (read_contract, decode_event_logs, scan_address_transactions). The mixed style remains readable but is not a single predictable pattern.
16 tools is slightly above the typical 3-15 range but reasonable for a read-only chain inspection and analysis surface. Each tool maps to a specific query type, though a few overlaps suggest some could be consolidated.
The surface covers core read-only chain workflows: status, blocks, transactions, addresses, contracts, logs, tokens, NFTs, validators, supply reconciliation, and historical probes. Minor gaps remain around gas estimation, broad event/topic filtering, and richer token/NFT enumeration, but no major dead ends for the stated purpose.
Read EVM and Solana chains for balances, tokens, eth_call, logs, receipts, gas, blocks and ENS.
Read chain data on 200+ networks and Sui: transactions, logs, balances, objects, ABI-decoded.
Read-only market and on-chain data for Bitcoin, Ethereum and more; on-chain from our own nodes.
Read-only KAI network overview, standards, fees, public terms, and developer onboarding.
