
Mcp 2026 Migration Lint
io.github.jmshinhwaPublished by GitHub account jmshinhwav0.1.5Updated Oct 24, 2026
The 2026-07-28 MCP revision removed the initialize handshake, sessions, ping and 4 more RPCs. 27 rul
Overview
A local linting tool that checks MCP server code for compatibility with the 2026-07-28 MCP revision.
- What you can do
- This server runs a migration linter for the 2026-07-28 MCP specification revision, which removed the initialize handshake, sessions, ping, and several other RPCs. It applies a set of rules to flag code that still relies on the removed protocol features. The registry description mentions 27 rules, though the full tool list is not published.
- When to use it
- Use it when you maintain an MCP server or client and need to find code that breaks under the 2026-07-28 revision. It is aimed at developers preparing a migration rather than at general assistant tasks.
- Requirements
- Runs locally as a stdio process via npx from the npm package @readystack/mcp-2026-migration-lint. Requires Node.js and network access to fetch the package. No authentication, environment variables, or headers are declared.
Installation
In SourceWeft
- Open Mcp 2026 Migration Lint in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.
Other MCP clients
Follow the launch instructions in the repository.
README
readystack-themes
Made by ReadyStack · free calculators and templates at getreadystack.com VS Code themes by ReadyStack
Source: README.md at commit ee1c884
Tools
0Version history
2- v0.1.5LatestSep 23, 2026
- v0.1.1Sep 16, 2026
Score
40% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 days25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
- Auth declared10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
- License10 pts
Declare a license in the repository or the registry entry.