MCPJungle
Website
One place to manage & connect to all your MCP servers
Is MCPJungle safe? Thin or incomplete trust evidence. Review carefully before production use.
Compare MCPJungle
How does it stack up against its Protocols & Tool Integration neighbours?
Pick any agent to compare →In detail: MCPJungle scores 52.2/100 (Grade C), ranked #952 of 1374 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 3.2/10; 62% of recent commits are signed; last pushed 2026-11-03. Every point is earned from checkable signals — never paid placement. How scoring works →
How MCPJungle could raise its score
Each line changes one public signal and recomputes with the live scoring function. The gains don't add up exactly, because the score is capped near the top.
- Raise the OSSF Scorecard from 3.2 to 9.0lowest checks: CI-Tests 0, CII-Best-Practices 0, Dependency-Update-Tool 0 +12.2 → 64.4 C · #34 of 63
- Sign every commit62% signed today +1.9 → 54.1 C · #46 of 63
Chain of custody
Scanners check what the code says. This traces who ships MCPJungle and whether that has changed: from the source repository, through how changes are reviewed and released, to the code you run. These are the checks for OWASP ASI04 Agentic Supply Chain Vulnerabilities.
-
Source Partly signed
github.com/mcpjungle/MCPJungle, MPL-2.0, last pushed 2026-11-03. 62% of the last 100 commits carry a verified signature; the rest can't be tied to a verified identity.
-
Review and release Weak
OpenSSF Scorecard rates the repository's practices 3.2/10 (scanned Nov 2, 2026). The checks that decide who can get a change released:
- Code Review1
- Branch Protection3
- Signed Releases8
- Dangerous Workflown/a
- Token Permissionsn/a
- Pinned Dependencies2
All 18 Scorecard checks
Binary-Artifacts 10Branch-Protection 3CI-Tests 0CII-Best-Practices 0Code-Review 1Contributors 10Dangerous-Workflow -1Dependency-Update-Tool 0Fuzzing 0License 10Maintained 5Packaging -1Pinned-Dependencies 2SAST 0Security-Policy 0Signed-Releases 8Token-Permissions -1Vulnerabilities 0 -
Published packages None
No registry package. MCPJungle is used from its repository, so what you run is whatever you check out: pin a release tag or commit.
Changes to this chain
- 2026-09-01 OSSF Scorecard: 3.3/10
Evidence behind this score
Coverage C: 2 of 5 independent evidence types found.
- GitHub repository data
- Package downloads (missing)
- Supply-chain checks
- Public actions (missing)
- Community mentions (missing)
Verify this score yourself
Every build re-issues MCPJungle’s score as an Ed25519-signed credential, valid for 7 days. You can check it offline against HVTracker’s published key; if anyone changes a number after signing, verification fails.
What this score doesn’t check
It covers who ships the code, not what the code does. It doesn’t read tool descriptions or prompts for injected instructions, watch runtime behaviour, or find bugs nobody has disclosed yet. For that, run a content scanner before you connect it, such as Cisco MCP Scanner or Snyk Agent Scan.
How MCPJungle compares in Protocols & Tool Integration
- #47 Figma Context MCP 53.5 +1.3
- #48 wcgw 53.2 +1.0
- #49 MCPJungle 52.2 this agent
- #50 FastAPI-MCP 51.2 −1.0
- #51 golf 48.8 −3.4
Bars show each HVTrust score; the tick marks MCPJungle’s 52.2.
Where the 52.2 comes from
HVTrust dimensions vs the Protocols & Tool Integration average
52.2 / 100 · 100.0% confidenceMCPJungle Protocols & Tool Integration average (63 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
64.5 / 100Common questions about MCPJungle
Does MCPJungle publish package provenance?
Does MCPJungle have an OpenSSF Scorecard?
Is MCPJungle actively maintained?
What license does MCPJungle use?
Are MCPJungle'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 MCPJungle'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 MCPJungle?
For maintainers
HVTrust scores MCPJungle 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/mcpjungle)
<a href="https://hvtracker.net/agents/mcpjungle"><img src="https://hvtracker.net/badge/mcpjungle.svg" alt="HVTrust"></a>
Other agents in Protocols & Tool Integration
GitHub REST API (repo, commits, stars, forks, license) · OpenSSF Scorecard CLI
Each agent's signals refresh once daily across 6 staggered batches. Methodology v4.4 · Raw JSON