mcpc vs ToolHive
An independent, evidence-based trust comparison of mcpc and ToolHive, 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.
mcpc leads on trust — 80.7/100 (Grade A) vs 71.0/100 (Grade B), a 9.7-point gap. Full breakdown below.
| Signal | mcpcapify/mcpc | ToolHivestacklok/toolhive |
|---|---|---|
| HVTrust score | 80.7 | 71.0 |
| Evidence grade | A | B |
| Coverage grade | B | C |
| Overall rank | #83 | #185 |
| Rank in Protocols & Tool Integration | #3 | #8 |
| GitHub stars | 764 | 2.1k |
| Last updated | 1d ago | today |
| Build provenance | Yes | No |
| OSSF Scorecard | 4.6 / 10 | 8.1 / 10 |
| License | Apache-2.0 | Apache-2.0 |
| Downloads | 1k/wk | — |
| Trust dimensions (points earned) | ||
| Safety / integrity / 25 | 17.7 | 15.1 |
| Identity & provenance / 18 | 18.0 | 10.8 |
| Transparency / 17 | 12.4 | 15.4 |
| Maintenance / 20 | 16.5 | 20.0 |
| Adoption / 20 | 11.1 | 8.0 |
| Runtime capability surface (full matrix) | ||
| MCP server | Implemented | Implemented |
| External providers | — | — |
| Requires API keys | Yes | No |
| Plugin surface | — | plugins |
| Provenance drift | 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.3 →