fix: keep server.json's description within the registry's 100-char limit - #10
Merged
Merged
Conversation
The MCP registry rejects a publish with HTTP 422 when `description` exceeds 100 characters. The refreshed description shipped in 0a511f1 was 183, so the publish bounced: 422 Unprocessable Entity "expected length <= 100", location: body.description Shortened to 100 while keeping the AI-citation differentiator first, since that string is what the registry and the directories reading it display. Adds a test asserting the limit. This constraint is only enforced server-side at publish time -- long after review, and outside anything the test suite or a diff read would catch -- which is exactly the class of thing that should be a local assertion instead. Mutation-checked: a 101-character description fails it. Also gitignores `.mcpregistry*`. mcp-publisher 1.8.1 stores its registry bearer token at ~/.config/mcp-publisher/token.json, outside the repo, but upstream also supports a working-directory token file and gitignores that pattern for exactly this reason. Publishing is run from the repo root, so this removes any chance of a future version dropping a live namespace credential into a public working tree. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_0175exdX9ofY4bo1HHmNiA6e
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 MCP registry rejected the v0.9.3 publish:
The description shipped in
0a511f1was 183 characters. Shortened to exactly 100, keeping the AI-citation differentiator first since that string is what the registry and downstream directories display.Adds a test asserting the limit. This constraint is enforced server-side at publish time only — long after review, and invisible to both the test suite and a diff read. Mutation-checked: a 101-character description fails it.
Also gitignores
.mcpregistry*.mcp-publisher1.8.1 stores its registry bearer token at~/.config/mcp-publisher/token.json(verified: mode 0600, outside the repo), but upstream also supports a working-directory token file and gitignores that pattern for exactly this reason. Publishing runs from the repo root, so this removes any chance of a future version dropping a live namespace credential into a public working tree.Validated the whole
server.jsonagainst the registry schema this time rather than just the failing field —check-jsonschemapasses, and everymaxLength/pattern/enum/format/requiredconstraint was enumerated and checked. Also confirmed the non-schema publish gates: themcp-nameownership marker is present in the live PyPI 0.9.3 description, 0.9.3 exists on PyPI, and there is no version collision in the registry.576 tests pass, ruff clean.