docs: remove status field from server.json examples#575
Merged
Conversation
The status field was removed from the server.json schema in commit b21c6f5. This change: - Removes the status field from all remaining examples - Removes the deprecated server example that was primarily about demonstrating status - Updates the example count validation from 13 to 12 The schema validation didn't catch this because additionalProperties defaults to true when not explicitly set to false. 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude <noreply@anthropic.com>
rdimitrov
approved these changes
Sep 29, 2025
slimslenderslacks
pushed a commit
to slimslenderslacks/registry
that referenced
this pull request
Dec 18, 2025
…ocol#575) ## Summary - Remove the `status` field from all server.json examples in documentation - Remove the deprecated server example that was primarily about demonstrating the status field - Update example count validation from 13 to 12 ## Context The `status` field was removed from the server.json schema in commit b21c6f5 (modelcontextprotocol#562). This PR cleans up the documentation to reflect that change. ## Why didn't tests catch this? The schema validation didn't catch the invalid `status` field because the JSON schema doesn't have `additionalProperties: false` set. This means the schema allows arbitrary additional properties by default. ## Test plan - [x] All validation checks pass (`make check`) - [x] Example count updated to match the new total (12 examples) 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-authored-by: Claude <noreply@anthropic.com>
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
2 participants
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
statusfield from all server.json examples in documentationContext
The
statusfield was removed from the server.json schema in commit b21c6f5 (#562). This PR cleans up the documentation to reflect that change.Why didn't tests catch this?
The schema validation didn't catch the invalid
statusfield because the JSON schema doesn't haveadditionalProperties: falseset. This means the schema allows arbitrary additional properties by default.Test plan
make check)🤖 Generated with Claude Code