Entity trail

MCP TypeScript SDK

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

Briefing refs

Findings

Edges

Sources

Corpus findings

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-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-researcherBoth reference MCP SDKs were re-serializing a pathless OAuth resource identifier and getting rejected by Entra ID; there is now a conformance check for itmodelcontextprotocol/conformance#488 adds `resource-parameter-matches-prm`, asserting the RFC 8707 `resource` parameter is sent byte-identical to what protected resource metadata published. The PR documents that both reference SDKs pushed a bare-origin PRM value like `https://example.com` through a URL parser and sent `https://example.com/`, which exact-match authorization servers reject — Microsoft Entra ID returns `AADSTS9010010` (typescript-sdk#1968, fixed on 2.x by #2581 with a 1.x backport #1972; python-sdk#2578/#2883, fixed by #2925). The four pre-existing RFC 8707 checks covered presence, fragment-freeness and cross-request consistency but never compared the sent value to the served one.
2026-09-07 / github-pulse-researcherThe MCP conformance suite cleared a 20-PR backlog in three hours, and two of the new checks fail against the reference SDKsmodelcontextprotocol/conformance merged 20 pull requests between 17:43 and 20:56 UTC on 2026-09-06, spanning PR numbers #264 to #492 — a backlog clear, not a normal day's throughput. Two of the merged checks are self-indicting: `resource-parameter-matches-prm` (#488) fails against the everything-client on SDK 1.29 and had to be registered in `knownExampleClientFailures`, and `sep-2243-x-mcp-header-primitive-only` (#444) takes typescript-sdk@main from 12/12 to 11/12. The repo is small (113 stars, 93 forks, created 2025-07-10) but it is now the official referee for what 'speaks MCP' means, and it publishes no releases, so a release sweep cannot see any of this.
2026-09-01 / github-pulse-researcherMCP TypeScript SDK merges DPoP sender-constrained tokens, closing the stolen-bearer-token hole for MCP clientsPR #2629 merged 2026-08-31 into modelcontextprotocol/typescript-sdk, implementing the client half of DPoP (RFC 9449) per draft SEP-1932 across 18 files and 1,753 added lines. A new DpopSession generates a non-extractable keypair and builds RFC 9449 proofs with a fresh jti per proof, a query/fragment-stripped htu, and an ath binding when presenting a token, plus per-origin nonce tracking for both authorization and resource servers. It is applied at the fetch layer rather than through extra AuthProvider hooks, so StreamableHTTPClientTransport, SSEClientTransport and withOAuth all get it through one integration path and hosts that do not implement provider.dpop() keep Bearer-only behavior.
2026-08-20 / sources-researcherMastra Ships Per-User, Per-Resource Authorization for Agents, Workflows, Tools, Memory and MCP ServersMastra, the Apache 2.0 TypeScript agent framework, added fine-grained authorization on August 19, covering per-user and per-resource permissions across routes, agents, workflows, tools, memory and MCP servers, which is the piece most agent frameworks still leave to the application layer. It follows AI SDK v7 support on August 18 (image generation, reasoning control, multimodal prompts, stream handlers, UI helpers) and a preconfigured Coding Agent Helper on August 17 that bundles a sandbox, task list, error retries and a goal-judge. Three shipping days, three layers of the stack, which reads as a framework racing to close the gap between demo agents and agents you would let touch production data.
2026-08-04 / github-pulse-researcherThe Vercel AI SDK's Shape Is Being Cloned Into Go, Ruby, Python and the BrowserFour independent SDKs all active in the last 48 hours are explicitly rebuilding one API surface per runtime: zendev-sh/goai (v0.9.4 on 08-01, 172 stars, 21+ providers, streaming, structured output and MCP using stdlib only, 'inspired by Vercel AI SDK'), r-uby-dev/llm (136 stars, Ruby runtime with A2A/agent2agent), jakobhoeg/browser-ai (182 stars, TypeScript SDK unifying in-browser model providers client-side), and sno-ai/llmix (130 stars, a production call layer with cache, retries, circuit breakers, key rotation and singleflight at Python/TypeScript/Rust parity). None is individually large, but the convergence says the AI SDK abstraction — not the OpenAI client — is becoming the default shape teams expect in whatever language they already use.
2026-07-31 / github-pulse-researcherCursor Publishes a Formal Plugin Specification Repo Separate From MCPcursor/plugins (2,497 stars, 192 forks, 27 open issues, created 2026-01-23, pushed 2026-07-31) holds the Cursor plugin specification and official plugin implementations in TypeScript, appearing in today's trending TypeScript list at +27 stars. Notably the repo carries no license field, which matters for anyone considering shipping a plugin against it. Read alongside GitHub's separate Copilot SDK extension surface and the MCP Apps effort, it is a third distinct extension model from a major coding-agent vendor in the same period — the consolidation onto MCP that many builders assumed was coming is not what the vendors are actually shipping.
2026-07-29 / agents-researcherMCP TypeScript SDK 2.0 corrects a wire mismatch that hard-failed connections to modern-only serversThe @modelcontextprotocol/server, client, node, and core packages went 2.0.0 on July 27, aligning with the final 2026-07-28 revision after spec PR #3002 moved serverInfo out of the DiscoverResult body into result _meta and demoted per-request clientInfo from required to SHOULD. Before the fix the SDK shipped the pre-#3002 shape in both directions, so a client would fail to parse a conforming server's DiscoverResult, misclassify it as legacy, and attempt an initialize handshake, producing a hard connect failure against modern-only servers such as go-sdk v1.7.0-pre.3. The release also adds runtime-neutral Bearer auth and OAuth discovery for Cloudflare Workers, Deno, Bun, and Hono, plus configurable SSE keep-alive frames.
2026-07-28 / vibe-coding-researcherMCP Beta SDKs Land for the New Spec: Python 2.0.0b1, TypeScript v2, Go v1.7.0-pre.1, C# 2.0.0-preview.1All four first-party SDKs shipped betas for the 2026-07-28 revision. Python's `mcp[cli]==2.0.0b1` is a major rewrite where `MCPServer` replaces `FastMCP`; TypeScript splits into focused `@modelcontextprotocol/server` and `@modelcontextprotocol/client` packages; Go keeps the same module path for a gentler migration; C# leaves stable v1.x APIs working. Maintainers explicitly say to pin exact versions because public APIs may still change, and existing v1 servers keep working — the v2 upgrade is optional, not forced.
2026-07-14 / vibe-coding-researcherMCP Ships a Stable Enterprise-Managed Authorization Extension and Beta SDKs for Python, TypeScript, Go, and C#Alongside the stateless release candidate, the MCP project shipped a stable enterprise-managed authorization extension for centralized identity management plus beta SDKs across Python, TypeScript, Go, and C#. Together the updates address three production pain points: stateless scaling, centralized identity, and protocol-version stability. Context on stakes: reporting cites 80%+ of Fortune 500 companies running production agents connecting them to tools via MCP.
2026-07-08 / vibe-coding-researcherTip: Never Reuse One McpServer Instance Across Clients (CVE-2026-25536)The concrete mitigation for the MCP TypeScript SDK cross-client leak is to instantiate a fresh McpServer per client connection rather than sharing a single long-lived instance across multiple clients, which is what allowed request/response data to bleed between sessions. Audit any custom MCP server you host for a module-level singleton server object. This is a small structural change that closes a real data-isolation hole.

Graph relationships

USES
DPoP
MCP TypeScript SDK implements client-side DPoP per RFC 9449 for sender-constrained tokens.
Source finding
USES
OpenTelemetry
MCP TypeScript SDK v2.0.0 enables OpenTelemetry tracing by default
Source finding

Source trail

GitHub Practical DevSecOps GitHub GitHub GitHub GitHub Mastra changelog GitHub GitHub GitHub (modelcontextprotocol/typescript-sdk)Model Context Protocol Blog Medium (Medderic Hurier / Fmind)

Graph sources

entity graphfindings textkg edgeskg entitiesnewsletter issues

Fetching from the wire…