Vestige MCP Server

Vestige Model Context Protocol Implementation. The vestige mcp mcp server wraps that behind the Model Context Protocol, so an assistant can use it through 1 defined tool rather than through you.

What it actually does

A Model Context Protocol (MCP) server implementation for interacting with the Vestige API, providing comprehensive DeFi analytics and data access for the Algorand ecosystem.

Vestige MCP serves as a bridge between MCP-enabled applications and the Vestige API, offering tools to access: - Network information and statistics - Protocol analytics (Tinyman, Pact, Algofi, etc.) - Asset data and price information - Pool analytics and liquidity information - Vault statistics - Balance tracking - Transaction monitoring - Market notes and annotations

Its toolset

Everything the assistant can do here goes through one of these:

• Real — time swap monitoring

Adding it to your client

Setup follows the usual MCP pattern — install or clone the server, register it in your client's configuration file, restart the client.

Configuration

You will need 8 environment variables: ALGORAND_NETWORK, ALGORAND_ALGOD_API, ALGORAND_ALGOD, ALGORAND_ALGOD_PORT, ALGORAND_TOKEN, ALGORAND_AGENT_WALLET, VESTIGE_API_URL, VESTIGE_API_KEY. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.

When to reach for it

This sits in the monitoring and observability group, where several servers overlap in what they claim to do but differ sharply once you actually set them up. Vestige MCP's toolset — Real — is a fair guide to whether it matches your workflow. It is maintained by GoPlausible; worth a glance at recent repository activity before you build anything load-bearing on it.

We check each listing at SyncDev against the project's documentation before it goes live — if something here drifts out of date, it is a bug worth reporting.

Caveats

• It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
• Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
• MCP clients confirm each tool call by default. Leave that on until you have watched what the vestige mcp mcp server does with a few real requests.