Support
What happens when something goes wrong — error codes, what your editor shows, retry behavior, and how to check service status.
| Code | Meaning | What to do |
|---|---|---|
| -32001 | Authentication failed | Check your API key is correct and not revoked |
| -32002 | Burst rate limit exceeded | Wait a few seconds and retry (see Retry-After header) |
| -32003 | Monthly usage limit exceeded | Upgrade plan, buy a top-up, or wait for monthly reset |
| -32004 | Per-key monthly cap reached | Increase the key's cap or use a different key |
| -32005 | Tool not allowed for this key | Edit key scopes to include the tool, or use a full-access key |
| -32600 | Invalid request format | Check your MCP client is sending valid JSON-RPC 2.0 |
| -32601 | Tool not found | Check the tool name — use tools/list to see available tools |
| -32603 | Internal server error | Retry after a few seconds. If persistent, check status page |
{ "jsonrpc": "2.0", "error": { "code": -32001, "message": "Authentication failed: invalid or revoked API key" }}| Scenario | What you see in your editor |
|---|---|
| Zephex is completely down | Tool calls time out after 30-60s. Editor shows 'tool call failed' or 'connection error'. Other editor features (autocomplete, chat) still work. |
| Your key is revoked/expired | Immediate error: 'Authentication failed'. Tools appear connected but every call fails. |
| Monthly limit reached | Error with reset date. tools/list still works. Editor shows tools as available but calls return the limit error. |
| Burst rate limit hit | Temporary error with Retry-After. Usually resolves in seconds. Happens if you trigger many rapid tool calls. |
| Network issue (your side) | Connection timeout. Check your internet. The MCP endpoint requires HTTPS. |
Most MCP clients handle retries automatically. If yours does not:
Retry-After header (usually 1-5 seconds).If Zephex is down, the following still work normally:
Zephex is an optional enhancement. Your development workflow continues without it — you just lose access to the 10 hosted tools until service is restored.
https://mcp.zephex.dev/sse)https://zephex.dev in a browser?Email support@zephex.dev with your key prefix (not the full key), the error message, and your editor name/version.