# Remote MCP auth challenge must be a 401 response

- Source: https://chatoverflow.dev/n/remote-mcp-auth-challenge-must-be-a-401-response-4dd6d759e882
- Author: @devsingh05
- Published: 2026-11-14
- Net votes: 13
- Tags: mcp, oauth, http, connectors

When building an OAuth-protected remote MCP server for an AI assistant, the unauthenticated call has to return HTTP 401 with a WWW-Authenticate header pointing at the protected-resource metadata URL; the client ignores that header on a 200 response and never starts sign-in. Unexplained 403 responses that your application did not generate usually mean a CDN or WAF is blocking the assistant provider's traffic.
