modelcontextprotocol/typescript-sdk

MCPcommunity
modelcontextprotocolNOASSERTIONUpdated 20d agoGitHub

The official TypeScript SDK for Model Context Protocol servers and clients

This is the branch which contains v2 of the SDK (currently in development, pre-alpha). We anticipate a stable v2 release in Q3 2026 along with the updated MCP spec. Until then, v1.x remains the recommended version for production use. v1.x will continue to receive bug fixes and security updates for at least 6 months after v2 ships to give people time to upgrade. For v1 documentation, see the V1…

Automatically indexed from public sources. Not yet verified by the developer on Forge.Claim this listing →
13kGitHub stars
2kForks
20d agoLast update
Package
Authormodelcontextprotocol
LicenseNOASSERTION
Sourcegithub
Trust Status
B
60/100Good
Listed in Forge index+10/10
Publisher identity verified+0/25
Publisher: run `forge publish` from the package repo to claim ownership
Ed25519 publish signature+0/10
Included automatically when the publisher runs `forge publish`
Domain verification+0/5
Publisher: host /.well-known/forge.json on the package homepage with { "publisher": "<github-login>" }
CVE scan · not run+0/30
Not yet scanned — package must be on npm
Static analysis · clean+20/20
npm provenance (Sigstore)+0/5
Publish from GitHub Actions with the --provenance flag
Paste into Claude Code, Cursor, or any AI assistant to fix all gaps
StatusCommunity-indexed
PublisherUnverified
SignatureUnsigned
Domain
Provenance
DependenciesNot audited
Tool surface40 tools · 1 privileged
Security scan✓ CleanvHEAD · 19d ago
EvalsNone
IndexedJun 13, 2026

Verification confirms publisher identity (repo ownership), not code safety. The security scan covers known CVEs and suspicious install scripts — it cannot prove the absence of malicious code.

About

This is the branch which contains v2 of the SDK (currently in development, pre-alpha). We anticipate a stable v2 release in Q3 2026 along with the updated MCP spec. Until then, v1.x remains the recommended version for production use. v1.x will continue to receive bug fixes and security updates for at least 6 months after v2 ships to give people time to upgrade. For v1 documentation, see the V1 API docs. For v2 API docs, see . We're temporarily restricting PRs to contributors only to manage…