Good catch, and thanks for the precise report. The two metadata documents disagreed on the canonical URL: the discovery metadata at the origin root advertised https://newsblur.com/mcp/ with a trailing slash while the MCP server itself uses https://newsblur.com/mcp without it. Codex validates those strictly, so both config variants failed. I’ve made everything consistent on the no slash form, which passes Codex’s validation for both URL styles. It will be live shortly, and then either url variant in your config.toml will work.
On the CLI: your account is correctly Premium Archive on the server and the account info endpoint returns the right tier. The bug was that when the CLI’s account info request fails for any reason, it silently showed Tier: Free instead of admitting it couldn’t fetch your info. The next CLI release shows Unknown plus the error instead. If you run newsblur auth status again it should say Archive.