CodeSampleX

Recordsnpm@modelcontextprotocol/sdk

Change the conditions
Fixed
Runtimenode 24 Package version1.31.0
Filter OSwindows 11 Architecturex64 Package managernpm 11 Execution contextnode Clear filters

Current conditions

@modelcontextprotocol/sdk @1.31.0windows 11 · x64 · node 24 · npm 11 · node

0 of 3 passed

Verified — this network ran a contract at this coordinate.

there is a sample here, and our run of it at this coordinate failed (20)

Project observations
15 / 27
Contract verifications
0 / 3
Usage records
54
Independent reporting peers
1
Failures with a captured fingerprint
0 / 12
Last recorded
2026-11-18

Exact records

This slice is down to its measured combinations — the environments below are exactly what ran.

Dependency Health

Observed combinations and failure evidence for this release

Observed problems 1 · Changed 7 · Steady 18

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 contract passed 2 project-days
express-rate-limit 8.7.1 CANDIDATE Correlated change; unproven combination contract passed 39 project-days
jose 6.2.13 CANDIDATE Correlated change; unproven combination contract passed 39 project-days
jose 6.2.4 CANDIDATE Correlated change; unproven combination contract passed 2 project-days
zod 3.25.76 CANDIDATE Correlated change; unproven combination contract passed 2 project-days
zod 4.4.3 CANDIDATE Correlated change; unproven combination contract passed 2 project-days
zod 4.6.7 CANDIDATE Correlated change; unproven combination contract passed 37 project-days
@hono/node-server 2.0.12 PASS All observations passed contract passed 2 project-days
@hono/node-server 2.1.5 PASS All observations passed contract passed 39 project-days
ajv 8.20.0 PASS All observations passed contract passed 41 project-days
ajv-formats 3.0.1 PASS All observations passed contract passed 41 project-days
content-type 1.0.5 PASS All observations passed contract passed 41 project-days
cors 2.8.6 PASS All observations passed contract passed 41 project-days
cross-spawn 7.0.6 PASS All observations passed contract passed 41 project-days
eventsource 3.0.7 PASS All observations passed contract passed 41 project-days
eventsource-parser 3.1.0 PASS All observations passed contract passed 2 project-days
eventsource-parser 3.1.1 PASS All observations passed contract passed 39 project-days
express 5.2.1 PASS All observations passed contract passed 2 project-days
express 5.3.0 PASS All observations passed contract passed 39 project-days
hono 4.13.13 PASS All observations passed contract passed 39 project-days
hono 4.13.8 PASS All observations passed contract passed 2 project-days
json-schema-typed 8.0.2 PASS All observations passed contract passed 41 project-days
pkce-challenge 5.0.1 PASS All observations passed contract passed 41 project-days
raw-body 3.0.2 PASS All observations passed contract passed 41 project-days
zod-to-json-schema 3.25.2 PASS All observations passed contract passed 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.