That focus is what makes it useful: instead of a broad chain toolkit, you get the numbers people actually ask about — where liquidity sits, what a pool is composed of, how an asset has traded. The setup is the rough edge. It wants a Node version newer than most machines have, it is a clone-and-build rather than a package install, and the example config carries a mnemonic that must not survive into your own. Fix that field first and the rest is straightforward.
An MCP server over the Vestige API, giving an assistant access to DeFi analytics across the Algorand ecosystem. It was distilled from the broader Algorand MCP project and narrowed to the analytics side: protocols, assets, pools, trading and network state.
- Network status, statistics and synchronisation state
- Protocol analytics across the major Algorand DeFi protocols, including total value locked and activity
- Asset data: prices and history, volume and liquidity metrics, market capitalisation and composition
- Trading data: real-time swap monitoring, historical trades, price candles and order book depth
- Pool analytics: composition, volume, TVL and historical pool data
- Vault statistics, balance tracking, transaction monitoring and market notes
Node.js 23.6.1 or later — check with `node -v` and upgrade first, since this is newer than most systems ship. Clone the repository into your client's server folder, `npm install`, `npm run build`, then point the client's command at node and the built server entry point. Configuration is environment values in the client entry: the Algorand network and node endpoints, the Vestige API URL and key, an items-per-page setting, and an agent wallet. One thing to change before you run anything: the sample configuration in the README ships a wallet mnemonic in plain text — replace it with your own value, and treat that field as the secret it is. MIT licensed.
Build from source — clone the repository and build it, then point your client at the binary