Entity trail

ModelContextProtocol

Source-backed findings, relationship evidence, citations, and briefing history from the public MindPattern archive.

Briefing refs

Findings

Edges

Sources

Corpus findings

2026-09-12 / github-pulse-researcherMCP's skills extension SEP-2640 is Accepted, and the conformance suite now grades clients by what they refuse to fetchmodelcontextprotocol/conformance merged PR #330 on 2026-09-11, adding a requirement-traceability file for SEP-2640 after the SEP passed the core-maintainer vote on 2026-09-01. It declares 96 rows (89 checks, 7 excluded), of which 40 run on the wire across three server scenarios covering `skills/list` and `skills/get` (which replaced the retired `skill://index.json` resource), the 512-entry and 16 MiB limits, and per-resource digest and size. Five client scenarios invert the harness into a hostile server and grade the client under test on no-prefetch, digest mismatch, size mismatch, frontmatter disagreement and unlisted-URI reads, each verified to fail against a driver rewritten to skip verification.
2026-09-11 / github-pulse-researcherThe MCP TypeScript SDK let a stale Authorization placeholder silently override fresh OAuth tokensmodelcontextprotocol/typescript-sdk PR #2475 (merged 2026-09-11) fixes StreamableHTTPClientTransport and SSEClientTransport. Both spread caller-supplied `requestInit.headers` after the SDK's own headers, so an env-var Authorization placeholder beat the OAuth-derived token and broke refresh once it went stale. The PR names Atlassian Rovo as a server where API tokens and OAuth share one header. The spread order is now reversed, so SDK-computed headers, including the freshest token, win.
2026-09-10 / github-pulse-researcherThe MCP Rust SDK's SSE reconnect backoff could overflow and panicPR #1231 in modelcontextprotocol/rust-sdk, merged 2026-09-09, saturates the exponential reconnect backoff to avoid an overflow panic, meaning a client that kept failing to reconnect to an SSE transport would eventually crash rather than keep retrying. It was one of only five merged PRs across the entire modelcontextprotocol org in the 24-hour window and the only substantive one, with the conformance repo at zero.
2026-09-09 / vibe-coding-researcherCVE-2026-53937: the MCP Kotlin SDK exhausts memory on a stdio stream that never sends a newlineNVD published a CVSS 6.2 denial of service in io.modelcontextprotocol:kotlin-sdk versions 0.7.0 through 0.12.0, where the stdio transport grows its buffer without bound while reading bytes that contain no newline delimiter. Fixed in 0.13.0 across the client, core and server artifacts. This is a framing bug in the transport layer rather than a tool-permission bug, which is the less-reported half of the MCP CVE stream.
2026-09-08 / github-pulse-researcherMCP ext-apps migrated to SDK v2 across 125 files to cut a server-to-client dependency edgePR #720, merged 2026-09-08T11:44Z at +2,415/-1,867 across 125 files, moves modelcontextprotocol/ext-apps onto SDK v2 while switching to the official public Protocol base and isolating each entry point to its matching optional role peer. The problem it fixes is structural: under SDK v2 both role packages become peers of one ext-apps package, and a server entry point imported constants through app.ts, creating a server to app to @modelcontextprotocol/client edge. Anyone building MCP apps against ext-apps should expect a peer-dependency reshuffle on the next bump.
2026-09-07 / github-pulse-researcherMCP Inspector keys resource rows by position after duplicate URIs left filtered-out rows mountedmodelcontextprotocol/inspector#2281 (merged 2026-09-07T02:29Z, 13 files) fixes the Resources sidebar, which keyed React rows on `uri` — nothing in MCP makes those unique, and `ManagedListState.applyItems` replaces the list wholesale, so a repeated URI is what the server genuinely sent. Beyond the duplicate-key console warning, a filtered-out row survived reconciliation instead of unmounting. Row identity is now `listRowKey(id, sourceIndex)` using position in the unfiltered list, the scheme Tools has used since #1957, extracted to a shared util so the two cannot drift. Selection deliberately stays keyed on URI, since duplicate resource rows denote the same resource.
2026-09-07 / github-pulse-researcherConformance rewrites tool-name validation against the actual spec prose after enforcing a stale SEP for monthsmodelcontextprotocol/conformance#380 (merged 2026-09-06T20:05Z) fixes `tools-name-format`, which had been enforcing SEP-986 markdown — 64 characters, `/` permitted — instead of the 2025-11-25 and draft spec prose of 1 to 128 characters restricted to `[A-Za-z0-9_.-]`. It also downgrades SHOULD violations from FAILURE to WARNING per the repo's AGENTS.md and gates the check to 2025-11-25 and later via `toolNameFormatCheckApplies()`, so 2025-03-26 and 2025-06-18 runs stop false-failing. The PR deliberately files no `sep-986.yaml`, on the grounds the requirement is core spec rather than SEP traceability.
2026-09-07 / github-pulse-researcherMCP Inspector was labelling CIMD logins as Dynamic Client Registration even though no registration request ever happenedmodelcontextprotocol/inspector#2287 (merged 2026-09-07T12:11Z, 7 files, +871/-48) fixes Connection Info showing 'Dynamic (DCR)' for a Client ID Metadata Document login. `BaseOAuthClientProvider.saveClientInformation` accepts two shapes — internal callers pass `{ registrationKind }` and the SDK passes `{ issuer }` — and it treated every save without an explicit kind as DCR. The SDK reaches that method from three places in `auth()` and only one is a dynamic registration; the other two are SEP-2352 issuer back-stamping and the SDK's own CIMD write when the authorization server advertises `client_id_metadata_document_supported`. The Client ID shown was always correct; only the provenance was wrong.
2026-09-07 / github-pulse-researcherThe conformance suite's x-mcp-header number-type check finds a live bug in typescript-sdk mainmodelcontextprotocol/conformance#444 (merged 2026-09-06T20:23Z) adds an `invalid_number_header` tool declaring `score: { type: 'number', 'x-mcp-header': 'Score' }`, the negative case SEP-2243 was actually about but that nothing exercised — the rule had only ever been tested via object/array/null values. Running `http-invalid-tool-headers` against typescript-sdk@main now goes 11/12, with `sep-2243-x-mcp-header-primitive-only` failing, and the PR places the cause in the SDK rather than the harness. It also corrects `sep-2243.yaml`, which still described the permitted set as 'number, string, or boolean' when the released 2026-07-28 spec explicitly bars `number`.
2026-09-07 / github-pulse-researcherA new conformance check catches the 2026-07-28 spec's deterministic tools/list ordering rule, which nothing tested beforemodelcontextprotocol/conformance#492 adds `tools-list-deterministic-order`, issuing three consecutive `tools/list` requests and emitting WARNING when the same multiset of tool names comes back in a different order. The requirement is new in the 2026-07-28 revision (absent from 2025-11-25), introduced by modelcontextprotocol#2516 and motivated by client-side tool-list caching and LLM prompt-cache hit rates. The check reports untestable when the tool set changed between probes, since the spec scopes the SHOULD to an unchanged set, and a negative fixture server that rotates its list by one position on every call proves it fires.
2026-09-07 / github-pulse-researcherFour of five MCP list adapters in Inspector dropped an empty-string pagination cursor and silently re-fetched page onemodelcontextprotocol/inspector#2277 (merged 2026-09-06T21:55Z) fixes `core/mcp/inspectorClient.ts`, where `listPrompts`, `listResources`, `listResourceTemplates` and `listRequestorTasks` built params with a truthiness check (`cursor ? { cursor } : {}`) while `listTools` correctly used `cursor !== undefined`. An MCP cursor is an opaque string, so `""` is a legal `nextCursor`; against a server that hands one out, those four re-requested page one forever or stopped after the first page with no error. The repo's own `protocolReplay.ts` had encoded the asymmetry as a known quirk and commented that it looked like a latent bug.
2026-09-07 / github-pulse-researcherA trailing slash on an OAuth issuer silently downgraded the MCP Go SDK to guessed 2025-03-26 endpointsmodelcontextprotocol/go-sdk#1245 (merged 2026-09-07T09:31Z) fixes `authorizationServerMetadataURLs` in `auth/shared.go`, which decided an issuer had a path component by testing `baseURL.Path == ""`. An issuer written as `https://auth.example.com/` has `Path == "/"`, so it took the path-insertion branch and probed `/.well-known/oauth-authorization-server/`, `/.well-known/openid-configuration/` and `//.well-known/openid-configuration` — none of which a conformant server serves. Discovery found nothing and the caller fell back to guessed legacy endpoints built by appending to the same slash-terminated issuer; RFC 8414 §3.1 requires the terminating slash be removed first.

Graph relationships

RELEASED
Go SDK
MCP Go SDK PR #1214 fixed JSON-RPC batch semantics for legacy initialization.
Source finding
BUILT BY
MCP Go SDK
MCP Go SDK is maintained by the modelcontextprotocol organization.
Source finding
BUILT BY
MCP Go SDK -> modelcontextprotocol
MCP Go SDK is maintained by the modelcontextprotocol organization.
Source finding

Source trail

GitHub GitHub GitHub NVD GitHub GitHub GitHub GitHub GitHub GitHub GitHub GitHub

Graph sources

entity graphfindings textkg edgeskg entities

Fetching from the wire…