What to prepare
- An active/latest exact official Registry version, matching source, license and installation metadata.
- An unlocked onboarding discussion and complete duplicate-comment/reply scan.
- Verified source-owner authority and service contributor identity.
Request curation and follow the actual catalog
New servers require manual curation even after official Registry publication. The service can send an accurate owner-authorized request without asking the customer to complete another form. It checks existing requests first and reconciles an uncertain write before any retry.
A request is not acceptance. The worker reads GitHub’s catalog independently and matches the registry name, source and installation identity before reporting inclusion.
Submission workflow
- Publish and verify the exact official Registry version.
- Review the proposed curation request and its actual source/release facts.
- The service posts one request to the existing onboarding discussion and retains its independent receipt.
- Follow curator response and verify the exact record in GitHub’s public catalog.
Blockers to resolve before review
Use these as preparation checks. The destination makes its own acceptance decision.
- Missing active/latest upstream identity or an existing onboarding request.
- Manual curation declines or does not select the server.
Primary sources
Checked 2026-10-30. Follow the destination’s current instructions if its requirements change.