MCP server for MyWallet providing wallet tools and blockchain operations for TON network
MyWallet MCP exposes 5 Ledger hardware wallet tools with reasonable naming (verb_noun pattern) and basic descriptions. However, critical gaps undermine production readiness: parameter descriptions are minimal or absent (e.g., 'wallet' object lacks field-level documentation), output schemas are completely undocumented, and error handling provides no recovery guidance. The 'wallet' parameter appears in 3 tools but is never formally defined, LLMs cannot infer its structure. No tool describes what it returns, making downstream composition impossible. Security-sensitive operations (signTonTransactionsWithLedger, signTonProofWithLedger) lack confirmation patterns or dry-run support despite irreversible consequences.
Retrieves a TON wallet from a connected Ledger device by account index. Takes about 170ms on Ledger Nano X.
Checks whether the TON app is open on a connected Ledger device and the device is unlocked
Signs a TON proof (for TonConnect authentication) using a connected Ledger device
Signs TON transactions using a connected Ledger device. Handles multiple messages and validates transaction compatibility with Ledger TON app version.
Verifies a TON address on a connected Ledger device by displaying it on the device screen
Output schemas completely undocumented. No tool declares what it returns, making it impossible for LLMs to plan downstream calls or extract required fields for chaining.
Parameter 'wallet' (object type) appears in 3 tools but lacks field-level documentation. LLMs cannot infer that it requires 'index' and 'version' properties, they must guess or fail.
Destructive operations (signTonTransactionsWithLedger, signTonProofWithLedger) lack confirmation or dry-run patterns. Agents can irreversibly sign transactions without user approval.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | F | 42 | 2026-07-28+ | v2 |
No error handling guidance. Tools provide no recovery hints (e.g., 'Ledger device not found. Ensure device is connected and TON app is open'). LLMs cannot self-correct on failure.
Parameter descriptions are generic or missing. 'network' is described as 'Network identifier (mainnet or testnet)' but does not state whether it accepts 'mainnet'/'testnet' strings or enum values. 'transactions' array lacks element schema.