updated 2026-08-14 06:32 UTC

MCP Bundles

modelcontextprotocol/mcpb

Desktop Extensions: One-click local MCP server installation in desktop apps

Protocols & Tool Integration TypeScript Grade C Listed NOASSERTION
53.8/100
Rank #426 of 1283
Compare MCP Bundles

How does it stack up against its Protocols & Tool Integration neighbours?

Pick any agent to compare →

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-05-26 · 80d ago
Recent change
Rank +3

Is MCP Bundles safe? MCP Bundles scores 53.8/100 (Grade C), ranked #426 of 1283 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 6.1/10; 100% of recent commits are signed; last pushed 2026-05-26. Every point is earned from checkable signals — never paid placement. How scoring works →

Ranked neighbours in Protocols & Tool Integration

#26 Agent Reach — 58.8 (C) → #27 Figma Context MCP — 55.2 (C) → #29 FastMCP — 49.5 (D) → #30 MetaMCP — 48.4 (D) →

Quick Trust Read

What Would Improve It
Publish package provenance or release attestations for stronger supply-chain evidence.
Recent Changes
2026-08-13
Rank Moved
Rank dropped 15 spots (#411 → #426)
2026-08-12
Rank Moved
Rank rose 14 spots (#425 → #411)
2026-08-10
Rank Moved
Rank dropped 18 spots (#406 → #424)
Maintainer Checklist
Raise Scorecard signals Current OSSF Scorecard is 6.1/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.
Refresh maintenance signals The repo was last pushed 80 days ago. Fresh activity helps separate stable projects from stale ones.
Compare with another agent Get email alerts for MCP Bundles View Protocols & Tool Integration Report missing data
44.7
Activity sub-score · out of 100
#28
In Protocols & Tool Integration

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-08-14 06:32 UTC · Repo last pushed 80 days ago

Rank Trend

2026-08-11 2026-08-14

Activity & Reach

Stars
2.1k
Forks
207
Last Push
2026-05-26
80 days ago
Commits (4 wk)
0
Downloads (7d)
—
HN mentions (30d)
—
Open Issues
64
Rank Change
=
was #426

Analysis

HVTrust Dimensions vs Protocols & Tool Integration

53.8 / 100 · 100.0% confidence

MCP Bundles Protocols & Tool Integration average (57 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
12.6 / 25
4.0 above avg 8.6
Identity / Provenance60% listing status · 40% build provenance
10.8 / 18
0.9 below avg 11.7
Transparency50% declared license · 50% OSSF Scorecard
13.7 / 17
2.3 above avg 11.4
Maintenance60% last-push freshness · 40% commit activity
6.7 / 20
7.1 below avg 13.8
AdoptionLog-scaled stars · package downloads
8.0 / 20
2.4 below avg 10.4

Activity Inputs

44.7 / 100
StarsRepository reach
19.9 / 30
FreshnessLast push recency
13.9 / 25
ActivityRecent commits
0.0 / 25
CommunityFork signal
10.8 / 20

Supply Chain Trust

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

Is MCP Bundles safe?

Public trust evidence for MCP Bundles 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 MCP Bundles publish package provenance?
No published build provenance is currently detected for MCP Bundles. This is common for open-source projects but means consumers cannot independently verify that the package on the registry matches the GitHub source.
Does MCP Bundles have an OpenSSF Scorecard?
MCP Bundles has an OpenSSF Scorecard score of 6.1/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 MCP Bundles actively maintained?
Slowing down. Last push was 80 days ago — keep an eye on whether activity resumes.
What license does MCP Bundles use?
MCP Bundles ships under NOASSERTION. A declared, OSI-approved license is one of the transparency signals HVTrust scores.
Are MCP Bundles's commits signed?
100% of the last 100 commits to MCP Bundles 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
MCP Bundles 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 MCP Bundles?

For maintainers

HVTrust scores MCP Bundles 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.

Submit a correction → Add the trust badge

Reputation Timeline

Signal history
Rank 5Listed 1HVTrust 1Grade 1Scorecard 1
2026-08-13
Rank Moved
Rank dropped 15 spots (#411 → #426)
2026-08-12
Rank Moved
Rank rose 14 spots (#425 → #411)
2026-08-10
Rank Moved
Rank dropped 18 spots (#406 → #424)
2026-08-08
Rank Moved
Rank dropped 101 spots (#303 → #404)
2026-07-15
Scorecard Added
OSSF Scorecard: 6.6/10
2026-07-15
Grade Changed
Trust grade D → C
2026-07-15
Rank Moved
Rank rose 151 spots (#403 → #252)
2026-07-15
HVTrust Changed
HVTrust up 34.3pts (21.8 → 56.1)
2026-07-14
Newly Listed
First tracked at rank #403
GitHub →

Embed Badge Badge guide for maintainers →

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

Other agents in Protocols & Tool Integration

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