mcp-deprecate
This server does not currently have a deployable release on Glama. Follow the repository's setup instructions to install and configure it for your MCP client, including any required credentials and local dependencies.
mcp-deprecate
Scan an MCP server for protocol features deprecated or removed by the 2026-07-28 specification release candidate, and get a dated migration checklist.
The 2026-07-28 RC is the largest revision of the Model Context Protocol since launch β it makes the protocol stateless, removes the initialize handshake and Mcp-Session-Id, and deprecates Roots, Sampling, and Logging. The spec ships the deprecation list as prose with a 12-month feature-lifecycle policy, but no tooling to find where your code is affected. mcp-deprecate is that tooling.
It ships as three surfaces over one rule engine: a CLI, a GitHub Action CI gate, and an MCP server.
What it flags
Two severities, and the difference matters:
Severity | Meaning | Examples |
π΄ error | Removed in the RC β breaking against a final-spec server |
|
π‘ warning | Deprecated β still works, removable no sooner than 12 months out (HTTP+SSE transport is shorter β 3 months after the RC reaches Final) | Roots, Sampling, Logging, the HTTP+SSE transport, |
It also prints a manual-review checklist for changes that have no reliable static signature (e.g. the new required resultType field, server/discover, CacheableResult fields). Every rule cites its originating SEP.
Related MCP server: mcpharden
Install
npm install -g mcp-deprecate
# or run without installing:
npx mcp-deprecate ./src1. CLI
mcp-deprecate [path] [options]$ mcp-deprecate ./src # line:column and migration text below are illustrative
...
ERROR 12:3 initialize / notifications/initialized handshake [mcp-2575-initialize Β· SEP-2575]
MCP is now stateless: the initialize / notifications/initialized handshake is removed.
β Carry protocol version, client identity, and capabilities in _meta on every request.
Summary: 1 error(s), 0 warning(s) across 1 file(s).Option | Default | Description |
|
|
|
|
| Non-zero-exit threshold: |
| Hide the manual-review checklist | |
| Print the full rule table and exit | |
| Print version and exit | |
| Print this help and exit |
Generate a migration document:
mcp-deprecate . --format md --fail-on none > MIGRATION.md # --fail-on none = always exit 0Exit codes: 0 clean Β· 1 findings at/above --fail-on Β· 2 usage/scan error.
2. GitHub Action
Gate pull requests so no one reintroduces a removed feature:
# .github/workflows/mcp-compat.yml
name: MCP compat
on: [pull_request]
jobs:
mcp-deprecate:
runs-on: ubuntu-latest
steps:
- uses: actions/checkout@v4
- uses: shurugiken/mcp-deprecate@v0.1.0 # pin to a released tag
with:
path: "src"
fail-on: "error" # use "warning" for a strict gateInputs: path (default .), fail-on (error/warning/none, default error), format (text/md/json, default text), version (npm dist-tag or version, default latest), advisories (true/false, default true).
3. MCP server
Security: the server reads any file path its client requests β it has no path allow-list. Connect it only to trusted MCP clients.
Run mcp-deprecate itself as an MCP server so an agent can lint other MCP servers:
{
"mcpServers": {
"mcp-deprecate": {
"command": "npx",
"args": ["-y", "--package", "mcp-deprecate", "mcp-deprecate-server"]
}
}
}Tools: scan_source(path, format?) (format defaults to md), check_spec_compat(path), list_rules().
Library
import { scanPath, render, summarize } from "mcp-deprecate";
const findings = await scanPath("./src");
console.log(render(findings, { format: "md" }));
console.log(summarize(findings)); // { errors, warnings, total, filesWithFindings }How it works & limitations
Detection is signature-based: distinctive protocol method strings (logging/setLevel), headers (Mcp-Session-Id), error codes (-32002), and official TypeScript SDK schema symbols (InitializeRequestSchema). This favors precision over recall β a clean scan is not a proof of compatibility, only the absence of known high-signal markers. Scans .ts/.tsx/.js/.jsx/.mjs/.cjs/.py/.json.
Known limits: comments are stripped before matching, but only single-line ones β Python triple-quoted docstrings and multi-line JS/TS template literals aren't tracked (tokens mentioned inside them are still matched); method values passed through a variable rather than a string literal, and values split across lines (includeContext: with the value on the next line), are not detected; rules keyed to TypeScript SDK symbols (e.g. InitializeRequestSchema) won't fire on Python servers or hand-built raw JSON-RPC strings; symlinks to files are followed but symlinked directories are not; an explicitly-passed file over 2 MB errors, and files over 2 MB are skipped during directory walks; the directory walk also skips node_modules, dist, build, out, coverage, vendor, __pycache__, and any hidden directory (names starting with ., e.g. .next, .turbo); the programmatic library entrypoint is ESM-only (require() works on Node 22.12+; on Node 20 import it as ESM or via dynamic import()) β the CLI and GitHub Action are unaffected and run on Node β₯20. The MCP server reads whatever path its client asks for, so grant it only to trusted clients.
Roadmap: AST-based call-site analysis (ts-morph), deeper Python SDK coverage, and a runtime prober that boots a server and checks advertised capabilities against the RC.
Sources
License
MIT Β© Kwashawn Warren
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelogβ¦
This server cannot be deployed
Maintenance
Related MCP Connectors
Scan any MCP server for tool-poisoning, security, auth & license. Trust score before install.
Scans remote MCP servers for protocol, security, and TLS issues; exposes scan tools via MCP.
Security scanner for MCP servers. Detect vulnerabilities, prompt injection, and tool poisoning.
Audit your MCP servers for poisoned tools and leaked secrets, and check AI-generated code for flaws.
Related MCP Servers
- AlicenseBqualityBmaintenanceFinds problems in your MCP servers before your users do. Scans your Claude config, checks every server's capabilities, actually calls tools to make sure they work, and catches breaking changes between versions.13751 npm121MIT
- FlicenseNot gradedqualityFmaintenanceScans MCP servers for security hardening issues including capability declarations, transport, and tool descriptions.1-
- AlicenseAqualityCmaintenanceSecurity scanning for MCP servers from the inside out. Provides runtime inspection, AST-based static analysis, config audit, dependency analysis, and OWASP MCP Top 10 compliance in a single MCP server.55194 npm6MIT
- AlicenseNot gradedqualityDmaintenanceZero-dependency MCP server inspector for protocol conformance, tool annotations, and capability checks.MIT