GitHub's MCP server advertised OAuth scopes it didn't support

GitHub's MCP server was telling OAuth clients they could ask for more than the server actually granted. The v1.12.1 release fixes the server's OAuth protected resource metadata, which GitHub says "became too permissive in the supported scopes advertised."

MCP clients read that metadata to decide what OAuth scopes to request during authorization. A client has no way to tell the list is inflated, it just requests what's listed. A token carrying scopes the integration never uses is dead weight sitting in a credential store, and dead weight is what turns a metadata bug into an incident the day one of those tokens leaks.

The fix narrows the metadata down to default scopes only. Nothing else about how the server authenticates changes, per the release notes.

What's missing from those notes is any account of impact: how long the metadata was over-broad, which clients pulled the wider list, or whether GitHub is rotating anything on its end. Anyone running this server is left to check their own tokens' actual scopes against 1.12.1's defaults, since the release doesn't say whether the two are reconciled automatically.