mcp-vet — lint your MCP server for 2026-07-28 spec breakage before you ship #815
Booyaka101
started this conversation in
Show and tell
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
On July 28 the MCP
2026-07-28spec locks — sessions and theinitializehandshake are removed,-32002→-32602,tasks/listandtasks/resultare gone, androots/sampling/loggingare deprecated.I built mcp-vet to catch those in your server before a client does:
npx @booyaka/mcp-vet .It statically scans TypeScript, JavaScript, and Python MCP servers, and matches how servers are actually written — not just raw strings:
setRequestHandler(InitializeRequestSchema, …)ClientCapabilities(roots=RootsCapability())sessionIdGenerator— flagged only when it's a real generator, not the migratedundefinedEvery finding has a confidence score, an
--fixhandles the mechanical-32002 → -32602(with a--dry-runpreview), and it emits SARIF/JSON with CI-ready exit codes. It's also a typed library, not just a CLI. Run against the official reference servers (TS + Python), it produced 0 false positives.Repo: https://github.com/Booyaka101/mcp-vet · npm
@booyaka/mcp-vet· MIT.Feedback and false-positive reports very welcome — especially edge cases in how your server registers handlers.
All reactions