Skip to main content
Glama

Related Servers

Alternatives to bloxberg-mcp

No user-submitted related servers found.

    Related Servers

    • F
      license
      Not graded
      quality
      D
      maintenance
      Enables 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
      -
    • A
      license
      Not graded
      quality
      D
      maintenance
      Enables 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.
      24 npm
      MIT
    • A
      license
      Not graded
      quality
      A
      maintenance
      Multi-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.
      4
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      Provides 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.
      282 npm
      MIT
    • F
      license
      Not graded
      quality
      D
      maintenance
      Enables comprehensive blockchain data analysis and exploration through the BlockScout API. Provides 56+ tools for transaction analysis, address exploration, token management, smart contract analysis, and market research across multiple blockchain networks.
      -

    TDQS

    A4.1/5.0

    Scored across 10 tools

    Disambiguation4/5

    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.

    Naming Consistency4/5

    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.

    Tool Count5/5

    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.

    Completeness5/5

    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.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues