Ops
Troubleshooting
Connection, tools, stale data, auth confusion, and timeouts — mapped to this implementation.
MCP will not connect
- Endpoint must be https://apogeemcp.digital/api/mcp or this origin’s /api/mcp.
- Auth none — do not require OAuth in the client.
- Transport HTTP / streamable HTTP, not stdio, not SSE.
- Open GET /api/mcp — expect JSON with transport streamable-http.
- Check /developers/status and hosting outages.
Tool unavailable
- Exact listed name, or a catalog alias via run_tool.
- Unknown tool → 404 / error string.
- 429 → wait Retry-After.
- tools/list is the listed set, not all 3000 names.
Data appears stale
- RHJ registry up to 10 minutes.
- pons lists ~20s.
- Explorer holders empty when Blockscout is 403.
- Wrong slug: use robinhood, not 4663, on Dex/Gecko.
- Tickers collide — pass a contract.
Authentication error
Apogee does not issue tokens. If your host demands OAuth, configure it as a custom connector with no auth, or use a client that supports unauthenticated HTTP MCP.
Timeout
Public RPC, Dex, and Gecko can be slow. NVIDIA NIM (Orbit) uses a 20s timeout. Retry with backoff; reduce lookback on list_pons_launches.
POSTs initialize and tools/list to this origin’s /api/mcp. No API key.