I am interested in why you chose to do this, abd publish it with the headline you used. Was it to learn something? Or to get publicity for another project?
Tbh, this sounds like fear mongering to me. Of course the statement “99.9% of servers are not compliant” sounds impressive, but then it turns spec hasn’t even been released yet.
Also some general feedback: the whole thing looks generated, as does the comment I am replying to.
Cool project idea. skimmed the README as well as the docs link and could not figure out which MCP is ready. Docs just seem to repeat the same thing over and over.
That's a misleading title - of course no existing MCP server is going to be compliant with a spec that has not yet been released, and obviously no server is going to incorporate substantial, breaking changes when the clients themselves don't support the spec...
"OAuth 2.0 Client ID Metadata Document (CIMD)" is a big one. As an agent-provider, prereigstering client IDs for a bunch of different services and going through each ones special hoops for org validation and stuff sucks.
I have to give it to the vibe coding industry, I didn't think one could reinvent the wheel quicker and more often than frontend JavaScript programmers, but they're pulling it off!
I can't really tell why you would need to support the newer spec. It's mentioned that old stuff will work for at least a year after the new spec has been released, but I'm not so clear on what exactly will break. Is there some kind of phase out plan that the AI players have agreed upon for protocol versions will support for how long? Who is making these promises?
More importantly, I see a whole bunch of changes in headers and routing and whatnot on the MCP side itself, but I'm not really seeing what the advantages of the new spec are to either LLM users or MCP server resellers. Why consider upgrading in the first place?
8 comments
[ 2.4 ms ] story [ 28.8 ms ] threadTbh, this sounds like fear mongering to me. Of course the statement “99.9% of servers are not compliant” sounds impressive, but then it turns spec hasn’t even been released yet.
Also some general feedback: the whole thing looks generated, as does the comment I am replying to.
Would be nice to chisel this before releasing
I can't really tell why you would need to support the newer spec. It's mentioned that old stuff will work for at least a year after the new spec has been released, but I'm not so clear on what exactly will break. Is there some kind of phase out plan that the AI players have agreed upon for protocol versions will support for how long? Who is making these promises?
More importantly, I see a whole bunch of changes in headers and routing and whatnot on the MCP side itself, but I'm not really seeing what the advantages of the new spec are to either LLM users or MCP server resellers. Why consider upgrading in the first place?