server.json: fit the description inside the registry's 100-char cap - #50
Open
ashishmishra26 wants to merge 1 commit into
Open
server.json: fit the description inside the registry's 100-char cap#50ashishmishra26 wants to merge 1 commit into
ashishmishra26 wants to merge 1 commit into
Conversation
The v0.5.0 publish reached npm but the MCP Registry stage failed with a 422: the registry caps description at 100 characters and the listing copy ran 183. Keep the differentiators that fit (hybrid keyword + semantic search, SQL, plain files); the full copy stays on npm via package.json, which has no such cap.
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.
The v0.5.0 release published to npm but the MCP Registry stage failed with a 422: the registry caps
descriptionat 100 characters and the copy in server.json ran 183.This trims it to 98 characters keeping the differentiators (hybrid keyword + semantic search, SQL, plain files). The full copy stays on npm through package.json, which has no cap.
After merge, a manual dispatch of the Publish workflow with dry_run=false finishes the v0.5.0 registry publish: the npm stage detects 0.5.0 is already up and skips, the registry stage publishes the corrected entry.