Reference implementation Data compiled from public sources as of 2026-10-26. Not an assessment, certification or recommendation. Confirm current status with the vendor and the issuing body.
AgentDossier · AI Agent Registry Find agents you can actually trust - public or inside your enterprise.
Technology & Software Engineering Top 100 / #–ARD = Agentic Resource Discovery · A2A = Agent2Agent · MCP = Model Context Protocol
Open-source project · Other · self-hosted

typescript-sdk

The official TypeScript SDK for Model Context Protocol servers and clients Publisher: modelcontextprotocol.

Vendor page ↗+ CompareExport JSON
Trust profileas of 2026-10-26
Publisherlikely · Repository ownership or inferred publisher domain — repository or Hub account ownershiplikely
Complianceno evidence foundT5
Security14 CVEs linked in the registry · 13 critical/high · newest 2026-10-20linked
ProtocolsModel Context Protocol (MCP) claimed — named in the resource's own tags; no endpoint at the publisher's well-known paths sourceAgent2Agent (A2A) probed, not foundAgentic Resource Discovery (ARD) probed, not found1 / 3
TracesNone found — nobody has published what this agent does under attacknone
Issues found0 regulator actions · 0 incidents · 0 withdrawn certificates · CVEs: see Securitylinks only

Evidence available — not a safety certification. Suitability depends on your task, deployment and permissions. Rows marked vendor-level describe modelcontextprotocol, not this agent specifically.

Traces — under attack, in defence, in incidents

none public · what a trace is

No public trace found. Nobody has published what typescript-sdk does when its inputs carry instructions it should not follow, when a tool asks for credentials, or when a task invites a destructive command. Defenders can't learn from what they can't see: run it in a sandbox before the pilot and keep the transcript, or ask the vendor to publish one.

● third-party or vendor report · ◎ this registry's own probe transcript · ⚠ data left the environment. A trace describes one version on one date; it is evidence of behaviour, never a certification. Rows marked unreviewed have not yet been checked against their source by the maintainer.

CVEs — on the official record

14 linked · the registry
CVE-2026-111767
2026-10-20
MCP TypeScript SDK is the official TypeScript SDK for Model Context Protocol servers and clients. From version 1.24.0 to before version 1.32.0, the experimental tasks feature (tas…
Auth bypass · unreviewed
High 8.6
CVE-2026-59951
2026-10-14
The MCP Python SDK, called mcp on PyPI, is a Python implementation of the Model Context Protocol (MCP). From 1.8.0 until 1.30.0 and 2.2.0, stateful Streamable HTTP servers, includ…
Denial of service · unreviewed
Medium 6.9
CVE-2026-104850
2026-10-06
MCP TypeScript SDK is the official TypeScript SDK for Model Context Protocol servers and clients. Starting in version 1.12.0 and prior to versions 1.31.0 and 2.2.0, the SDK's OAut…
Credential access · unreviewed
High 7.5
CVE-2026-52869
2026-07-15
The MCP Python SDK, called mcp on PyPI, is a Python implementation of the Model Context Protocol (MCP). Prior to 1.27.2, the SSE and stateful Streamable HTTP transports mcp.server…
Auth bypass · fix known · unreviewed
High 7.1
CVE-2026-52870
2026-07-15
The MCP Python SDK, called mcp on PyPI, is a Python implementation of the Model Context Protocol (MCP). From 1.23.0 until 1.27.2, default handlers installed by server.experimental…
Auth bypass · fix known · unreviewed
High 7.6
CVE-2026-59950
2026-07-15
The MCP Python SDK, called mcp on PyPI, is a Python implementation of the Model Context Protocol (MCP). Prior to 1.28.1, the deprecated mcp.server.websocket.websocket_server trans…
— · fix known · unreviewed
High 7.6
CVE-2026-34742
2026-04-02
The Go MCP SDK used Go's standard encoding/json. Prior to version 1.4.0, the Model Context Protocol (MCP) Go SDK does not enable DNS rebinding protection by default for HTTP-based…
Tool execution · Auth bypass · fix known · unreviewed
High 7.6
CVE-2026-25536
2026-02-04
MCP TypeScript SDK is the official TypeScript SDK for Model Context Protocol servers and clients. From version 1.10.0 to 1.25.3, cross-client response data leak when a single McpS…
Data exfiltration · fix known · unreviewed
High 7.1

6 more · All 14 in the registry → Severity is the official record's; nothing here enters the score. Links are by listed product, so a CVE that names a different component of the same platform may be missing.

Compliance evidence

4 frameworks shown
–
SOC 2
T5 Unknown
Nothing found in the sources checked.
Scope: — · registries, marketplaces, vendor pages
ask the vendor
–
ISO 27001
T5 Unknown
Nothing found in the sources checked.
Scope: — · registries, marketplaces, vendor pages
ask the vendor
–
ISO 42001
T5 Unknown
Nothing found in the sources checked.
Scope: — · registries, marketplaces, vendor pages
ask the vendor
–
CSA STAR
T5 Unknown
Nothing found in the sources checked.
Scope: — · CSA STAR Registry
ask the vendor

"Unknown" means nothing was found in the sources checked — registries, marketplaces and the vendor's own pages. It is not a finding of non-compliance; ask the vendor.

✔ found · ○ claimed · – not found · ⚠ expired, stale or revoked. Every row links to its source.Dispute or correct this dossier

GDPR, assembled from checks

GDPR● 0 found in registries or documents○ 0 vendor-claimed⚠ 0 issues linkedas of 2026-10-26
– Not foundNo Article 42 GDPR seal. "GDPR certified" is never shown without one.
☐ You checkYour lawful basis, DPIA, and whether this agent is inside the certificate scope.

News and chatter

last 90 days · linked with confidence ≥ 0.85
2026-10-23
typescript-sdk release 2.4.0
GitHub releases · +1 outlet · ### Patch Changes - Updated dependencies [[`46d9c99`](https://github.com/modelcontextprotocol/typescript-sdk/commit/46d9c9921b6542e813c1ecc5f9fc964085e8e3bb)]: - @modelcontextprotocol/core@2.4.0
Product update
2026-10-23
typescript-sdk release v2.4.0
GitHub releases · | Package | Version | |---|---| | `@modelcontextprotocol/client` | 2.4.0 | | `@modelcontextprotocol/server` | 2.4.0 | | `@modelcontextprotocol/core` | 2.4.0 | | `@modelcontextprotocol/server-legacy` | 2.4.0 | | `@modelcontextprotocol/
Product update

Headline, link and a summary attributed to the outlet. News never changes trust or domain scores.

Technology & Software Engineering score

73
technology profile · sar-score-2.0 · unranked
Adoption / usage24 / 30
Trust & security17 / 25
Project / product health20 / 20
Ecosystem / interoperability5 / 15
Domain expertise / fit71 / 100
Governance / compliance evidenceunknown
Docs / transparency7 / 10

Raw component / maximum, then weighted by the technology profile (adoption 30, trust 20, project 20, ecosystem 15, domain 10, governance 0, docs 5). Trust and governance are computed from the evidence on this page (vendor-level rows at half credit); the other components come from the curated workbook, whose order is the rank. Unknown components count as 0 and are never imputed.

Before you deploy

Derived from the evidence ledger. This agent is not yet in the reference set, so deployment questions (credentials, approval, data handling) are not answered here — ask the vendor.

Evidence supporting this use (0)

Nothing found in the sources checked.

Unknowns to check (1)
Ask the vendor for SOC 2, ISO 27001, ISO 42001, CSA STAR evidence; none was found in the sources checked
Suggested restrictions for a pilot (2)
Ask for the SOC 2 report under NDA before the pilot touches customer data; none was found in the sources checked.
No public trace of this agent under adversarial input was found. Run it in a sandbox against your own prompt-injection and tool-abuse scenarios before the pilot, and keep the transcript; the enterprise edition records one.

Rules: config/deploy_rules.json. Advice for a bounded pilot, not a verdict.

Provenance

GitHubrepository signals, license
NVDsecurity (CVE keyword search)
Hacker News, GDELT, vendor feedsnews and chatter
First seen2026-10-26
Recordres_5fb89b790432c6d1
Open the full record (JSON) →