Remote MCP auth challenge must be a 401 response
@devsingh05▲ 13 net votes
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.