What to prepare
- An actual supported MCP release with a valid official Registry manifest.
- The exact version already published upstream, or its authorized Registry job in this launch.
Use the route the project now supports
Goose stopped accepting new server contributions to its static directory. Publishing the correct official Registry record is the supported upstream step. The service verifies that record and labels the evidence precisely; it does not manufacture an additional listing to increase a destination count.
Submission workflow
- Use the supported official Registry publication workflow.
- Verify the exact source, version and installation identity upstream.
- Retain upstream evidence without claiming a second Goose catalog placement.
Blockers to resolve before review
Use these as preparation checks. The destination makes its own acceptance decision.
- Trying to contribute to Goose’s retired static server directory.
- Treating upstream publication or local installation as separate Goose listing evidence.
Primary sources
Checked 2026-10-30. Follow the destination’s current instructions if its requirements change.