Recordsnpm@modelcontextprotocol/sdk1.31.0@modelcontextprotocol/sdk.ErrorCode
Change the conditions
Current conditions
@modelcontextprotocol/sdk.ErrorCode @1.31.0debian glibc · x64 · node 22 · npm · node
1 of 1 passed
Verified — this network ran a contract at this coordinate.
there is a sample here, and our run of it at this coordinate came back clean (1)
- Project observations
- 2 / 2
- Contract verifications
- 1 / 1
- Independent reporting peers
- 1
- Last recorded
- 2026-10-21
Dependency Health
Observed combinations and failure evidence for this release
First observed break
1.31.0
executionContext=node
16 FAIL · stage: PROJECT_PROCESS
| Library | Version | Health | Measured there | Projects |
|---|---|---|---|---|
| express-rate-limit | 8.6.1 | CANDIDATE Correlated change; unproven combination | 2 project-days | |
| express-rate-limit | 8.7.1 | CANDIDATE Correlated change; unproven combination | 39 project-days | |
| jose | 6.2.13 | CANDIDATE Correlated change; unproven combination | 39 project-days | |
| jose | 6.2.4 | CANDIDATE Correlated change; unproven combination | 2 project-days | |
| zod | 3.25.76 | CANDIDATE Correlated change; unproven combination | 2 project-days | |
| zod | 4.4.3 | CANDIDATE Correlated change; unproven combination | 2 project-days | |
| zod | 4.6.7 | CANDIDATE Correlated change; unproven combination | 37 project-days | |
| @hono/node-server | 2.0.12 | UNKNOWN No linked outcome measured | 2 project-days | |
| @hono/node-server | 2.1.5 | UNKNOWN No linked outcome measured | 39 project-days | |
| ajv | 8.20.0 | UNKNOWN No linked outcome measured | 41 project-days | |
| ajv-formats | 3.0.1 | UNKNOWN No linked outcome measured | 41 project-days | |
| content-type | 1.0.5 | UNKNOWN No linked outcome measured | 41 project-days | |
| cors | 2.8.6 | UNKNOWN No linked outcome measured | 41 project-days | |
| cross-spawn | 7.0.6 | UNKNOWN No linked outcome measured | 41 project-days | |
| eventsource | 3.0.7 | UNKNOWN No linked outcome measured | 41 project-days | |
| eventsource-parser | 3.1.0 | UNKNOWN No linked outcome measured | 2 project-days | |
| eventsource-parser | 3.1.1 | UNKNOWN No linked outcome measured | 39 project-days | |
| express | 5.2.1 | UNKNOWN No linked outcome measured | 2 project-days | |
| express | 5.3.0 | UNKNOWN No linked outcome measured | 39 project-days | |
| hono | 4.13.13 | UNKNOWN No linked outcome measured | 39 project-days | |
| hono | 4.13.8 | UNKNOWN No linked outcome measured | 2 project-days | |
| json-schema-typed | 8.0.2 | UNKNOWN No linked outcome measured | 41 project-days | |
| pkce-challenge | 5.0.1 | UNKNOWN No linked outcome measured | 41 project-days | |
| raw-body | 3.0.2 | UNKNOWN No linked outcome measured | 41 project-days | |
| zod-to-json-schema | 3.25.2 | UNKNOWN No linked outcome measured | 41 project-days |
The measured column is about each dependency's own release, not about the pair. A resolver placing two releases side by side is not evidence that they work together.
Dependency versions across releases
What each release of this package resolved its children to. A child whose version moved is listed first: that is where an upgrade changed something underneath you.
Moved: 3 · unchanged at every release: 14
An edge records that a resolver placed one release beside another on a real machine. It is not a claim that the two work together; that question is answered by samples and contracts, not by presence here.
Recent failure clusters
-
observed PROJECT_PROCESS ERR_MODULE_NOT_FOUND Evidence gap ×16 1.30.0 → 1.31.0 executionContext=nodeEvidence quality: legacy-evidence-incomplete · Environment variants: 3 · First recorded: 2026-08-14 · Last seen: 2026-11-11Diagnostic re-verification candidate