You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
403 on org namespace: token minted without org permission despite public membership and Owner role #1527
State on my side, all verified rather than assumed:
GET /orgs/evidence-readiness/public_members/BrienBounded → 204 (membership public)
Owner of the org
Both /orgs/evidence-readiness and /users/evidence-readiness → 200 (it is an organization)
Token file deleted and confirmed absent before re-running mcp-publisher login github, so this is a freshly minted token, not a cached one
gh auth status shows read:org present, though mcp-publisher appears to run its own device flow rather than reusing that token — no corresponding entry appears in my authorized OAuth apps
Expected: the token carries io.github.evidence-readiness/*. Actual: personal namespace only.
Is org enumeration under github-at expected to see public membership, or does it require something beyond Owner and public visibility?
Root cause identified + working workaround posted on #1649. Short version: the device-flow GitHub App (MCP Registry Login (Prod)) does not request read:org scope, so the token cannot see org memberships — even public ones. Workaround: exchange a read:org-scoped token directly via POST /v0/auth/github-at.
Closing this as a duplicate of #1468, which tracks the same inability to publish to organization namespaces using interactive GitHub device login and is now linked from the authentication docs. I cross-linked this report there to preserve its diagnostics and workaround reports.
#1483 corrected the misleading error guidance and documented PAT/GitHub Actions OIDC alternatives; it did not fix interactive organization authentication. #1468 remains open for that underlying problem. Please continue tracking the fix there.
Activity
Register dike-legal-search's MCP server in the official MCP Registry
List the MCP server in the MCP Registry, published from CI with OIDC
List the MCP server in the MCP Registry via CI OIDC; date v0.26.0 (#56)
jcolvin1056 commentedon Oct 11, 2026
Root cause identified + working workaround posted on #1649. Short version: the device-flow GitHub App (
MCP Registry Login (Prod)) does not requestread:orgscope, so the token cannot see org memberships — even public ones. Workaround: exchange aread:org-scoped token directly viaPOST /v0/auth/github-at.rdimitrov commentedon Oct 23, 2026
Closing this as a duplicate of #1468, which tracks the same inability to publish to organization namespaces using interactive GitHub device login and is now linked from the authentication docs. I cross-linked this report there to preserve its diagnostics and workaround reports.
#1483 corrected the misleading error guidance and documented PAT/GitHub Actions OIDC alternatives; it did not fix interactive organization authentication. #1468 remains open for that underlying problem. Please continue tracking the fix there.