RSK MCP Server - Rootstock Blockchain Tools
OfficialServer 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 |
|---|---|
| start-interactionC | Start interaction with the Rootstock CLI functions, start this once someone ask something related to the rootstock (rsk) blockchain |
| start-wallet-interactionC | Start wallet management interaction. This shows all available wallet operations and management options. |
| list-pending-operationsA | List all pending operations that require user confirmation |
| confirm-operationB | Confirm and execute a pending operation |
| cancel-operationB | Cancel a pending operation |
| create-walletC | Create a new wallet based on the selected option. This function will ask for required information step by step. |
| check-balanceB | Check the balance of a wallet for RBTC or ERC20 tokens on Rootstock blockchain. You can either use an existing wallet file or provide wallet data directly. |
| use-wallet-from-creationB | Use wallet data directly from a previous wallet creation result. This helps avoid re-uploading files. |
| check-transactionA | Check the status and details of a transaction on Rootstock blockchain using the transaction hash |
| deploy-contractB | Deploy a smart contract to the Rootstock blockchain using ABI and bytecode |
| verify-contractB | Verify a smart contract on the Rootstock blockchain using source code and compilation metadata |
| read-contractA | Read data from a verified smart contract on the Rootstock blockchain by calling view/pure functions |
| transfer-tokensC | Transfer RBTC or ERC20 tokens on Rootstock blockchain between wallets |
| check-transaction-historyC | Check the transaction history of a wallet on Rootstock blockchain using Alchemy API |
| issue-attestationB | Issue a new attestation on Rootstock network using RAS (Rootstock Attestation Service) |
| verify-attestationC | Verify an existing attestation by UID on Rootstock network |
| revoke-attestationC | Revoke an existing attestation by UID on Rootstock network |
| list-attestationsA | List attestations on Rootstock network by querying EAS contract event logs. Requires a custom rpcUrl — RSK public nodes do not support eth_getLogs. |
| create-schemaB | Create a new attestation schema on Rootstock network |
| attest-deploymentB | Create a deployment attestation on Rootstock using RAS. Uses default testnet schema UIDs when none is provided. |
| attest-verificationC | Create a contract verification attestation on Rootstock using RAS. Uses default testnet schema UIDs when none is provided. |
| attest-transferB | Create a transfer attestation on Rootstock using RAS. Uses default testnet schema UIDs when none is provided. |
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 22 tools
Several tools have overlapping names or purposes, such as check-transaction vs check-transaction-history and start-interaction vs start-wallet-interaction. Descriptions help differentiate, but agents could still confuse similar tools.
Tool names use a dash-separated pattern but verbs are inconsistent (e.g., 'issue-attestation' vs 'attest-deployment'). Some verbs are vague ('start-interaction'), breaking a strict verb_noun pattern.
22 tools cover a broad range of blockchain operations (wallet, transactions, contracts, attestations). The count is slightly high but justifiable for the comprehensive scope.
The tool set covers major workflows: wallet management, transfers, contract lifecycle, and attestation CRUD. Minor gaps like advanced contract queries exist, but core functionality is well-represented.