bloxberg-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_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. |
| get_blockA | Fetch a block by number, hash, or "latest". Returns header fields and transaction hashes (or full transactions if requested). |
| get_transactionA | Fetch a transaction and its receipt by hash. The receipt includes status, gas used, and logs. |
| get_balanceA | Native token (BERG) balance of an address, in wei and formatted. |
| read_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. |
| get_address_transactionsA | Transaction history of an address from the Blockscout explorer, newest first. Paginated. |
| get_token_infoA | Metadata for an ERC-20/721/1155 token contract (name, symbol, decimals, supply, type) from the Blockscout explorer. |
| get_contract_sourceA | Verified source code, compiler settings, and ABI of a contract from the Blockscout explorer (empty result if the contract is not verified). |
| inspect_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. |
| verify_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. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
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.