Plugin troubleshooting
If something fails, ask Claude for your session status first — it shows your mode, whether a signer is set, whether you're logged in, whether trading is halted, and your active caps and gates. Most errors below map to one of those.
Signing & session
| Symptom |
What it means |
Fix |
| "needs a signer" |
aws/privatekey mode with no key configured (session status shows signer: null) |
Set the KMS key id (see AWS KMS) or, dev only, the private key |
| NotLoggedIn |
The sign-in session expired |
Usually transient — the server re-logs-in and retries once automatically |
| Browser wallet timeout |
In browser mode, the sign-in or trade wasn't approved in your wallet in time |
Approve the prompt promptly, then retry |
| AccountNotVerified |
Your wallet's DID / KYC isn't complete |
Finish verification before trading |
Pricing & swaps
| Symptom |
What it means |
Fix |
| "min_amount_out must be > 0" |
A swap was attempted with no slippage floor |
Let the assistant derive it from a quote — never zero |
| MarketClosed / StalePrice |
An oracle stock outside US market hours |
Trade only when the market is open |
| PoolNotFound |
A made-up/mistyped ticker, or an oracle stock quoted as if it were an AMM token |
Check the symbol; price oracle stocks with the oracle price, not a pool quote |
| No-liquidity revert |
The AMM pool is too thin for that size |
Reduce the amount or pick a more liquid symbol |
| Slippage revert |
The price moved past your minimum-out |
Re-quote and retry promptly |
Policy & controls
| Symptom |
What it means |
Fix |
| "…ALLOW_… is off" / tool not available |
A gated capability (orders, withdrawals, deposits, subaccounts) isn't enabled |
Enable the gate in config — deliberately |
| Exceeds a cap / symbol not allowed |
A spend cap or allowlist blocked it |
This is policy, not a bug — don't route around it |
| TradingHalted |
The session kill switch is engaged |
Resume trading (only cancel_order works while halted) |
Install & startup
- First launch hangs for a minute or two — that's
uv resolving the environment on first run. It needs network access. It's not a crash.
- Chain-id mismatch error on startup — your RPC override points at a different chain than the network you selected. Fix the network or the override so they match.
Still stuck? The full failure-mode reference lives in the server's troubleshooting resource, and every tool is listed in the MCP tools reference.