modelcontextprotocol / modelcontextprotocol/registry
403 on org namespace: token minted without org permission despite public membership and Owner role
@pree-dew is already working on this.
Since Aug 15, 2026.
- Dominant language
- Go
- Stars
- 7.3k
- Forks
- 994
- Avg merge
- 4d 12h
- Merged PRs (30d)
- 19
Description
Publishing to io.github.evidence-readiness/evr returns 403 with You have permission to publish: io.github.BrienBounded/*.
The minted token confirms the registry granted no org permission:
json
"auth_method": "github-at",
"auth_method_sub": "BrienBounded",
"permissions": [{"action": "publish", "resource": "io.github.BrienBounded/*"}]
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?
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Assessment
This issue has not been assessed yet.