Blog
What we learn building a classifier that has to label every possible schema diff, and what the public monitor sees across the ecosystem.
2026-08-12
Lenient servers return 200 for outdated requests. Strict ones return opaque validation errors. Either way, the schema change that caused it is invisible to error tracking.
2026-08-12
The thirteen breaking classes an MCP tool schema can produce, each one named, with how it fails at runtime and what to do about it, from the classifier that labels them.
2026-08-12
Treat MCP contracts like dependencies: snapshot, pin the hash, verify in CI on every push and nightly, and let a green check be the only thing that closes an incident.
2026-08-12
Error trackers catch exceptions. Agent failures increasingly return 200. Where each tool wins, honestly, including where you don't need contract monitoring at all.
2026-08-12
The largest MCP spec revision since launch is rolling through the ecosystem. Every server migration is a chance for silent contract changes. How to watch yours.