Blockscout MCP Server vs Gate DEX MCP
A side-by-side look at the Blockscout MCP Server and Gate DEX MCP MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Blockscout MCP Server for finance & fintech work over a hosted endpoint; choose Gate DEX MCP for finance & fintech as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Blockscout MCP Server when
- You need dedicated capabilities in the Finance & Fintech domain.
- You prefer a remote HTTP/SSE transport.
- You want tools like
__unlock_blockchain_analysis__, get_block_info, get_block_number.
Choose Gate DEX MCP when
- You need dedicated capabilities in the Finance & Fintech domain.
- You prefer a local stdio subprocess transport.
- You want tools like
dex_auth_google_login_start, dex_auth_google_login_poll, dex_auth_login_google_wallet.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Finance & Fintech | Finance & Fintech |
| Quality signal | 61/100 · Good | 59/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Remote HTTP/SSE | Local subprocess (stdio) |
| Auth | Not declared | Not declared |
| Pricing | Not declared | Not declared |
| Required env vars | None listed | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 46 | 44 |
| Directory activity | 1 views 0 installs 0 upvotes | 1 views 0 installs 0 upvotes |
| Tools | 16 | 33 |
| Full listing | View Blockscout MCP Server | View Gate DEX MCP |
Tools & capabilities
Blockscout MCP Server tools 16
__unlock_blockchain_analysis__Initializes a Blockscout MCP session: returns server reference data, the `blockscout-analysis` skill pointer, and the URI resolution rule. Call this tool exactly once per session, before any other tool, and reuse its payload for the rest of the session; do not call it again.get_block_infoGet block information like timestamp, gas used, burnt fees, transaction count etc. Can optionally include the list of transaction hashes contained in the block. Transaction hashes are omitted by default; request them only when you truly need them, because on high-traffic chains the list may exhaust the context.get_block_numberRetrieves the block number and timestamp for a specific date/time or the latest block. Use when you need a block height for a specific point in time (e.g., "block at 2024-01-01") or the current chain tip. If `datetime` is provided, finds the block immediately preceding that time. If omitted, returns the latest indexed block.get_address_by_ens_nameUseful for when you need to convert an ENS domain name (e.g. "blockscout.eth") to its corresponding Ethereum address.get_transactions_by_addressRetrieves native currency transfers and smart contract interactions (calls, internal txs) for an address. **EXCLUDES TOKEN TRANSFERS**: Filters out direct token balance changes (ERC-20, etc.). You'll see calls *to* token contracts, but not the `Transfer` events. For token history, use `get_token_transfers_by_address`. A single tx can have multiple records from internal calls. Requires an `age_from` date to scope results for performance and relevance. **SUPPORTS PAGINATION**: If response includes 'pagination' field, use the provided next_call to get additional pages.get_token_transfers_by_addressGet ERC-20 token transfers for an address within a specific time range. **SUPPORTS PAGINATION**: If response includes 'pagination' field, use the provided next_call to get additional pages.lookup_token_by_symbolSearch for token addresses by symbol or name. Returns multiple potential matches based on symbol or token name similarity. Only the first 7 matches from the Blockscout API are returned.get_contract_abiGet smart contract ABI (Application Binary Interface). An ABI defines all functions, events, their parameters, and return types. The ABI is required to format function calls or interpret contract data.inspect_contract_codeInspects a verified contract's source code or metadata.read_contractCalls a smart contract function (view/pure, or non-view/pure simulated via eth_call) and returns the decoded result. This tool provides a direct way to query the state of a smart contract. Example: To check the USDT balance of an address on Ethereum Mainnet, you would use the following arguments: { "tool_name": "read_contract", "params": { "chain_id": "1", "address": "0xdAC17F958D2ee523a2206206994597C13D831ec7", "abi": { "constant": true, "inputs": [{"name": "_owner", "type": "address"}], "name": "balanceOf", "outputs": [{"name": "balance", "type": "uint256"}], "payable": false, "stateMutability": "view", "type": "function" }, "function_name": "balanceOf", "args": "["0xF977814e90dA44bFA03b6295A0616a897441aceC"]" } }get_address_infoGet comprehensive information about an address, including: - Address existence check - Native token (ETH) balance (provided as is, without adjusting by decimals) - First transaction details (block number and timestamp) for age calculation - ENS name association (if any) - Contract status (whether the address is a contract, whether it is verified) - Proxy contract information (if applicable): determines if a smart contract is a proxy contract (which forwards calls to implementation contracts), including proxy type and implementation addresses - Token details (if the contract is a token): name, symbol, decimals, total supply, etc. Essential for address analysis, contract investigation, token research, and DeFi protocol analysis.get_tokens_by_addressGet comprehensive ERC20 token holdings for an address with enriched metadata and market data. Returns detailed token information including contract details (name, symbol, decimals), market metrics (exchange rate, market cap, volume), holders count, and actual balance (provided as is, without adjusting by decimals). Essential for portfolio analysis, wallet auditing, and DeFi position tracking. **SUPPORTS PAGINATION**: If response includes 'pagination' field, use the provided next_call to get additional pages.- +4 more on the listing page
Gate DEX MCP tools 33
dex_auth_google_login_startStart Google OAuth login flow, returns verification URLdex_auth_google_login_pollPoll login status, returns mcp_token on successdex_auth_login_google_walletLogin with Google OAuth authorization codedex_auth_gate_login_startStart Gate OAuth login flow, returns verification URLdex_auth_gate_login_pollPoll Gate OAuth login status, returns mcp_token on successdex_auth_login_gate_walletLogin directly with Gate OAuth authorization codedex_auth_logoutRevoke current sessiondex_wallet_get_addressesGet wallet addresses for each chain (EVM, Solana)dex_wallet_get_token_listToken balances with prices and paginationdex_wallet_get_total_assetTotal portfolio value and 24h changedex_wallet_sign_messageSign a message with wallet private key (EVM / Solana)dex_wallet_sign_transactionSign a raw transaction with wallet private key- +21 more on the listing page
Ready-to-paste client configs
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
Blockscout MCP Server
{
"mcpServers": {
"blockscout-mcp-server": {
"url": "https://mcp.blockscout.com/mcp"
}
}
}
Gate DEX MCP
{
"mcpServers": {
"gate-dex-mcp": {
"command": "npx",
"args": [
"-y",
"mcporter"
]
}
}
}
Frequently asked questions
Blockscout MCP Server is categorized under Finance & Fintech and uses a remote HTTP/SSE transport. Gate DEX MCP belongs to Finance & Fintech and uses a local stdio subprocess. Pick Blockscout MCP Server for finance & fintech work and Gate DEX MCP for finance & fintech.
Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.
Blockscout MCP Server has no declared pricing — check the project's own site. Gate DEX MCP has no declared pricing — check the project's own site. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add blockscout-mcp-server and gate-dex-mcp as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Blockscout MCP Server has a quality signal of 61/100 (Good) with 1 views, 0 installs and 46 GitHub stars. Gate DEX MCP has 59/100 (Good) with 1 views, 0 installs and 44 GitHub stars.