Jonathan Hefner

> TextContent type is notably missing a mime type property, so as near as I can tell there's no mechanism to actually communicate a mime type like application/json to a...

> VS Code and many other clients allow users to change models on-the-fly, even in the same "chat session." With this proposal, if that happens, a client would need to...

> Instead of specifying content types as a capability during the initialization phase, what about specifying them as a `_meta` parameter on each relevant JSON-RPC request (similar to an [`Accept`...

As previously mentioned, this change would now require an SEP. Also, it's worth looking at https://github.com/modelcontextprotocol/modelcontextprotocol/issues/125, which makes a similar proposal. In particular, https://github.com/modelcontextprotocol/modelcontextprotocol/issues/125#issuecomment-2567837003 notes that MCP leans towards "*fewer*...

One concern here is brigading. Should a server with 100k downloads be taken down due to 100 reports? Would there be an appeal process? Perhaps we could track report counts...

This change would now require an SEP. Your summary says "These annotations enable better governance policies, security controls, resource management, and user experience enhancements", but it's not clear to me...

Will the central registry actually implement search, or are we just defining an endpoint for API implementors? My instinct was that, for scalability reasons, search would be the purview of...

Closing in favor of https://github.com/modelcontextprotocol/modelcontextprotocol/issues/292.

Perhaps GitHub draft PRs are not deployed to staging? Will mark as "Ready for review" to see if that gets deployed, but this should not be merged yet.

@olaservo Thank you for the feedback! :smiley: I tried to address some of it in https://github.com/jonathanhefner/mcp-registry/commit/dcc2c306286fa9e97dcbf1340470e4cb2abe483c. Will also respond to your questions inline.