Use the symptom and boundary below before recreating a connector.

## The client cannot discover OAuth

Confirm the MCP URL is exactly `https://data.upscrape.com/mcp`. Do not point the client at `https://app.upscrape.com`. The client must be able to follow protected-resource and authorization-server metadata.

## The browser signs in but authorization does not finish

Allow redirects between the data resource and app authorization hosts. Browser sessions are host-scoped, and the consent form must submit within the authorization host's content-security policy.

## The tool list looks stale

Some clients cache MCP tool lists per connector. Reconnect or recreate the connector after changing platform or capability pinning. The server currently advertises `listChanged: false`.

## A capability is missing

Search without a platform or category filter, then confirm that the account can see the platform in the public or authenticated catalog. Pinning cannot bypass visibility policy.

## Execution returns a business error

Tool and business failures use `isError: true` inside the JSON-RPC result. Inspect that tool content. JSON-RPC protocol errors are reserved for malformed requests, unknown methods, and invalid tool parameters.

## A result is incomplete

Look for the explicit truncation marker. MCP previews stop at 24 KiB; retrieve the full job through the REST job endpoint when appropriate.

## A slow execution never finishes in the first call

Use the returned `job_id` with `upscrape_get_job_result`. The default MCP wait is bounded and does not promise that every capability completes within one tool call.