McpMux
Configure MCP servers once, connect every AI client through a single local gateway
Is McpMux safe? Thin or incomplete trust evidence. Review carefully before production use.
Compare McpMux
How does it stack up against its MCP Servers neighbours?
Pick any agent to compare →In detail: McpMux scores 51.8/100 (Grade C), ranked #888 of 1325 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 5.7/10; 87% of recent commits are signed; last pushed 2026-09-10. Every point is earned from checkable signals — never paid placement. How scoring works →
How McpMux compares in MCP Servers
- #500 Codealive MCP 51.9 +0.1
- #501 Mobai MCP 51.9 +0.1
- #502 McpMux 51.8 this agent
- #503 spreadsheet-kit MCP 51.8 ±0
- #504 Newsmcp 51.8 ±0
Bars show each HVTrust score; the tick marks McpMux’s 51.8.
Where the 51.8 comes from
HVTrust dimensions vs the MCP Servers average
51.8 / 100 · 100.0% confidenceMcpMux MCP Servers average (775 agents)
Quick Trust Read
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 →
Rank Trend
Activity & Reach
Analysis
Activity Inputs
35.9 / 100Supply Chain Trust
Common questions about McpMux
Does McpMux publish package provenance?
Does McpMux have an OpenSSF Scorecard?
Is McpMux actively maintained?
What license does McpMux use?
Are McpMux's commits signed?
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
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 signal live
- External deps live
- Tool / plugin surface live
- Package provenance drift live
Detected changes to McpMux's runtime surface and supply-chain posture, from daily public-signal snapshots. A change here means our detectors see something different — a genuinely changed capability, or better evidence of an existing one.
Maintain McpMux?
For maintainers
HVTrust scores McpMux 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
Embed Badge Badge guide for maintainers →
For maintainers
[](https://hvtracker.net/agents/mcpmux)
<a href="https://hvtracker.net/agents/mcpmux"><img src="https://hvtracker.net/badge/mcpmux.svg" alt="HVTrust"></a>
Other agents in MCP Servers
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