Hi,
I have a premium archive account.
I try to connect to the MCP server with https:/newsblur.com/mcp
I also tried https:/newsblur.com/mcp/
Both connect fine, then fail with an authorisation error saying: ‘Server rejected the API token’
Do I need an API token? I thought the auth was automatic or would pop me to a browser window to agree to access.
Please could you advise what is going wrong?
Thanks
1 Like
Seeing the same with ChatGPT, failing to connect at the OAuth step, and have a premium archive subscription as well.
OAuth callback: error=invalid_scope&error_description=Client+was+not+registered+with+scope+read
I’m seeing the same issue as a third ChatGPT user. I have an active Premium Archive subscription and tested the connection through ChatGPT Developer Mode.
I tried both endpoints:
ChatGPT correctly discovers Dynamic Client Registration (DCR), reports that CIMD is unavailable, and discovers the following scopes:
I also tried explicitly adding all three as base scopes before creating a new connector. The result is still the same:
There was a problem connecting NB Test. Try again later.
The OAuth connection does not complete, and no MCP actions are discovered. This appears consistent with the earlier callback error stating that the client was not registered with the read scope.
Could you please check whether the DCR registration endpoint is saving and allowing the requested read, write, and mcp scopes for newly registered ChatGPT clients?
Martin991 nailed it. The registration endpoint wasn’t saving scopes. When a client registers without naming one, we stored an empty scope list and then rejected every scope that client asked for at /authorize. That’s the “Client was not registered with scope read” error.
ChatGPT registers without a scope every time, so it could never connect. The scopes you type into ChatGPT’s dev mode UI go into the authorize request, not the registration, which is why adding all three didn’t help.
Clients that omit a scope now default to read, write and mcp. Registrations already stored in the broken state get repaired the next time you connect, so just try again. Nothing to delete on your end.
GraBird, yours looks like a separate problem. LittleBird never completed registration with us, so it never reached the scope check. “Server rejected the API token” suggests it’s sending a NewsBlur API token instead of running the OAuth flow. Does it have an option to connect via OAuth rather than pasting a token? If you can share what its connection screen asks for, I’ll dig in.
2 Likes
Thanks for the quick turnaround. Confirmed that it’s working for me in ChatGPT now.
Hi, thanks for your attention to this. Littlebird offers up a screen to add the mcp server address:
This works with other MCP servers well, and usually will swap to a browser screen to authorise. However with Newsblur, I get this message:
Your help with this would be really welcome. Thanks
Many thanks Samuel, it works like charm now! 
1 Like