What to prepare
- A public GitHub source repository and an accurate task-focused public description.
- The maintainer’s published server-link intake must remain open and unlocked.
- No existing request mentioning this repository in the checked intake history, and an available operator contribution identity.
Use the maintainer’s actual intake
The project maintains a public GitHub issue inviting MCP server links. That gives a specific, reviewable contribution route with a persistent request reference. It is different from discovering a private website endpoint and assuming it is a supported public publishing API.
The preflight verifies that the issue is still open, unlocked and consistent with that invitation. It also checks the available bounded comment history for an existing repository request. If the full prerequisite cannot be verified, the target cannot be purchased.
Review the public request before payment
The proposed comment should identify the source repository and describe the useful capability accurately. Keep credentials, internal endpoints and private account details out of the submission. The operator’s contribution identity performs the public action after you authorize the exact payload.
Owner source access and public intake contribution are separate capabilities. Connecting a token for your repository does not silently authorize that token to act as the service’s account on unrelated upstream projects.
Keep the result honest
The worker confirms the posted comment’s author, body and actual URL. That is evidence that the intake received the approved request. It is not evidence that the directory has imported the server, approved it or made it searchable.
Your launch preserves the request reference and an awaiting-ingestion or attention state while publication remains unconfirmed. Repeating the same request to manufacture more references would create noise, not a stronger listing result.
Submission workflow
- Run the free full preflight to verify the maintainer’s intake and check existing requests.
- Review the exact proposed public comment and explicitly authorize its submission.
- Verified payment queues the operator’s intake request, then confirms the returned author, body and comment reference.
- Track it as awaiting ingestion until actual MCP.so publication is independently established; an intake comment is not a live listing.
Blockers to resolve before review
Use these as preparation checks. The destination makes its own acceptance decision.
- The published intake is closed, locked, or no longer invites server links.
- The repository already has a pending intake request.
- The maintainer needs more information or does not choose to publish the server.
Primary sources
Checked 2026-10-29. Follow the destination’s current instructions if its requirements change.