get_token_infoLABSCO SUMMARY
Holder-level token analytics, scoped to Ethereum.
Four read-only calls cover the questions people actually ask about a token contract: what is it, who holds it, is that changing, and what else is in that wallet. It is a thin layer over one vendor's API, so the answers are as good as that API's coverage and your key's rate limit.
What it is
A server over the DeAI API for on-chain analytics on Ethereum: token metadata, holder analysis and wallet portfolios.
What you get
- get_token_info returns a token's name, symbol, decimals, logo and transfer tax
- get_top_holders lists who holds a token, with balances and percentages
- get_token_holder_balance_changes tracks how holder balances moved over the past week
- get_portfolio returns a wallet's total value, its change, and the tokens it holds
- Inputs are validated against schemas and requests carry a timeout, so a slow endpoint fails rather than hangs
- Nothing sensitive is logged or stored
Requirements
A DeAI API key, supplied to the server as an environment value. Runs on Node as a local process. Coverage is Ethereum mainnet, and your key's tier sets the request rate and credit budget.
Setup effort
Build from source — git clone https://github.com/decenterailab/deai-api-mcp-server.git
USE CASES
01
Checking a token contract before you touch it
Read the name, symbol, decimals and any transfer tax straight from the contract's record.
02
Seeing how concentrated the holders are
Take the top holders with balances and percentages instead of scrolling a block explorer.
03
Spotting accumulation or distribution
Look at how the largest holders' balances moved over the past week.
04
Sizing up a wallet
Get the total value, the recent change and the holdings behind an address in one call.
4 tools
Listed in project docs. Your client may show a different list.
get_top_holdersget_token_holder_balance_changesget_portfolioBEFORE YOU INSTALL
What to know first
Tools you get
4 tools named in the project's documentation.
Requires
- Node.js 18+
- API_KEY in your environment
Where it runs
The documented client runs the server on your machine.
INSTALLATION
Connect your client
You clone this one yourself.
Server setup
Clone the repository:
TERMINAL
git clone https://github.com/decenterailab/deai-api-mcp-server.git
cd deai-api-mcp-serverInstall dependencies:
TERMINAL
npm installMCP Clients
Claude Desktop
CLAUDE DESKTOP · JSON
{
"mcpServers": {
"deai-api": {
"command": "node",
"args": [
"<YOUR_PATH_TO_DEAI_API_MCP_SERVER>/src/server.js"
],
"env": {
"API_KEY": "<YOUR_API_KEY>"
}
}
}
}
