Deai Api MCP Server

Most developer tooling work still happens through a UI a human drives. Deai Api MCP server moves it into the conversation instead. MCP server for DeAI API - provides ethereum token information/holders/portfolio/balance changes/top holders/ details.

The short version

A Model Context Protocol (MCP) server that provides tools to interact with the DeAI API for token analysis, holder tracking, and wallet portfolio analytics on Ethereum.

• get_token_info — - Get detailed token information including name, symbol, decimals, logo, and token tax
• get_top_holders — - Analyze the holders of any token with their balances and percentages
• get_token_holder_balance_changes — - Track balance changes for token holders over the last 7 days
• get_portfolio — - Get comprehensive portfolio data for any wallet including total value, changes, and token holdings

The tools it exposes

The server publishes 2 tools. What each one is for:

• Prerequisites — The Prerequisites tool exposed by this server
• Installation — 1. Clone the repository: bash git clone https://github.com/decenterailab/deai-api-mcp-server.git cd deai-api-mcp-server

What it needs from you

Configuration is passed through the environment: API_KEY. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.

• Node.js 18+ - DeAI API key - Get one at https://t.me/DeCenterAIDev

Getting it running

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

How it compares

This sits in the developer tooling group, where several servers overlap in what they claim to do but differ sharply once you actually set them up. Deai Api's toolset — Prerequisites, Installation — is a fair guide to whether it matches your workflow. It is maintained by decenterailab; 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.

Things to watch

• 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.
• Keep per-call confirmation enabled while you learn its behaviour; it is the cheapest safeguard you have.