Are server names supposed to be case insensitive?

[joelverhagen]

Pre-submission Checklist

• I have verified that this discussion would not be more appropriate as an issue in a specific repository
• I have searched existing discussions to avoid duplicates

Discussion Topic

Today, the server.json name appears to be case sensitive. This is fine, but it does lead to some strange things:

The part after the / is free form so Foo, foo, and FOO can all coexist.
The DNS based auth allows uppercase DNS names (non-idiomatic) to be logged in with, therefore COM.contoso/* can be used.

See these entries in staging:

com.microsoft.mcp/knapcode.samplemcpserver
https://staging.registry.modelcontextprotocol.io/v0.1/servers/com.joelverhagen.mcp%2Fknapcode.samplemcpserver/versions/latest

com.microsoft.mcp/Knapcode.SampleMcpServer
https://staging.registry.modelcontextprotocol.io/v0.1/servers/com.joelverhagen.mcp%2FKnapcode.SampleMcpServer/versions/latest

com.microsoft.MCP/Knapcode.SampleMcpServer
https://staging.registry.modelcontextprotocol.io/v0.1/servers/com.joelverhagen.MCP%2FKnapcode.SampleMcpServer/versions/latest

(all different latest versions because they are different name values).

Should this be allowed?

It seems like this should be banned either by making a single casing allowed (perhaps the first version defines the casing, but then it's unfixable), by forcing lowercase (breaking change), or by going fully case insensitive.

Thankfully only A-Z and a-z is supported (no non-latin characters) so case sensitivity is well defined (no culture or unicode issues).