MCP TypeScript SDK

The official TypeScript SDK for Model Context Protocol servers and clients

Protocols & Tool Integration TypeScript Grade C Listed NOASSERTION
63.5/100
Rank #508 of 1328
Compare MCP TypeScript SDK

How does it stack up against its Protocols & Tool Integration neighbours?

Pick any agent to compare →

Promising trust profile, but some evidence still deserves review.

Open compare tool Suggest correction
Listing state
Listed
Evidence coverage
Grade C · 2/5 signals
Last push
2026-09-20 · 0d ago
Recent change
Grade Changed +1

Is MCP TypeScript SDK safe? MCP TypeScript SDK scores 63.5/100 (Grade C), ranked #508 of 1328 tracked open-source AI agent projects, on evidence coverage C (2 of 5 independent signal types). The public evidence: no package-provenance attestation found; OSSF Scorecard rates its supply-chain practices 6.4/10; 100% of recent commits are signed; last pushed 2026-09-20. Every point is earned from checkable signals — never paid placement. How scoring works →

Ranked neighbours in Protocols & Tool Integration

Quick Trust Read

What Would Improve It
Publish package provenance or release attestations for stronger supply-chain evidence.
Recent Changes
2026-09-17
Grade Changed
Trust grade B → C
2026-09-17
Rank Moved
Rank dropped 74 spots (#429 → #503)
2026-09-08
Rank Moved
Rank dropped 10 spots (#390 → #400)
Maintainer Checklist
Raise Scorecard signals Current OSSF Scorecard is 6.4/10. Tighten the weakest checks to improve public safety evidence.
Publish provenance Add package provenance or release attestations so users can verify where shipped artifacts came from.
77.2
Activity sub-score · out of 100
#31

How to read this: HVTrust (0–100) weighs supply-chain signals (provenance, OSSF Scorecard, signed commits, open license) alongside real-world adoption. Grade C reflects the trust score band: A ≥ 80, B ≥ 65, C ≥ 50, D < 50. Evidence coverage C is separate — it grades how many independent signal types back the score (2 of 5), so a high score on thin evidence stays visible. Full methodology →

Signals refreshed 2026-09-20 16:11 UTC · Repo last pushed today

Rank Trend

2026-08-11 2026-09-20

Activity & Reach

Stars
13.4k
Forks
2.2k
Last Push
2026-09-20
today
Commits (4 wk)
8?
Downloads (7d)
HN mentions (30d)
Open Issues
300
Rank Change
=
was #508

Analysis

HVTrust Dimensions vs Protocols & Tool Integration

63.5 / 100 · 100.0% confidence

MCP TypeScript SDK Protocols & Tool Integration average (61 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
13.0 / 25
2.5 above avg 10.5
Identity / Provenance60% listing status · 40% build provenance
10.8 / 18
0.8 below avg 11.6
Transparency50% declared license · 50% OSSF Scorecard
13.9 / 17
1.1 above avg 12.8
Maintenance60% last-push freshness · 40% commit activity
13.9 / 20
in line with avg 14.0
AdoptionLog-scaled stars · package downloads
9.9 / 20
0.7 below avg 10.6

Activity Inputs

77.2 / 100
StarsRepository reach
24.8 / 30
FreshnessLast push recency
25.0 / 25
ActivityRecent commits
11.9 / 25
CommunityFork signal
15.5 / 20

Supply Chain Trust

Package Provenance
None
No package attestations found
OSSF Scorecard
6.4 / 10
OpenSSF Scorecard · scanned Sep 14, 2026
Signed Commits
100%
of last 100 commits verified
Binary-Artifacts 10
Branch-Protection 5
CI-Tests 10
CII-Best-Practices 0
Code-Review 4
Contributors 10
Dangerous-Workflow 10
Dependency-Update-Tool 10
Fuzzing 0
License 9
Maintained 10
Packaging 10
Pinned-Dependencies 5
SAST 7
Security-Policy 10
Signed-Releases -1
Token-Permissions 0
Vulnerabilities 0

Is MCP TypeScript SDK safe?

MCP TypeScript SDK has a mixed signal profile. Some trust indicators are present, others are missing. Whether it is safe for your use case depends on which gaps matter to you — review the breakdown below before adopting in production.
Does MCP TypeScript SDK publish package provenance?
No published build provenance is currently detected for MCP TypeScript SDK. This is common for open-source projects but means consumers cannot independently verify that the package on the registry matches the GitHub source.
Does MCP TypeScript SDK have an OpenSSF Scorecard?
MCP TypeScript SDK has an OpenSSF Scorecard score of 6.4/10. The Scorecard checks for branch protection, signed releases, dependency updates, fuzzing, code review, and other supply-chain hygiene items. See the full check breakdown on this page.
Is MCP TypeScript SDK actively maintained?
Actively maintained. The repository was pushed to within the last 1 day(s).
What license does MCP TypeScript SDK use?
MCP TypeScript SDK ships under NOASSERTION. A declared, OSI-approved license is one of the transparency signals HVTrust scores.
Are MCP TypeScript SDK's commits signed?
100% of the last 100 commits to MCP TypeScript SDK are verified-signed (GPG, SSH, S/MIME, or GitHub's signing flow). Signed commits help confirm that code was authored by who the commit claims.

Not a safety endorsement. HVTracker describes what public signals show, not whether a project is safe for your use case. Run your own security review before adopting in production.

AI agent surface

MCP, providers, tool surface
Scored in HVTrust

These runtime-trust fields — detected from public repo docs and manifests — contribute a bounded adjustment to this project's HVTrust score alongside supply-chain evidence. The exact values each field can add or subtract are documented in the methodology → Compare this surface across every listed agent in the capability matrix →

MCP Server Support
high confidence
Implemented
MCP TypeScript SDK appears to expose MCP server capabilities.
Detailed evidence is not shown in the public view.
External Service Dependencies
None detected
No clear third-party provider dependency detected.
Credential signal: No explicit API-key/config marker detected.
Tool / Plugin Surface
None detected
No clear plugin system or broad tool surface detected.
Detailed evidence is not shown in the public view.
Package Provenance Drift
N/A
No package source configured
Detailed evidence is not shown in the public view.
  • MCP signal live
  • External deps live
  • Tool / plugin surface live
  • Package provenance drift live

Maintain MCP TypeScript SDK?

For maintainers

HVTrust scores MCP TypeScript SDK from public signals only — we never contact maintainers first. If a signal is wrong, stale, or missing (provenance you publish, a Scorecard you run, signed releases), tell us and we'll review it. Corrections are public and tracked on GitHub.

Reputation Timeline

Signal history
Rank 16Grade 1
2026-09-17
Grade Changed
Trust grade B → C
2026-09-17
Rank Moved
Rank dropped 74 spots (#429 → #503)
2026-09-08
Rank Moved
Rank dropped 10 spots (#390 → #400)
2026-09-07
Rank Moved
Rank dropped 24 spots (#366 → #390)
2026-09-05
Rank Moved
Rank dropped 63 spots (#296 → #359)
2026-09-04
Rank Moved
Rank dropped 12 spots (#284 → #296)
2026-08-31
Rank Moved
Rank dropped 25 spots (#250 → #275)
2026-08-29
Rank Moved
Rank dropped 11 spots (#247 → #258)
2026-08-26
Rank Moved
Rank dropped 31 spots (#206 → #237)
2026-08-24
Rank Moved
Rank dropped 14 spots (#195 → #209)
2026-08-22
Rank Moved
Rank rose 13 spots (#210 → #197)
2026-08-19
Rank Moved
Rank dropped 13 spots (#190 → #203)
2026-08-17
Rank Moved
Rank rose 11 spots (#208 → #197)
2026-08-13
Rank Moved
Rank dropped 16 spots (#191 → #207)
2026-08-10
Rank Moved
Rank dropped 11 spots (#177 → #188)
2026-08-08
Rank Moved
Rank dropped 31 spots (#143 → #174)
2026-07-13
Rank Moved
Rank dropped 12 spots (#97 → #109)

Embed Badge Badge guide for maintainers →

For maintainers
HVTrust 63.5 Grade C
Markdown:
[![HVTrust](https://hvtracker.net/badge/mcp-typescript-sdk.svg)](https://hvtracker.net/agents/mcp-typescript-sdk)
HTML:
<a href="https://hvtracker.net/agents/mcp-typescript-sdk"><img src="https://hvtracker.net/badge/mcp-typescript-sdk.svg" alt="HVTrust"></a>

Other agents in Protocols & Tool Integration

Data sources
GitHub REST API (repo, commits, stars, forks, license) · OpenSSF Scorecard CLI
Each agent's signals refresh once daily across 6 staggered batches. Methodology v4.3 · Raw JSON