A static linter that audits MCP server code for 2026-07-28 stateless spec compliance and flags every breaking change before it ships

MCP server maintainers have no automated way to detect whether their server still uses patterns the 2026-07-28 stateless RC removed or deprecated. The RC is a breaking protocol shift: sessions are gone (Mcp-Session-Id header removed, SEP-2567), _meta fields must appear inline on requests (not stripped), three new HTTP headers are mandatory, error code -32002 maps to -32602, and three constructs are formally deprecated with a 12-month removal clock (SEP-2596). Every team that ships an MCP server must audit for all of these manually today. This tool is a CLI and CI-friendly static scanner that reads TypeScript and Python MCP server source files, traces handler registrations, and flags exactly which of these breaking or deprecation-category issues are present, with per-finding fix guidance that cites the spec section. It is not an interactive inspector (that is MCP Inspector, a different tool) and is not a generic linter (existing tools like mcp-lint validate tool schemas for cross-client compatibility, not protocol-level stateless-spec compliance). Revenue comes from a CI/team tier (per-seat or per-repo subscription) and a hosted check service where teams paste a repo URL and get a compliance report without a local install.