Skip to main content
Glama

bloxberg-mcp

An MCP (Model Context Protocol) server for the bloxberg blockchain — the permissioned Ethereum-based network operated by 50+ research institutions worldwide.

Connect any MCP-capable AI assistant (Claude Code, Claude Desktop, Cursor, …) to bloxberg: query chain state, explore transactions and contracts, and verify Research Object Certificates (W3C Verifiable Credentials anchored on-chain) — the first MCP server with native support for bloxberg's scientific-data certification stack.

Tools

Tool

What it does

get_network_info

Chain id, latest block, gas price, node version, endpoints

get_block

Block by number, hash, or latest

get_transaction

Transaction + receipt by hash

get_balance

Native BERG balance of an address

read_contract

Call any read-only contract function via a human-readable ABI signature

get_address_transactions

Address tx history (Blockscout explorer, paginated)

get_token_info

ERC-20/721/1155 token metadata (Blockscout)

get_contract_source

Verified contract source + ABI (Blockscout)

inspect_certificate

Parse a Research Object Certificate locally — issuer, subject, proof info

verify_certificate

Full cryptographic verification of a certificate against the chain, using the bloxberg cert-verifier-js engine (MerkleProof2019 replay, on-chain Merkle-root comparison, issuer identity, status)

Related MCP server: blockscout-mcp

Networks

network value

Chain

chainId

RPC

l1 (default)

bloxberg mainnet (Proof-of-Authority)

8995

https://core.bloxberg.org

l2-testnet

bloxberg 2.0 testnet (Arbitrum AnyTrust)

77888

https://explorer.l2.bloxberg.org/rpc

Setup

Requires Node.js ≥ 20.

git clone https://github.com/adi-ghag/bloxberg-mcp.git
cd bloxberg-mcp
npm install && npm run build

Claude Code:

claude mcp add bloxberg -- node /path/to/bloxberg-mcp/dist/index.js

Claude Desktop / generic MCP client (mcpServers config):

{
  "mcpServers": {
    "bloxberg": {
      "command": "node",
      "args": ["/path/to/bloxberg-mcp/dist/index.js"]
    }
  }
}

Then ask your assistant things like:

  • "What's the latest block on bloxberg?"

  • "Read name() from contract 0x787B…4C41 on the bloxberg L2 testnet"

  • "Here's my research certificate JSON — verify it against the chain."

Example: verifying a Research Object Certificate

bloxberg anchors only the Merkle root of a certificate batch on-chain — an individual file hash is never on-chain by itself, so verification requires the full credential document. verify_certificate accepts the credential JSON (inline or by URL) and replays the whole pipeline: format validation → MerkleProof2019 proof replay → on-chain root comparison → issuer identity → status. The result lists every step with its pass/fail status.

Development

npm test           # unit tests (mocked network)
npm run test:live  # + integration tests against real bloxberg endpoints
npx tsx scripts/smoke.mts   # manual end-to-end smoke test

Limitations (v1)

  • Read-only by design: no transaction signing or sending — the server never touches keys.

  • verify_certificate supports credentials anchored on bloxberg L1 (what the published verifier engine knows). Verification of L2-testnet-anchored credentials is experimental and may fail chain lookup.

  • Explorer tools use the Blockscout v1 API (the v2 REST API is disabled on bloxberg's Blockscout instances).

License

MIT © Aditya Ghag

Available Tools

10 tools
get_address_transactionsGet address transactionsA

Transaction history of an address from the Blockscout explorer, newest first. Paginated.

Inputs: address (required), page, network, pageSize.

get_balanceGet balanceA

Native token (BERG) balance of an address, in wei and formatted.

Inputs: address (required), network.

get_blockGet blockA

Fetch a block by number, hash, or "latest". Returns header fields and transaction hashes (or full transactions if requested).

Inputs: block, network, includeTransactions.

get_contract_sourceGet verified contract sourceA

Verified source code, compiler settings, and ABI of a contract from the Blockscout explorer (empty result if the contract is not verified).

Inputs: address (required), network.

get_network_infoGet bloxberg network infoA

Overview of a bloxberg network: chain id, latest block number, gas price, node client version, and public endpoints. Also lists all networks this server knows.

Inputs: network.

get_token_infoGet token infoA

Metadata for an ERC-20/721/1155 token contract (name, symbol, decimals, supply, type) from the Blockscout explorer.

Inputs: address (required), network.

get_transactionGet transactionA

Fetch a transaction and its receipt by hash. The receipt includes status, gas used, and logs.

Inputs: hash (required), network.

inspect_certificateInspect a Research Object CertificateA

Parse a bloxberg Research Object Certificate (W3C Verifiable Credential) WITHOUT verifying it: shows issuer, subject, dates, proof type, and anchoring hints. Purely local — no network calls. Use verify_certificate for cryptographic verification against the chain.

Inputs: url, certificate.

read_contractRead contractA

Call a read-only (view/pure) contract function. Pass the function as a human-readable ABI signature, e.g. "function balanceOf(address) view returns (uint256)" or "function name() view returns (string)". Arguments are passed as strings and coerced by type.

Inputs: address (required), signature (required), args, network.

verify_certificateVerify a Research Object CertificateA

Cryptographically verify a bloxberg Research Object Certificate against the blockchain using the bloxberg cert-verifier engine (@bloxberg-org/cert-verifier-js-bloxberg): format validation, MerkleProof2019 replay, on-chain Merkle root comparison, issuer identity, and status checks. Returns the final verdict plus every verification step. Note: a bare file hash cannot be verified — bloxberg anchors only Merkle batch roots on-chain, so the full credential document is required.

Inputs: url, certificate.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    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

    ActivityInactive
    ResponsivenessOutdated data

    Related MCP Connectors

    Related MCP Servers

    • 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.
      MIT
    • 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.
      53 npm
      MIT