MCPilot
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
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| callB | Executing a new message call immediately without submitting a transaction to the network |
| get-connect-uriB | Get the connect URI to connect to a MetaMask wallet |
| show-connect-qrcodeC | Show the connect QR code for a given connect URI |
| deploy-contractC | Deploy a contract to the network, given bytecode, and constructor arguments |
| disconnectB | Disconnect the metamaks wallet |
| get-accountC | Get current account |
| get-native-currency-balanceC | Get the native currency balance of an address |
| get-token-balanceC | Get token balance of an address |
| get-block-numberC | Get the block nunber of a chain |
| get-blockC | Get the block information of a chain |
| get-chain-idB | Get the current chain id |
| get-chainsB | Get the configured chains |
| get-ens-addressC | Get the ENS address for name |
| get-ens-nameC | Get the primary ENS name for address |
| get-tokenD | Get the token information |
| get-transaction-receiptC | Get the Transaction Receipt given a Transaction hash |
| get-transactionC | Get the transactions given hashes or chain identifiers |
| read-contractC | Call a read-only function on a contract, and returning the response |
| send-transactionD | Send transactions to networks |
| sign-messageD | Sign messages |
| switch-chainD | Switch the target chain |
| verify-messageC | Verify that a message was signed by the provided address |
| wait-for-transaction-receiptC | Waits for the transaction to be included on a block, and then returns the transaction receipt |
| wait-secondsC | Wait the given seconds |
| write-contractC | Execute a write function on a contract |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| be-metamask-assistant | Be a MetaMask assistant |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 25 tools
Most tools have distinct purposes with clear boundaries, such as 'deploy-contract' vs. 'write-contract' for different contract interactions. However, 'call' and 'read-contract' could be slightly confusing as both involve read-only calls, though 'call' is more general and 'read-contract' is contract-specific. Overall, the descriptions help differentiate them, with only minor overlap.
The naming follows a mostly consistent verb-noun pattern (e.g., 'get-account', 'send-transaction'), but there are deviations like 'call' (single verb), 'disconnect' (single verb), and 'wait-seconds' (verb-noun but unconventional). No camelCase mixing, but the pattern is not fully uniform, making it readable but not perfectly predictable.
With 25 tools, the count feels heavy for an MCP server focused on blockchain interactions, suggesting potential over-scoping. While the domain is broad, many tools could be consolidated (e.g., multiple 'get-' functions) or are utility-based (e.g., 'wait-seconds'), making the set borderline excessive and less streamlined than ideal.
The tool set provides comprehensive coverage for blockchain and wallet operations, including account management, contract interactions (deploy, read, write), transaction handling, chain switching, and utilities like signing and waiting. No obvious gaps exist for the intended domain, offering a complete lifecycle from connection to execution.