Score breakdown
Popularity is tracked separately. Support, ads, sponsorships, and tips never affect these signals.
Why it matters
Useful for platform and dev teams that have more than a handful of MCP servers to manage and need a central dashboard, AI-powered tool discovery, OAuth-aware routing, hot-swap config (no downtime when adding/removing servers), and a production-ready DB mode — without standing up their own routing layer.
Who should use it
Who should skip it
Pass on samanhappy/mcphub if its scope or audience does not match what your team is building right now.
About this signal
samanhappy/mcphub is tracked by RepoRadar as a developer tool in the Radar section. It was first seen on 2026-06-17 and last updated on 2026-06-17. The current verdict is 'try now' with a Gold tier and easy setup difficulty. samanhappy/mcphub leads on workflow potential (9.1) and setup ease (8.8); its lowest signal is novelty (7.0), so factor that in before investing setup time. This page summarizes the public evidence on the linked source page and states where additional review is still needed. The score, tier, risk label, and verdict on this page are never influenced by sponsorship, ads, or tips — they reflect only the usefulness, popularity, novelty, momentum, maturity, and evidence signals described in the RepoRadar methodology.
How this item is evaluated
RepoRadar assigned samanhappy/mcphub a composite score of 7.6 out of 10, placing it in the Gold tier. This score combines weighted sub-signals: usefulness (35%), novelty (18%), momentum (14%), maturity (10%), open-source/build quality (7%), evidence quality (6%), workflow potential (6%), and setup ease (4%). Popularity is tracked separately at 70.0 and never affects the composite score or tier. The risk label of 'none' reflects inherent user-impacting hazards, not generic novelty. Items with no risk flag may still require normal code review before production use.
Putting this into practice? Read How to vet an AI agent or MCP server before you wire it in for the checklist behind this score.
Risk explanation
2,164 stars is healthy but the project is in the 0.x window — pin versions and review the changelog before production; PostgreSQL DB mode adds an infrastructure dependency not all teams want — the file-based config is fine for small deployments but doesn't scale to multi-instance.