Vitruveo Chain Tools MCP
# Vitruveo Chain Tools MCP
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.
## Install locally
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.
- [Installation and compatibility matrix](docs/INSTALLATION.md)
- [Tool reference and evidence limitations](docs/TOOLS.md)
- [Security and read-only policy](SECURITY.md)
- [Release, license and dependency review](docs/RELEASE-REVIEW.md)
- [Release notes](CHANGELOG.md)
- [VS Code example](examples/vscode.mcp.json)
- [Cursor example](examples/cursor.mcp.json)
- [Claude Desktop example](examples/claude-desktop.json)
- [Codex example](examples/codex-config.toml)
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.
TDQS
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.