McpMux

Configure MCP servers once, connect every AI client through a single local gateway

MCP Servers Rust Grade C Listed GPL-3.0
51.1/100
Rank #866 of 1328
Compare McpMux

Thin or incomplete trust evidence. Review carefully before production use.

Open compare tool Suggest correction
Listing state
Listed
Evidence coverage
Grade C · 2/5 signals
Last push
2026-08-11 · 28d ago
Recent change
Rank +7

Is McpMux safe? McpMux scores 51.1/100 (Grade C), ranked #866 of 1328 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.8/10; 87% of recent commits are signed; last pushed 2026-08-11. Every point is earned from checkable signals — never paid placement. How scoring works →

Ranked neighbours in MCP Servers

Quick Trust Read

What Would Improve It
Publish package provenance or release attestations for stronger supply-chain evidence.
Recent Changes
2026-09-08
Rank Moved
Rank dropped 14 spots (#852 → #866)
2026-09-07
Rank Moved
Rank dropped 40 spots (#812 → #852)
2026-09-06
Rank Moved
Rank dropped 11 spots (#801 → #812)
Maintainer Checklist
Raise Scorecard signals Current OSSF Scorecard is 5.8/10. Tighten the weakest checks to improve public safety evidence.
Publish provenance Add package provenance or release attestations so users can verify where shipped artifacts came from.
33.8
Activity sub-score · out of 100
#485

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 →

Signals refreshed 2026-09-08 15:33 UTC · Repo last pushed 28 days ago

Rank Trend

2026-08-11 2026-09-08

Activity & Reach

Stars
20
Forks
9
Last Push
2026-08-11
28 days ago
Commits (4 wk)
0
Downloads (7d)
HN mentions (30d)
Open Issues
5
Rank Change
▼14
was #852

Analysis

HVTrust Dimensions vs MCP Servers

51.1 / 100 · 100.0% confidence

McpMux MCP Servers average (778 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
11.6 / 25
1.7 above avg 9.9
Identity / Provenance60% listing status · 40% build provenance
10.8 / 18
2.6 below avg 13.4
Transparency50% declared license · 50% OSSF Scorecard
13.4 / 17
1.4 above avg 12.0
Maintenance60% last-push freshness · 40% commit activity
10.1 / 20
2.1 below avg 12.2
AdoptionLog-scaled stars · package downloads
3.2 / 20
3.7 below avg 6.9

Activity Inputs

33.8 / 100
StarsRepository reach
7.9 / 30
FreshnessLast push recency
21.1 / 25
ActivityRecent commits
0.0 / 25
CommunityFork signal
4.7 / 20

Supply Chain Trust

Package Provenance
None
No package attestations found
OSSF Scorecard
5.8 / 10
OpenSSF Scorecard · scanned Sep 3, 2026
Signed Commits
87%
of last 100 commits verified
Binary-Artifacts 10
Branch-Protection 8
CI-Tests 9
CII-Best-Practices 0
Code-Review 3
Contributors 6
Dangerous-Workflow 10
Dependency-Update-Tool 10
Fuzzing 0
License 10
Maintained 10
Packaging -1
Pinned-Dependencies 0
SAST 0
Security-Policy 10
Signed-Releases 8
Token-Permissions 0
Vulnerabilities 0

Is McpMux safe?

Public trust evidence for McpMux is thin: several supply-chain signals are missing or weak. This does not mean the project is unsafe — it means an outside observer cannot easily verify the usual integrity checks. Treat with extra scrutiny.
Does McpMux publish package provenance?
No published build provenance is currently detected for McpMux. This is common for open-source projects but means consumers cannot independently verify that the package on the registry matches the GitHub source.
Does McpMux have an OpenSSF Scorecard?
McpMux has an OpenSSF Scorecard score of 5.8/10. The Scorecard checks for branch protection, signed releases, dependency updates, fuzzing, code review, and other supply-chain hygiene items. See the full check breakdown on this page.
Is McpMux actively maintained?
Maintained. Last push was 28 days ago.
What license does McpMux use?
McpMux ships under GPL-3.0. A declared, OSI-approved license is one of the transparency signals HVTrust scores.
Are McpMux's commits signed?
87% of the last 100 commits to McpMux are verified-signed (GPG, SSH, S/MIME, or GitHub's signing flow). Signed commits help confirm that code was authored by who the commit claims.

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
Scored in HVTrust

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 Server Support
high confidence
Implemented
McpMux appears to expose MCP server capabilities.
Detailed evidence is not shown in the public view.
External Service Dependencies
None detected
No clear third-party provider dependency detected.
Credential signal: No explicit API-key/config marker detected.
Tool / Plugin Surface
None detected
No clear plugin system or broad tool surface detected.
Detailed evidence is not shown in the public view.
Package Provenance Drift
N/A
No package source configured
Detailed evidence is not shown in the public view.
  • MCP signal live
  • External deps live
  • Tool / plugin surface live
  • Package provenance drift live

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
Rank 17Listed 1Score 1HVTrust 1Grade 1Scorecard 1
2026-09-08
Rank Moved
Rank dropped 14 spots (#852 → #866)
2026-09-07
Rank Moved
Rank dropped 40 spots (#812 → #852)
2026-09-06
Rank Moved
Rank dropped 11 spots (#801 → #812)
2026-09-05
Rank Moved
Rank dropped 59 spots (#742 → #801)
2026-09-04
Rank Moved
Rank dropped 31 spots (#711 → #742)
2026-09-03
Rank Moved
Rank dropped 41 spots (#670 → #711)
2026-09-02
Rank Moved
Rank dropped 32 spots (#638 → #670)
2026-09-01
Rank Moved
Rank dropped 25 spots (#613 → #638)
2026-08-31
Rank Moved
Rank dropped 31 spots (#582 → #613)
2026-08-29
Rank Moved
Rank dropped 32 spots (#543 → #575)
2026-08-28
Scorecard Added
OSSF Scorecard: 5.8/10
2026-08-28
Grade Changed
Trust grade D → C
2026-08-28
Rank Moved
Rank rose 573 spots (#1116 → #543)
2026-08-28
HVTrust Changed
HVTrust up 31.0pts (20.9 → 51.9)
2026-08-27
Rank Moved
Rank dropped 19 spots (#1097 → #1116)
2026-08-26
Rank Moved
Rank dropped 71 spots (#1026 → #1097)
2026-08-24
Rank Moved
Rank dropped 10 spots (#1014 → #1024)
2026-08-16
Rank Moved
Rank dropped 32 spots (#992 → #1024)
2026-08-14
Rank Moved
Rank dropped 43 spots (#950 → #993)
2026-08-14
Activity Score Changed
Activity score down 11pts (48 → 37)
2026-08-10
Rank Moved
Rank dropped 58 spots (#905 → #963)
2026-08-08
Newly Listed
First tracked at rank #894

Embed Badge Badge guide for maintainers →

For maintainers
HVTrust 51.1 Grade C
Markdown:
[![HVTrust](https://hvtracker.net/badge/mcpmux.svg)](https://hvtracker.net/agents/mcpmux)
HTML:
<a href="https://hvtracker.net/agents/mcpmux"><img src="https://hvtracker.net/badge/mcpmux.svg" alt="HVTrust"></a>

Other agents in MCP Servers

Data sources
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