I've never been an MCP fan or user, i loved the OpenAPI spec and i love APIs but MCP feels to me the same way GraphQL felt

The same reasons I disliked GraphQL, I dislike MCP. It's too open-ended and iffy, it's hard to cache, it's easy to attack, the auth is weird and an add-on, and everything about it is verbose. It feels like a bodge, and I think we'll suffer if we stay with it. We run an MCP server ourselves and I did a blog post measuring them and the ones from different tools and I know i went in with a negative views but i could not find may redeeming qualities. I think what bothers me the most is that it ignores existing, well-established web standards in favour of reinventing them poorly (in my view) Also there are so many inefficient implementations that will just burn your tokens and cost you a lot in time, if running locally, or in money if using an LLM api. I know i'm blaming some of the problems with how people implement it on the protocol but i think a clean and well designed protocol can make some of the problems go away, and no, i don't know what that looks like, this is just a rant about the state of things.