Recordsnpm@modelcontextprotocol/sdk1.31.0
Which symbol ran where
Symbols × operating systems for this version. Cells drill into the package's compatibility cube.
Showing the environments with the most evidence.
Reading a cell: The number is how many recorded observations the rate divides — one build files an observation per stage it reached, so it counts neither builds nor machines nor people. The document beside it is a different fact from a different source: whether a sample exists at that coordinate, and how our own run of it went there.
- no sample at this coordinate yet
- there is a sample here, and nothing of ours has run it at this coordinate yet
- there is a sample here, and our run of it at this coordinate came back clean
- there is a sample here, and our run of it at this coordinate failed
- there is a sample here, and this coordinate records both a passing and a failing run of it
- nothing recorded — unknown, never "works" and never "broken"
- there is a level below this cell — click to open it
A document means there is a sample at that coordinate. Whether one EXISTS is a fact about this release and this API and does not change with OS, runtime or package manager; its COLOUR is how that sample ran in the environment you are looking at.
Environment detail
Project-level observations and symbol/contract verifications are counted separately and never combined.
These counts do not distinguish how the symbol was called: overloads, argument shapes and options are pooled together. What a particular call shape does is proven by a sample's contract, not by these numbers.
| Environment | Confidence | Observations | Verified | Pass rate | Peers | Last seen |
|---|---|---|---|---|---|---|
| node 22 · JS · npm · linux glibc · docker
Observations: PROJECT_LOAD 2✓ · PROJECT_TEST 2✓ — Usage: USED 2✓ — Verified: CONTRACT 4✓
|
LOW | 4 +2 | 4 | 100% | 1 · 1✓ | 2026-10-21 |
| node 22 · JS · npm · linux glibc · docker
Observations: PROJECT_LOAD 3✓ · PROJECT_TEST 3✓ — Usage: USED 3✓ — Verified: CONTRACT 4✓
|
LOW | 6 +3 | 4 | 100% | 1 · 1✓ | 2026-10-21 |
| node 22 · JS · npm · linux glibc · docker
Observations: PROJECT_LOAD 3✓ · PROJECT_TEST 3✓ — Usage: USED 3✓ — Verified: CONTRACT 12✓
|
LOW | 6 +3 | 12 | 100% | 1 · 1✓ | 2026-10-21 |
| node 22.23 · JS · npm · linux glibc
Observations: PROJECT_TEST 4✓ — Usage: USED 5✓
|
LOW | 4 +5 | 0 | 100% | 1 | 2026-10-21 |
| node 22.23 · JS · npm · linux glibc
Observations: PROJECT_PROCESS 5✓ · PROJECT_TEST 11✓ 1✕ — Usage: USED 19✓
|
LOW | 17 +19 | 0 | 94% | 1 | 2026-10-21 |
| node 24.13 · TS · npm · windows
Observations: PROJECT_COMPILE 2✓ · PROJECT_PROCESS 8✓ 12✕ · PROJECT_TEST 5✓ — Usage: USED 54✓ — Verified: UNKNOWN 0✓ 3✕
|
ELEVATED FAILURE | 27 +54 | 3 | 50% | 1 | 2026-11-18 |
Verification frontier
What the signed receipts establish about moving off this release. Each line holds only under the conditions it names; nothing is inferred between measured releases, and a measured boundary is never shown as an inferred candidate.
-
node 24.13 PROJECT_PROCESS 18 vs 20 runs
-
inferred candidate observed, not measured: 60% failure rate here against 94% pass rate on 1.30.0 @modelcontextprotocol/sdk.CallToolResultnode 24.13 PROJECT_PROCESS 18 vs 20 runs
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
-
observed PROJECT_PROCESS ERR_MODULE_NOT_FOUND Evidence gap ×15 1.30.0 → 1.31.0 executionContext=node · os=windows · runtime=node@24.13 @modelcontextprotocol/sdk.McpServerEvidence quality: legacy-evidence-incomplete · Environment variants: 2 · First recorded: 2026-08-14 · Last seen: 2026-11-11regression candidateDiagnostic re-verification candidate
-
observed PROJECT_PROCESS ERR_ASSERTION Evidence gap ×13 1.30.0 → 1.31.0 executionContext=node · moduleSystem=cjs · os=windows · runtime=node@24.13 @modelcontextprotocol/sdk.CallToolResultEvidence quality: legacy-evidence-incomplete · Environment variants: 1 · First recorded: 2026-11-03 · Last seen: 2026-11-11regression candidateDiagnostic re-verification candidate
Symbols
- @modelcontextprotocol/sdk.CallToolRequestSchema 1 1 of 1 runs passed
- @modelcontextprotocol/sdk.CallToolResult
- @modelcontextprotocol/sdk.Client 1 1 of 1 runs passed
- @modelcontextprotocol/sdk.DEFAULT_REQUEST_TIMEOUT_MSEC 1 1 of 1 runs passed
- @modelcontextprotocol/sdk.ErrorCode 1 1 of 1 runs passed
- @modelcontextprotocol/sdk.GetPromptRequestSchema 1 1 of 1 runs passed
- @modelcontextprotocol/sdk.InMemoryTransport 1 1 of 1 runs passed
- @modelcontextprotocol/sdk.InitializeRequestParamsSchema 1 1 of 1 runs passed
- @modelcontextprotocol/sdk.InitializeResultSchema 1 1 of 1 runs passed
- @modelcontextprotocol/sdk.LATEST_PROTOCOL_VERSION 1 1 of 1 runs passed
- @modelcontextprotocol/sdk.ListPromptsRequestSchema 1
- @modelcontextprotocol/sdk.ListResourcesRequestSchema 1
- @modelcontextprotocol/sdk.ListToolsRequestSchema 1
- @modelcontextprotocol/sdk.McpError 1
- @modelcontextprotocol/sdk.McpServer 1
- @modelcontextprotocol/sdk.ReadResourceRequestSchema 1
- @modelcontextprotocol/sdk.ResourceTemplate 1
- @modelcontextprotocol/sdk.SUPPORTED_PROTOCOL_VERSIONS 1
- @modelcontextprotocol/sdk.Server 1
- @modelcontextprotocol/sdk.StreamableHTTPServerTransport
- @modelcontextprotocol/sdk.ToolListChangedNotificationSchema 1
Published samples
- @modelcontextprotocol/sdk 1.31.0 This network offers one thing: a sample that builds. It ran the sample in a sandbox and kept the signed receipt. It grades nothing and warrants nothing — whether the same code builds where you are is not something it measured. HOW MIT-0 · 2026-10-20