Remove namespace match validation for websiteUrl and remote URL #769
+30
−118
Conversation
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
This was referenced Nov 14, 2025
domdomegg
approved these changes
Nov 14, 2025
joelverhagen
changed the title
Merged
domdomegg
added a commit
that referenced
this pull request
Nov 17, 2025
Deploys v1.3.9 to production. ## Changes in v1.3.9 - New web UI for browsing the registry (#757) - Fixed namespace match validation for websiteUrl and remote URL (#769) - Added releases administration guide (#764) - Updated community projects documentation - Multiple dependency updates Release notes: https://github.com/modelcontextprotocol/registry/releases/tag/v1.3.9 The [deploy-production workflow](https://github.com/modelcontextprotocol/registry/actions/workflows/deploy-production.yml) will automatically deploy once this PR is merged.
jonathanhefner
added a commit
to jonathanhefner/mcp-registry
that referenced
this pull request
Nov 18, 2025
Follow-up to modelcontextprotocol#769, which removed the validation that remote server URLs must match the server's namespace. This commit updates `official-registry-requirements.md` to reflect the current behavior. 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude <[email protected]>
Swathi-MuraliSrinivasan
pushed a commit
to Swathi-MuraliSrinivasan/paychex-mcp-registry
that referenced
this pull request
Nov 20, 2025
…lcontextprotocol#769) <!-- Provide a brief summary of your changes --> ## Motivation and Context <!-- Why is this change needed? What problem does it solve? --> Resolve modelcontextprotocol#768 and modelcontextprotocol#494. Require HTTPS for remote URLs. Currently all remote URLs on the MCP Registry are HTTPS. Also fix a test bug when running on Windows (bad temp path). ## How Has This Been Tested? <!-- Have you tested this in a real application? Which scenarios were tested? --> Unit tests. Published a server.json locally with a website URL not matching the server name. ## Breaking Changes <!-- Will users need to update their code or configurations? --> ## Types of changes <!-- What types of changes does your code introduce? Put an `x` in all the boxes that apply: --> - [ ] Bug fix (non-breaking change which fixes an issue) - [x] New feature (non-breaking change which adds functionality) - [ ] Breaking change (fix or feature that would cause existing functionality to change) - [ ] Documentation update ## Checklist <!-- Go over all the following points, and put an `x` in all the boxes that apply. --> - [x] I have read the [MCP Documentation](https://modelcontextprotocol.io) - [x] My code follows the repository's style guidelines - [x] New and existing tests pass locally - [x] I have added appropriate error handling - [ ] ~I have added or updated documentation as needed~ N/A ## Additional context <!-- Add any other context, implementation notes, or design decisions -->
Swathi-MuraliSrinivasan
pushed a commit
to Swathi-MuraliSrinivasan/paychex-mcp-registry
that referenced
this pull request
Nov 20, 2025
Deploys v1.3.9 to production. ## Changes in v1.3.9 - New web UI for browsing the registry (modelcontextprotocol#757) - Fixed namespace match validation for websiteUrl and remote URL (modelcontextprotocol#769) - Added releases administration guide (modelcontextprotocol#764) - Updated community projects documentation - Multiple dependency updates Release notes: https://github.com/modelcontextprotocol/registry/releases/tag/v1.3.9 The [deploy-production workflow](https://github.com/modelcontextprotocol/registry/actions/workflows/deploy-production.yml) will automatically deploy once this PR is merged.
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.
Motivation and Context
Resolve #768 and #494.
Require HTTPS for remote URLs. Currently all remote URLs on the MCP Registry are HTTPS.
Also fix a test bug when running on Windows (bad temp path).
How Has This Been Tested?
Unit tests.
Published a server.json locally with a website URL not matching the server name.
Breaking Changes
Types of changes
Checklist
I have added or updated documentation as neededN/AAdditional context