Cliff Hall
Cliff Hall
> Hey Folks, > > Just wanted to know what is currently blocking this MR and if needed how I can help. This would be awesome to get merged in...
@pcarleton mentioned [this one](http://github.com/modelcontextprotocol/typescript-sdk/issues/672) when I asked in Discord. But I'm not certain that keeps 401 from reaching the client, it's just related to scopes. So I'll look into this...
> > ALSO: A big problem Is I don't have an in-project server that returns a 401 with this header for testing. > > I am in the process of...
> I see in the request that it is exposed and when I try to start the server.. it immediately runs the OAuth flow and tries to fetch the `.well-known/oauth-protected-resource`...
> Ahh sorry for the confusing report, I do see the 401 and then it continues with the OAuth Flow. > > See attached picture as you can see at...
> This is the image with no `WWW-Authenticate` ... > and this is the image with `WWW-Authenticate` ... Ok, right. But if you notice, the actual header you're looking at...
> Hm.. for some reason I can't find the 401 in the browser client inspector and I just see a 200 for the actual `/mcp` endpoint call. I tried doing...
@MOmarMiraj I've had a crack at a fix. Can you test it again?
> @cliffhall Just tried it and still similar issue, don't see the 401 on the network side of things. It would be great to see the response header list there....
> Also what I noticed, the MCP inspector doesn't extract the URL from the WWW-Authenticate header. First we have to get the header. We're working on that part.