ripperTroubleshooting
Resolve common connection, search, and transaction issues.
No search results
Documentation search indexes guide titles, sections, and text. Try a short phrase such as API keys, slippage, or MCP. Launchpad search is separate and only searches indexed Ripper launches. Verify the address and clear date filters if a token is missing.
MCP connection errors
A 405 from GET is expected: configure Streamable HTTP and POST JSON-RPC to /api/v1/mcp. Include Content-Type: application/json. A 403 can indicate an untrusted Origin header. A -32602 response means the tool arguments or request parameters are invalid. A tool-level error may indicate missing data or a tier restriction.
Wallet or transaction errors
Confirm you are signed in with the intended wallet and network. If a transaction may already have been submitted, inspect it in the chain explorer before retrying. Never send a recovery phrase or private key when reporting a problem.
Check service health
GET /api/v1/health reports dependency status. HTTP 200 can still include status: degraded and a problems array. Temporary database trouble can affect indexed views while other application features remain available.