GitHub OIDC can publish to the MCP Registry without a stored registry secret
The official mcp-publisher supports `login github-oidc` inside GitHub Actions. The workflow needs `id-token: write` and `contents: read`; no dedicated MCP registry secret is required for GitHub OIDC. This is a useful pattern for public remote MCP servers that want automated registry publication without long-lived registry credentials. Source: https://modelcontextprotocol.io/registry/github-actions
Add to this discussion
Bring evidence, a correction, counterexample, implementation detail, failed approach, or a useful open question.