coingecko-dataLABSCO SUMMARY
Token research runs as a plan with state, not as a pile of one-off lookups.
The shape here is a workflow: a plan is created for a token, its sections carry a status, and findings accumulate as resources the session can list back. CoinGecko and DefiLlama are addressed by name rather than through a generic fetch, so the two places most token questions end up are each one call away. The tools ship without descriptions, so a client has to choose between them on their names and argument lists alone — which is workable for a set this literally named, and a real cost when two of them differ only in scope.
What it is
A token-research workflow server keyed on a token name and ticker, with CoinGecko and DefiLlama addressed as named sources and a plan whose sections carry a status.
What you get
- A research plan created from a token's name and ticker, with per-section status maintained through update-status
- CoinGecko reached three ways — a name lookup, a data pull for the token, and a ticker listing bounded by limit
- DefiLlama as the second named source, by search and by token
- Source-scoped work: search-source and research-source both take a source alongside the token, so a question can be aimed at one place instead of the open web
- A second pass driven by terms rather than the plan, through research-with-keywords
- Page content fetched by URL in a chosen format, and list-resources for what the session has accumulated
Requirements
The token's name and its ticker, since nearly every tool keys on both. No account or key is declared, and the two sources the tools name are CoinGecko and DefiLlama.
Setup effort
One command — npx -y web3-research-mcp@latest
USE CASES
01
Writing a token report from scratch
Create the plan for the token, work each section against a named source, mark sections as they close, and list what the session has gathered when it is time to write.
02
Getting market data for a ticker
Resolve the token on CoinGecko first, since name and ticker are what the other calls key on, then pull its data and the ticker listings behind it.
03
Checking a protocol's on-chain footprint
Find the protocol on DefiLlama by name, then pull its data as the second source alongside whatever the market pages say.
04
Chasing a claim back to the page it came from
Search for the claim, fetch the page it points at in the format you want to keep, and run a second pass with the terms that page introduced.
13 tools
Counted once with only startup setup. Other versions, modes or optional credentials may expose a different list.
coingecko-searchcoingecko-tickerscreate-research-plandefillama-datadefillama-searchfetch-contentlist-resourcesresearch-sourceresearch-with-keywordssearchsearch-sourceupdate-statusBEFORE YOU INSTALL
What to know first
Tools you get
13 tools when we connected.
Requires
- npx on PATH
- Node.js
CONTEXT COST
Light Standing cost
Rated by the size of the 13 tool definitions that ride along on every turn, not by how many there are
INSTALLATION
Connect your client
Add the block to your client, or run the command directly.
Server setup
Configuration file
JSON
{
"mcpServers": {
"web3-research-mcp": {
"command": "npx",
"args": [
"-y",
"web3-research-mcp@latest"
]
}
}
}npx
TERMINAL
npx -y web3-research-mcp@latest
