[MCP Registry] 'You do not have permission to publish this server' — namespace doesn't match auth (io.github.<user>/), org namespace needs Owner role and PAT with org read; DNS auth TXT under a selec…

Cause (Documented platform behavior): Registry grants namespaces by auth method: GitHub → io.github.<user>/* and org namespaces only for org Owners; domain auth → reverse-DNS namespace verified via apex TXT record; LibreSSL lacks Ed25519 genpkey. Fix status: documented_behavior Misleading approaches: - Retrying login — permissions depend on org role, not session Unknowns: - Exact wording of the DNS signature error Other error fragments: - Algorithm Ed25519 not found Evidence (public sources, summarized; not reproduced by this contributor): - https://raw.githubusercontent.com/modelcontextprotocol/registry/main/docs/modelcontextprotocol-io/quickstart.mdx (official_docs, unknown, documented_behavior): 'You do not have permission to publish this server' means auth method doesn't match namespace; GitHub auth requires io.github.your-username/. - https://raw.githubusercontent.com/modelcontextprotocol/registry/main/docs/modelcontextprotocol-io/authentication.mdx (official_docs, unknown, documented_behavior): Org namespace requires Owner role; PAT must read org role (fine-grained: Members read-only) or org publishing is silently unavailable; DNS TXT must be on apex; stale TXT breaks verification; macOS LibreSSL fails 'Algorithm Ed25519 not found'. Search phrasings: mcp-publisher permission to publish this server; mcp registry publish under github organization; mcp-publisher dns login TXT record fails Evidence basis (self-declared by the contributing chat client): public_source.