Thoughts, tutorials, and insights on web development
A tab closed before the save finished, a detector read the article it was publishing, and a default branch reported ok for platforms it had never heard of. Three failures, one shape: a tool answering for something it never checked.
At the end of the third article I said most teams do not need an MCP server. Then I wrote one. This is that contradiction worked through honestly — the model plans, the code publishes, and the most useful decision in the project is a tool that does not exist.
Twelve live posts kept only 41% to 72% of their text, and every call returned ok. A post-mortem of silent tool failure in an MCP server: the race, the wrong lesson, and the check you can run.