Essays on MCP
Opinionated, data-backed writing on the Model Context Protocol — grounded in the dataset behind this directory, not vibes. No “how to install MCP” filler.
The State of MCP Servers: what 1,157 tools across 126 servers actually tell us
I pulled every tool from every server we track and counted. The ecosystem is younger, more local, and less differentiated than the launch posts imply.
What I learned reading the security notes of 126 MCP servers
I went through the security profile of every server we track. The real risks are boring, concrete, and mostly about what you hand the model — not the protocol.
The Cursor tool-limit trap, and the math nobody does
The average MCP server exposes nine tools. Cursor degrades past ~40. The wall is at five servers, not fifty — and almost no one does this arithmetic before they hit it.
Local or remote MCP? The decision most people get backwards
Remote MCP sounds modern, so people reach for it. The data and the tradeoffs both say: default to local, and go remote only for specific reasons.