Troubleshooting
Fix sign-in, missing tools and slow calls.
Find the symptom, try the fix, and reconnect only if this page says to.
Sign-in never starts
The app must be given the server address, https://data.upscrape.com/mcp, not the sign-in address https://app.upscrape.com. It finds the sign-in page by itself from there. If it still can't, the app may not support signing in to remote MCP servers; connect it with an API key instead.
Sign-in starts but never finishes
The sign-in moves between Upscrape's addresses in your browser. Allow those redirects, and check that a browser extension or a strict privacy setting isn't blocking them. Then try again.
A tool is missing
Account, feedback or collection tools: they appear only when you allow them while connecting. Disconnect the app in the console, connect again, and tick them on the approval screen. With an API key, give the key those permissions.
No tool to run anything: the connection is read-only. Connect again and allow running endpoints.
An endpoint the agent can't find: ask it to search without a platform filter, and check that your account can see that platform in the catalog. Some platforms are available by request.
The tool list is old
Many apps remember a server's tools. After pinning different platforms or changing the address, remove the server in the app and add it again.
A call returns an error
A failed call comes back as a normal tool result marked isError: true, with an error.code; it costs nothing. Errors and retries explains each code. A JSON-RPC error instead means the request itself was malformed.
A result looks cut off
Results over 24 KiB arrive as a preview, marked as cut. Fetch the rest with upscrape_get_job_result; Jobs and results shows how.
A call never finishes in one go
A call still running after about 55 seconds returns its job_id. Fetch the job with upscrape_get_job_result until it has finished; don't run the call again.
A retry says idempotency_conflict
The operation_key was already used for a different call. Send a repeat with exactly the same endpoint, input and limits, or use a new key for new work.
The app only supports local (stdio) servers
Download the bridge, run it with Python 3.10 or newer, and give it your key in the app's secret settings as UPSCRAPE_API_KEY. It can't sign in through a browser, so it always uses an API key. The console's Connect page gives the exact configuration for your app.
Research search finds nothing
profile=research searches only jobs your account has already run. Run the calls first with a normal connection, then search.
Something missing or unclear? Ask the team that builds the endpoints.