GitHub shipped a compliant MCP server. Most authors can't
Weekly security audits of remote MCP servers. OAuth 2.1, PKCE, DCR, token hygiene, and the spec gaps nobody's reading. - korrel-dev/mcp-audits
Opening excerpt (first ~120 words) tap to expand
GitHub shipped a compliant MCP server. Most authors can't. Audit 01. GitHub Remote MCP Server. 2026-04-27. GitHub's remote MCP server is a careful OAuth 2.1 implementation. It works because GitHub has owned its OAuth infrastructure for over a decade. Most MCP server authors don't have that, and the spec quietly assumes they will. This is the first in a weekly series auditing remote MCP servers against the OAuth 2.1 authorization requirements of the Model Context Protocol specification. I picked GitHub first because it's the highest-stakes, most-integrated, most-resourced MCP server in the ecosystem. If anyone is going to get the spec right, it's them. They got the structural pieces right. Where they fell short, the gaps point to something about the ecosystem, not something about GitHub.
…
Excerpt limited to ~120 words for fair-use compliance. The full article is at GitHub.