feat(mcp): publish Fanout to the official registry - #223
Merged
Conversation
There was a problem hiding this comment.
🔵 Needs a closer look
It changes the release pipeline to publish externally to the MCP Registry, so a final human review is warranted due to the operational impact.
Pull request overview
This PR adds official Model Context Protocol (MCP) Registry metadata for Fanout and extends the release workflow to publish that metadata only after the release’s full verification gate succeeds, using GitHub OIDC and a checksum-verified publisher binary.
Changes:
- Add a new MCP Registry
server.jsondefinition forio.github.labstack/fanoutconfigured for remote (HTTPS streamable HTTP) connectivity. - Document MCP Registry publication as part of the release contents and post-verification workflow behavior.
- Extend the GitHub Actions release workflow with an
mcp-registryjob that validates and publishesserver.jsonafterverify-release.
File summaries
| File | Description |
|---|---|
server.json |
Introduces the MCP Registry server definition and remote connection template for self-hosted Fanout instances. |
docs/release.md |
Updates release documentation to include MCP Registry publication and clarifies it occurs after full verification. |
.github/workflows/release.yml |
Adds an OIDC-authenticated, checksum-verified publish step to the MCP Registry gated on verify-release. |
Review details
- Files reviewed: 3/3 changed files
- Comments generated: 0
- Review effort level: Lite
💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Why remote-only
Fanout requires its MCP resource and OAuth audience to use a stable HTTPS public origin. Advertising the OCI image as an automatically launched localhost HTTP package would produce a connection that violates that contract. Container installation remains documented separately; the registry entry connects clients to an already deployed Fanout instance.
Verification