Skip to content

Relax the validation of websiteUrl #768

Closed

Description

@joelverhagen

Is your feature request related to a problem? Please describe.

Today, the websiteUrl is validated to have the same reverse domain as the MCP Server namespace.

// validateWebsiteURLNamespaceMatch validates that website URL matches the reverse-DNS namespace
func validateWebsiteURLNamespaceMatch(serverJSON apiv0.ServerJSON) error {

This is a challenge for some MCP Servers. Take Playwright for example. Its website URL is https://playwright.dev/ but the namespace will likely be microsoft.com.

On NuGet.org, we allow any website URL (called project URL) for packages. This flexibility has not caused us many issues and gives authors a chance to host their branding or docs site independently from their server namespace.

The icon URL currently can be any host. The repository URL can mismatch the namespace, when non-GitHub auth is used.

Describe the solution you'd like

Remove the validation for websiteUrl. Allow any URL, or some much looser set of validations.

Describe alternatives you've considered

Keep it as is.

Additional context

Here's an error when I was testing Playwright publishing:
Error: publish failed: server returned status 400: {"title":"Bad Request","status":400,"detail":"Failed to publish server","errors":[{"message":"websiteUrl https://playwright.dev/ does not match namespace com.joelverhagen.mcp/playwright: remote URL host playwright.dev does not match publisher domain mcp.joelverhagen.com"}]}

Activity

  1. tadasant commented on Nov 14, 2025

    @tadasant
    Member

    Agree with this under the same reasoning as #494, would accept a PR

  2. joelverhagen commented on Nov 14, 2025

    @joelverhagen
    ContributorAuthor

    @tadasant working on the PR as we speak :)

  3. joelverhagen commented on Nov 14, 2025

    @joelverhagen
    ContributorAuthor

    I have opened a PR to resolve this issue as well as a similar issue for remote URLs.
    #769

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or request

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions