MCP Apps vs mcpc
Both are Grade A and 3.9 points apart, so choose on what you weigh most. MCP Apps leads on transparency and adoption; mcpc leads on supply-chain integrity and maintenance.
Official repo for spec & SDK of MCP Apps protocol - standard for UIs embedded AI chatbots, served by MCP servers
Choose MCP Apps if transparency and adoption matter most.
- +5.4Adoption: 8.9M weekly downloads against 5.2k
- +0.6Transparency: OSSF Scorecard 5.8 against 5.1
The most compatible MCP CLI client. Supports: tools, resources, prompts, completions, async tasks, skills, stdio and streamable HTTP (MCP 2026-07-28 and 2025-11-25), persistent sessions, OAuth 2.1 with DCR, CIMD, client credentials, and ID-JAG, OS keychain, --json for code mode, grep for tool…
Choose mcpc if supply-chain integrity and maintenance matter most.
- +1.2Maintenance: last push 4d ago, against 5d ago
- +0.6Safety / Integrity: 96% of recent commits signed, against 68%
Where they differ
1 dimension identical: Identity 18.0 · Full evidence table
An independent, evidence-based trust comparison of MCP Apps and mcpc, 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 Appsmodelcontextprotocol/ext-apps | mcpcapify/mcpc |
|---|---|---|
| HVTrust score | 88.0 | 84.1 |
| Evidence grade | A | A |
| Coverage grade | B | B |
| Overall rank | #62 | #118 |
| Rank in Protocols & Tool Integration | #7 | #9 |
| GitHub stars | 3.1k | 1.1k |
| Last updated | 5d ago | 4d ago |
| Build provenance | Yes | Yes |
| OSSF Scorecard | 5.8 / 10 | 5.1 / 10 |
| License | NOASSERTION | Apache-2.0 |
| Downloads | 8.9M/wk | 5k/wk |
| Trust dimensions (points earned) | ||
| Safety / integrity / 25 | 18.1 | 18.7 |
| Identity & provenance / 18 | 18.0 | 18.0 |
| Transparency / 17 | 13.4 | 12.8 |
| Maintenance / 20 | 16.2 | 17.4 |
| Adoption / 20 | 17.6 | 12.2 |
| Runtime capability surface (full matrix) | ||
| MCP server | Implemented | Implemented |
| External providers | 1 — Anthropic | — |
| Requires API keys | No | Yes |
| Plugin surface | plugins | — |
| 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 →