mcp-proxy vs MCP TypeScript SDK
MCP TypeScript SDK leads on trust: 94.5/100 (Grade A) against 84.5/100 (Grade A), a 10.0-point gap. MCP TypeScript SDK leads on supply-chain integrity and adoption.
A bridge between Streamable HTTP and stdio MCP transports
mcp-proxy doesn't lead on any scored dimension in this pair.
The official TypeScript SDK for Model Context Protocol servers and clients
Choose MCP TypeScript SDK if supply-chain integrity and adoption matter most.
- +4.6Safety / Integrity: 100% of recent commits signed, against 50%
- +4.6Adoption: 65.4M weekly downloads against 222.8k
- +2.0Maintenance
- +1.5Transparency: OSSF Scorecard 6.9 against 5.2
Where they differ
1 dimension identical: Identity 18.0 · Full evidence table
An independent, evidence-based trust comparison of mcp-proxy and MCP TypeScript SDK, two Protocols & Tool Integration projects in the HVTracker registry. Scores come from public, checkable signals — supply-chain provenance, OSSF Scorecard, maintenance, and adoption — not popularity.
Full evidence
| Signal | mcp-proxysparfenyuk/mcp-proxy | MCP TypeScript SDKmodelcontextprotocol/typescript-sdk |
|---|---|---|
| HVTrust score | 84.5 | 94.5 |
| Evidence grade | A | A |
| Coverage grade | B | B |
| Overall rank | #101 | #2 |
| Rank in Protocols & Tool Integration | #7 | #1 |
| GitHub stars | 2.8k | 13.5k |
| Last updated | today | 2d ago |
| Build provenance | Yes | Yes |
| OSSF Scorecard | 5.2 / 10 | 6.9 / 10 |
| License | MIT | NOASSERTION |
| Downloads | 223k/wk | 65.4M/wk |
| Trust dimensions (points earned) | ||
| Safety / integrity / 25 | 16.5 | 21.1 |
| Identity & provenance / 18 | 18.0 | 18.0 |
| Transparency / 17 | 12.9 | 14.4 |
| Maintenance / 20 | 16.7 | 18.7 |
| Adoption / 20 | 15.4 | 20.0 |
| Runtime capability surface (full matrix) | ||
| MCP server | Implemented | Implemented |
| External providers | — | — |
| Requires API keys | Yes | No |
| Plugin surface | — | — |
| Provenance drift | Match | Match |
How to read this: HVTrust (0–100) weighs supply-chain signals (provenance, OSSF Scorecard, signed commits, open license) alongside real-world adoption, scaled by an evidence-confidence factor. Grade bands: A ≥ 80, B ≥ 65, C ≥ 50, D < 50. Signals refresh daily. Full methodology v4.4 →