A Model Context Protocol (MCP) server for querying data from 48 blockchains using 3xpl.com blockchain explorer JSON API
A Model Context Protocol (MCP) server for querying data from 48 blockchains using 3xpl.com blockchain explorer JSON API. The 3xpl.com json api mcp server wraps that behind the Model Context Protocol, so an assistant can use it through 14 defined tools rather than through you.
This repository can also be an example of 3xpl JSON API usage, see details in the code.
Everything the assistant can do here goes through one of these:
resolve_ens_domain — resolves an ENS domain to a regular addressdetect_blockchains — retrieve a list of blockchains on which a transaction/address is presentget_latest_block — get latest block height in specified blockchainget_average_fee_24h_usd — retrieves average transaction fee for last 24 hours in specified blockchain in US dollarsget_mempool_events_count — get the number of unconfirmed events(transfers, inputs/outputs, not transactions) at the moment in the memory pool of provided blockchainget_events_count_24h — retrieve number of events(transfers, inputs/outputs, not whole transactions) in last 24h for provided blockchainget_block_overview — extract short summary about a block in provided blockchainget_address_overview — extract short summary about an address in provided blockchainget_transaction_overview — extract short summary about a transaction in provided blockchain(to be improved)list_blockchains_and_modules — get a list of blockchains and their modules with module descriptionsaggregate_block_transactions — aggregate transactions in a blockaggregate_transaction_transfers — aggregate individual transfers in a transactionsYou will need one environment variable: THREEXPL_API_KEY. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.
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.
Among the knowledge and memory options, the useful question is rarely "what can it do" but "what does it cost you to run" — permissions, credentials, and how much of your context its toolset consumes. 3xpl.Com JSON API's toolset — resolve_ens_domain, detect_blockchains, get_latest_block and 11 more — is a fair guide to whether it matches your workflow. It is maintained by exekerey; worth a glance at recent repository activity before you build anything load-bearing on it.
This entry was verified against 3xpl.Com JSON API's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.
| Tool | What it does |
|---|---|
| resolve_ens_domain | resolves an ENS domain to a regular address |
| detect_blockchains | retrieve a list of blockchains on which a transaction/address is present |
| get_latest_block | get latest block height in specified blockchain |
| get_average_fee_24h_usd | retrieves average transaction fee for last 24 hours in specified blockchain in US dollars. |
| get_mempool_events_count | get the number of unconfirmed events(transfers, inputs/outputs, not transactions) at the moment in the memory pool of provided blockchain |
| get_events_count_24h | retrieve number of events(transfers, inputs/outputs, not whole transactions) in last 24h for provided blockchain |
| get_block_overview | extract short summary about a block in provided blockchain |
| get_address_overview | extract short summary about an address in provided blockchain |
| get_transaction_overview | extract short summary about a transaction in provided blockchain(to be improved) |
| list_blockchains_and_modules | get a list of blockchains and their modules with module descriptions |
| aggregate_block_transactions | aggregate transactions in a block |
| aggregate_transaction_transfers | aggregate individual transfers in a transactions |
| aggregate_address_balances | aggregate balances for an address with |
| aggregate_address_transactions | aggregate confirmed transactions for an address |
MCP configuration:
```json
{
"mcpServers": {
"3xpl_API": {
"command": "uv",
"args": [
"run",
"--with",
"mcp[cli]",
"mcp",
"run",
"{:path_to_cloned}/3xpl_mcp/main.py"
],
"env": {
"THREEXPL_API_KEY": ""
}
}
}
}Configuration as documented by the project. Restart the client after saving.
| Variable | Description | Required |
|---|---|---|
| THREEXPL_API_KEY | Credential the server authenticates with. | Yes |
A knowledge graph your assistant keeps between sessions — entities, relations and observations that persist.
Kill hallucinated APIs — version-accurate, up-to-date library documentation injected straight into context.
Your workspace, on speaking terms with AI — search, read and write Notion pages and databases.
A structured scratchpad for hard problems — stepwise reasoning with revisions, branches and visible logic.
Symbol-level code navigation, refactoring and memory for coding agents — the IDE brain your assistant has been missing.
Chat with your second brain — search, read and write vault notes through the Local REST API.