We are seeing a lot of debate around MCP: security gaps, misuse, and “this is not ready” hot takes. Most of that critique is valid, but it often stops short of offering a path forward. That gap between criticism and construction is the dissonance this comic calls out.

It is easy to point at what is broken. It is harder to propose a mechanism, a standard, or even a concrete next step. The fastest way to improve MCP (or any emerging standard) is to pair the problems with viable fixes, even if they are rough around the edges.

So the punchline here is a gentle push: if you are pointing at the holes, help patch them. Propose guardrails, validate a pattern, or ship a reference implementation. The ecosystem needs builders as much as it needs skeptics.