[barefeg]

For some time, authentication was not part of the MCP. Now it’s there https://modelcontextprotocol.io/specification/2025-03-26/bas... so I’m wondering what is being addressed in Klavis. Is it something that the reference implementation of MCP lacks? If so, will it eventually make it to MCP?

I think it’s important to release SDKs that are secure by default, so not providing this in the reference MCP would be a big issue.

In my view, MCP should be maintained by the vendors themselves. It’s too complicated to use in the enterprise if everything comes from the community with questionable security. So I applaud initiatives that try to solve this. I think smithery.ai provides something similar while also being a repository of servers (I’m not associated with them), but again the problem is needing to trust an extra middleman vendor.

Does anyone else share this view? For example, will AWS (or insert any other hyperscaler) end up providing the “Bedrock” of MCP where security is native to the platform? Or will individual companies (Box, Google, MS, etc.) start rolling them out as part of their standard developer APIs?

[wirehack]

Yes thank you! the newest MCP spec added the authentication part but it seems that people think it is still not perfect and are doing more modifications to the auth part. E.g. https://github.com/modelcontextprotocol/modelcontextprotocol.... We will also keep an eye on the spec development.

[throwup238]

> For example, will AWS (or insert any other hyperscaler) end up providing the “Bedrock” of MCP where security is native to the platform?

Cloudflare already provides something along those lines with MCP on Workers with authentication (via their zero trust product AFAIK): https://blog.cloudflare.com/remote-model-context-protocol-se...

Sounds like they were one of the partners with Anthropic in their recent “Integrations” announcement.