mcp-near-wallet-manager
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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| create_walletA | Create or import a NEAR wallet (keypair) and return implicit account info. |
| check_balanceC | Check NEAR account balance and key stats via JSON-RPC. |
| sign_transactionB | Sign a NEAR transaction payload (transfer/function_call actions) with an ED25519 private key. |
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 3 tools
Each tool performs a clearly distinct function: creating/importing a wallet, checking balance, and signing a transaction. No overlapping responsibilities or ambiguous boundaries.
All tool names follow the verb_noun pattern in lowercase snake_case: create_wallet, check_balance, sign_transaction. Style is fully consistent across the set.
Three tools is a compact and well-scoped set for a wallet manager covering creation, inspection, and transaction signing. Each tool serves a distinct and necessary purpose.
Core wallet functions are covered: create/import, balance query, and signing. Minor gaps exist, such as account cleanup or direct transaction submission, but agents can accomplish primary wallet management tasks without dead ends.