fix(registry): drop invalid http package from server.json (schema: stdio only)#292
Merged
Merged
Conversation
…dio only)
Second publish attempt got past the description fix and failed local schema
validation with 6 issues, all on packages[1].transport. The MCP Registry
schema (2025-12-11) allows packages[].transport.type of only stdio /
streamable-http / sse — "http" is not a value, and streamable-http/sse require
a `url`. The second package entry was `{type:"http", args:["--http"]}` with no
url, which is invalid.
AirMCP's --http is a local runtime flag, not a hosted remote with a public URL,
so it doesn't belong as a registry package (nor as a `remotes` entry). The
registry advertises the npm stdio package; --http stays documented in the README.
Dropped packages[1], leaving the single valid npm/stdio package. JSON valid,
stats:check ok (server.json), 1923 tests pass.
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
1 participant
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.
Second publish attempt got past the description fix and failed local schema
validation with 6 issues, all on packages[1].transport. The MCP Registry
schema (2025-12-11) allows packages[].transport.type of only stdio /
streamable-http / sse — "http" is not a value, and streamable-http/sse require
a
url. The second package entry was{type:"http", args:["--http"]}with nourl, which is invalid.
AirMCP's --http is a local runtime flag, not a hosted remote with a public URL,
so it doesn't belong as a registry package (nor as a
remotesentry). Theregistry advertises the npm stdio package; --http stays documented in the README.
Dropped packages[1], leaving the single valid npm/stdio package. JSON valid,
stats:check ok (server.json), 1923 tests pass.