Injective MCP - An MCP server for managing Injective blockchain wallets and performing token operations
Server defines 5 tools with basic schemas and descriptions. All tools have non-empty descriptions (10-100 chars) and input schemas with typed properties. However, critical gaps limit production readiness: (1) parameter descriptions are minimal or missing context (e.g., 'recipient' lacks validation hints; 'slippage' lacks range guidance); (2) no output schemas documented, LLMs cannot predict response structure for chaining; (3) error handling is absent, no recovery guidance or categorization; (4) no idempotency or confirmation patterns for irreversible operations (transfer-token, deploy-token, swap-token); (5) security concerns: wallet file stored in plaintext in Documents folder, no permission gates. Tool names follow verb_noun pattern (good), but descriptions lack WHEN/WHY context. Schemas present but incomplete, missing examples of valid values, ranges, and format constraints.
Create a new Injective wallet. If a wallet already exists, returns the existing address.
Deploy a new token on Injective using CosmWasm
Query the balance of your Injective wallet
Swap one token for another on Injective using spot market orders
Transfer tokens from your Injective wallet to another address.
No output schemas documented. LLMs cannot predict response structure, breaking tool chaining and forcing agents to guess field names.
Irreversible operations (transfer-token, deploy-token, swap-token) lack confirmation or dry-run patterns. Agents can execute destructive actions without safeguards.
Parameter descriptions lack format constraints and ranges. 'recipient' does not specify address format validation; 'slippage' lacks min/max bounds; 'amount' lacks minimum positive value guidance.
No error handling or recovery guidance. Tool implementations throw generic errors without actionable next steps for LLMs (e.g., 'Failed to create wallet' gives no retry or fallback path).
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | F | 48 | 2026-07-28+ | v2 |
Wallet credentials stored in plaintext JSON file (Documents/injective_wallet.json). No encryption, no permission gates, no audit logging. Violates secret-injection and audit-trail patterns.