MCP011 — Resource-not-found still returns the old -32002 error code
| Severity | error |
| Fixed by | Upgrading your MCP SDK to a release targeting 2026-07-28 |
| Transports | stdio, http |
| Specification | 2026-07-28 |
| Changelog entry | Minor change 6 |
Why this changed
Resource-not-found moved from the ad-hoc -32002 to JSON-RPC’s standard
-32602 (Invalid Params). -32002 now sits in the implementation-defined
block, so a client cannot tell a stale not-found from a vendor-specific
error.
Running just this check
npx mcp-stateless --stdio "node dist/server.js" --only MCP011Suppressing it
If this check does not apply to your server, skip it:
npx mcp-stateless --stdio "node dist/server.js" --skip MCP011Rule ids are permanent and are never reissued, so a suppression cannot start silently matching a different check later.
Generated from src/rules/MCP011.ts by
scripts/gen-rule-docs.mjs. Edit the rule source, not this page.