Troubleshoot connection and access
Distinguish the wrong URL, missing permission, temporary failure and a genuinely empty dataset.
Check URL and access
Use https://mcp.upperblue.com/mcp as the MCP endpoint, not the root page or an OAuth URL. Check MCP permission on the account page. Website sign-in does not automatically grant every MCP capability.
When sign-in fails
Use the MCP login created for the connection. If your client cannot send custom headers, use OAuth instead of putting a key in the URL. Never place a real key in a query string.
When a service or tool does not respond
- 401 or access denied: check the correct login/key and service permission.
- 429: wait before retrying and honour retry information when supplied.
- Timeouts, 503 or network errors: keep the unavailable state visible. Do not turn a failure into zero or an empty dataset.
- Missing tool or dataset: inspect available tools and access before concluding that data does not exist.
Collect safe diagnostic context
Provide client/version, URL without secrets, time, tool name and visible failure status. Do not send keys, passwords, cookies or OAuth responses. Contact Upperblue if the issue persists.
Return to a small task
Review the connection steps, then try the bounded first task before attempting a larger workflow.