@sandy081 asked:

May I know if the server definition supports a required publisher property? I remember @sridharavinash mentioning that this can be derived from the repository owner or org. If so then it makes sense that the server registry populates the publisher information in the server list and server response.

My response:

There was no current plan to include a publisher property -- it is just implied through the reverse-DNS name field. If you think it would be helpful to include, I would suggest opening a Discussion as that would be some net new requirements work that I think it'd be helpful to get more input on.

@sandy081:

Is the name field meant for the name of the MCP server, eg: @modelcontextprotocol/server-filesystem in which case the owner/publisher would be modelcontextprotocol right? If so, it would be helpful if the server registry resolves this information into a separate property with necessary details like publisher and publisherDisplayName, for eg

"publisher": {
    "name": "modelcontextprotocol",
    "displayName": "Model Context Protocol",
    "verified": true
}

I think the registry is the right one to resolve this information and leaving this to clients could cause falsy information. It is important for a user to know the publisher/owner of an MCP server. Hence it would be great if this can be included in the initial version.