1Money Network MCP
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| ONEMONEY_PROTOCOL_HEADERS | No | Optional JSON string of headers for custom gateways/proxies | |
| ONEMONEY_PROTOCOL_NETWORK | No | Network type: testnet, mainnet, or local | testnet |
| ONEMONEY_PROTOCOL_BASE_URL | No | Override the network base URL | |
| ONEMONEY_PROTOCOL_TIMEOUT_MS | No | Request timeout in milliseconds | 10000 |
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
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 32 tools
Tools are mostly distinct by domain area (accounts, chain, checkpoints, tokens, transactions, utils). A few pairs like tokens_issue vs tokens_mint or accounts_get_nonce vs accounts_get_bbnonce could be ambiguous without descriptions, but the verb/object division generally clarifies purpose.
All tool names follow a consistent group_verb_object pattern with snake_case throughout (e.g., accounts_get_nonce, tokens_burn, transactions_estimate_fee). Even compound actions like bridges_and_mints maintain the same style, so the naming is highly predictable.
With 32 tools, the server feels overloaded. Many utilities (utils_typeof, utils_safe_promise_all, utils_safe_promise_line) are not domain-specific and could be omitted, while the core token and transaction areas are well-covered. The count exceeds a comfortable scope for an MCP server.
The tool surface covers core blockchain operations: account nonces, chain ID, checkpoint queries, token lifecycle (issue, mint, burn, pause, whitelist/blacklist, metadata, authority), and transaction submission/estimation/retrieval. Minor gaps exist, such as an explicit token transfer tool (though payment may cover that) and no direct block query, but overall coverage is strong.