Hosted search_engine: organic results contain opaque relative /goto links instead of destination URLs #181

Summary

The hosted MCP search_engine tool sometimes returns opaque relative URLs in organic[].link, such as /goto?url=<opaque-value>, instead of absolute destination URLs.

The response is valid JSON, but downstream clients cannot validate the destination domain or use these values as source citations without guessing the redirect origin or making extra requests.

Environment and observation

• Hosted Bright Data MCP, not a locally pinned npm release.
• Tool: search_engine.
• Engine: google.
• Observed in multiple domain-restricted searches.
• Query text, locale, date filters, target domains, result titles, opaque values and account details are intentionally omitted for privacy.

Sanitized response shape

The following is a synthetic illustration of the observed structure, not a runnable reproduction or a real search result:

{
  "organic": [
    {
      "link": "/goto?url=<opaque-value>",
      "title": "<redacted>",
      "description": "<redacted>"
    }
  ],
  "current_page": 1
}

Expected behavior

Return canonical absolute destination URLs in organic[].link, or provide a documented response field containing the resolved destination.

Questions

1. Are relative /goto links expected output from the hosted Google search tool, or a parsing regression?
2. Is there a supported way to request resolved destination URLs without one additional request per result?
3. If these links are intentional, can their origin and resolution contract be documented? Clients should not have to infer it.

No credentials, production queries, client conversations or personal data are included. I can follow up with non-sensitive diagnostics, but cannot share the original workload publicly.