Token Holders API MCP Server

Token Holders API MCP server exists for a simple reason — assistants are far more useful when they can act on Token Holders API directly instead of describing what you should do. Token holder distribution — top holders, whale count, concentration score. x402.

What you get

Token holder distribution -- top holders, concentration %, whale count. On-chain due diligence for agents. Pay-per-call via x402 (USDC on Base L2) -- no API key, no signup, no rate-limit wall.

What the assistant can call

Once Token Holders API is connected, these are the calls the assistant has available:

• token_get_holder_analysis — GET

Setting it up

Setup follows the usual MCP pattern — install or clone the server, register it in your client's configuration file, restart the client. The configuration blocks on this page cover the common clients.

Choosing this one

Plenty of developer tooling servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. Token Holders API's toolset — token_get_holder_analysis — is a fair guide to whether it matches your workflow. It is maintained by Br0ski777; 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.

Before you rely on it

• 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.
• MCP clients confirm each tool call by default. Leave that on until you have watched what the token holders api mcp server does with a few real requests.