bloxberg-mcp
Related Servers
Alternatives to bloxberg-mcp
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityDmaintenanceEnables AI models to interact with Blockscout API for blockchain data, including transactions, blocks, balances, and contract calls. Supports multiple endpoints for comprehensive blockchain exploration.4-
- AlicenseNot gradedqualityDmaintenanceEnables AI assistants to query on-chain data across EVM chains like Base, Optimism, Avalanche, Celo, and Arbitrum, including balances, transactions, gas, and smart contract interactions.27 npmMIT
- AlicenseNot gradedqualityAmaintenanceMulti-provider blockchain explorer toolkit for AI agents — query wallets, transactions, tokens, contracts and logs across Etherscan, Blockscout, Routescan and BSC providers through one consistent API.3,984 PyPI4MIT
- AlicenseNot gradedqualityDmaintenanceProvides tools for AI assistants to query the Canton Network for data on contracts, governance, validators, and party transactions through the Lighthouse Explorer API. It enables seamless interaction with blockchain statistics, price history, and name services without requiring an API key.132 npmMIT
- AlicenseNot gradedqualityAmaintenanceEnables AI assistants to access live blockchain data across multiple networks, including wallet holdings, payment verification, token prices, swaps, and scam checks.MIT
- FlicenseNot gradedqualityDmaintenanceProvides AI agents with 71 tools to query Etherscan's blockchain analytics via the Etherscan API, with no authentication required.-
TDQS
Scored across 10 tools
The set is highly organized: blocks, transactions, addresses, contracts, token metadata, and certificates each have a distinguishable tool. The only near-overlap is between inspect_certificate and verify_certificate, but the descriptions explicitly separate 'parse without verifying' from 'cryptographically verify', so an agent can choose correctly.
Most tools follow a get_<resource> pattern such as get_block, get_transaction, and get_network_info. read_contract, inspect_certificate, and verify_certificate are verb exceptions, but they are consistent snake_case action-resource names and are semantically clear.
Ten is a well-sccoped number for a blockchain/certificate-oriented MCP server. One can use at get_network_info to certificates, every tool covers a meaningful, non-redundant task.
The read-only blockchain exploration surface is essentially complete: network metadata, block, transaction, address his, balances, contract reading, source/ABI metadata, and token metadata. Certificate iteration is also well covered with both insp and cryptoss verification. There is no write/send-transaction path, but that is consistent with the server's read-only and verification-focused purpose.