ChainFETCH MCP Server
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| CHAINFETCH_API_TOKEN | Yes | Your ChainFETCH API token from chainfetch.app |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_addresses_semanticC | Semantic search for Ethereum addresses using AI-powered vector similarity matching |
| search_addresses_jsonB | JSON search for addresses with 150+ parameters for comprehensive filtering |
| search_addresses_llmC | LLM-powered address search using LLaMA 3.2 3B to intelligently select from 150+ parameters |
| get_address_summaryC | Get AI-generated summary for a specific address |
| get_address_infoB | Get detailed information about a specific Ethereum address |
| search_transactions_semanticC | Semantic search for transactions using AI-powered vector similarity matching |
| search_transactions_jsonC | JSON search for transactions with 254+ carefully curated parameters |
| search_transactions_llmC | LLM-powered transaction search using LLaMA 3.2 3B to select from 254 parameters |
| get_transaction_summaryC | Get AI-generated summary for a specific transaction |
| get_transaction_infoC | Get detailed information about a specific transaction |
| search_blocks_semanticB | Semantic search for blocks using AI-powered vector similarity matching |
| search_blocks_jsonD | JSON search for blocks with 120+ parameters |
| search_blocks_llmC | LLM-powered block search using LLaMA 3.2 3B to select from 120+ parameters |
| get_block_summaryC | Get AI-generated summary for a specific block |
| get_block_infoC | Get detailed information about a specific block |
| search_tokens_semanticC | Semantic search for tokens using AI-powered vector similarity matching |
| search_tokens_jsonC | JSON search for tokens with comprehensive search parameters |
| search_tokens_llmC | LLM-powered token search using AI to select optimal parameters |
| get_token_summaryC | Get AI-generated summary for a specific token |
| get_token_infoC | Get detailed information about a specific token |
| get_nft_instance_infoC | Get NFT instance information |
| search_smart_contracts_semanticC | Semantic search for smart contracts using AI-powered vector similarity matching |
| search_smart_contracts_jsonD | JSON search for smart contracts with 50+ parameters |
| search_smart_contracts_llmC | LLM-powered smart contract search using AI to select from 150+ parameters |
| get_smart_contract_summaryC | Get AI-generated summary for a specific smart contract |
| get_smart_contract_infoC | Get detailed information about a specific smart contract |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 26 tools
The tools are organized by resource type (address, block, NFT, smart contract, token, transaction) and action (get_info, get_summary, search), which provides clear distinctions. However, the three search methods (JSON, LLM, semantic) for each resource create some potential confusion about which search tool to use for a given query, as their purposes overlap significantly despite different interfaces.
Tool names follow a highly consistent verb_noun pattern throughout: get_<resource>_info, get_<resource>_summary, search_<resource>_json, search_<resource>_llm, search_<resource>_semantic. The naming is systematic and predictable across all 26 tools, making it easy to understand the pattern and locate specific tools.
With 26 tools, the count feels excessive for a blockchain data server. While the domain is broad, having three nearly identical search methods (JSON, LLM, semantic) for each of five resource types creates significant redundancy. A more streamlined approach with fewer overlapping tools would improve coherence without losing functionality.
The tool set provides comprehensive coverage for blockchain data exploration. Each major resource type (address, block, smart contract, token, transaction) has both detailed information retrieval and AI-generated summaries, plus multiple search approaches. The inclusion of NFT instance information adds additional domain coverage, creating a complete surface for blockchain data analysis.