Does server name after slash allow more slashes? (inconsistent schema and endpoint)

[joelverhagen]

Describe the bug

The JSON schema for server.json has a regex for the server name.

registry/docs/reference/server-json/server.schema.json

Line 50 in 9d63afb

"pattern": "^[a-zA-Z0-9.-]+/[a-zA-Z0-9._-]+$",

But this is not validated on publish. I found this when I added a /aot to my server name (and AOT'd variant = io.github.joelverhagen/Knapcode.SampleMcpServer/aot). I wasn't sure if VS Code was correct telling me that my server name was not valid... so I published anyway:

I remember seeing a sample in the past with multiple slashes in the "path" portion but I can't find it now.

To Reproduce

See the schema.

And look at this mistake of mine :/

    {
        "$schema": "https://static.modelcontextprotocol.io/schemas/2025-07-09/server.schema.json",
        "name": "io.github.joelverhagen/Knapcode.SampleMcpServer/aot",
        "description": "A sample MCP server using the MCP C# SDK. Generates random numbers and random weather.",
        "repository": {
            "url": "https://github.com/joelverhagen/Knapcode.SampleMcpServer.git",
            "source": "github"
        },
        "version": "0.8.0-beta",
        "packages": [
            {
                "registry_type": "nuget",
                "registry_base_url": "https://api.nuget.org",
                "identifier": "Knapcode.SampleMcpServer",
                "version": "0.8.0-beta",
                "transport": {
                    "type": "stdio"
                },
                "package_arguments": [
                    {
                        "value": "mcp",
                        "type": "positional",
                        "value_hint": "mcp"
                    },
                    {
                        "value": "start",
                        "type": "positional",
                        "value_hint": "start"
                    }
                ],
                "environment_variables": [
                    {
                        "value": "{weather_choices}",
                        "variables": {
                            "weather_choices": {
                                "description": "Comma separated list of weather descriptions to randomly select.",
                                "is_required": true
                            }
                        },
                        "name": "WEATHER_CHOICES"
                    }
                ]
            }
        ],
        "_meta": {
            "io.modelcontextprotocol.registry/official": {
                "id": "86667e38-34da-44eb-a0ce-e34112fd98c6",
                "published_at": "2025-09-12T21:54:51.656512708Z",
                "updated_at": "2025-09-12T21:54:51.656512708Z",
                "is_latest": true
            }
        }
    },

Expected behavior

Schema and server validation should agree.

[joelverhagen]

@claude - can you take a stab at this? Start with an implementation that enforces the regex in the in the publish endpoint. There is other server JSON validation you can put it with. You should take a TDD approach. Add a test that uses a package name with a 2 slashes in it (unlike the other examples) and assert that the publish fails. It won't, but then make the code change to see the test pass.

[joelverhagen]

@claude - good robot. You tried. I think I need to have right permissions to the repository for that to work. Go ahead and take a break for the weekend

[ossamalafhel]

Hi @danherbriley,

Thanks for reporting this issue! I've submitted PR #476 which addresses this inconsistency.

The fix adds validation to reject server names with multiple slashes during the publish API call, ensuring consistency with the JSON schema regex pattern ^[^/]+/[^/]+$.

With this change, server names like:

• com.example/server/path
• org.company/dept/team/project
• com.example//double-slash

Will now be properly rejected with the error message: "server name cannot contain multiple slashes"