Trust and health report
MCPJungle - trust report
Sourced, dated trust signals - maintenance label posture, repository provenance, and security scan status. Not a composite safety grade.
GraphCanon updated Oct 4, 2026 · GitHub synced Sep 20, 2026
40views this month
Maintenance
Recency and activity heuristics from public GitHub metadata (maintenance label, momentum); methodology: github_public_v1.
Steady60% signal
last push 48d ago · last release Aug 2, 2026 · 1 releases (90d)
+97 stars (30d) · +14 open issues (30d)
Provenance
Repository identity and fork provenance (github_public_v1).
- GitHub repo id: 984119889
- Not a fork
- Verified publisher: organization account
- Computed Sep 20, 2026
Security intelligence
Source-by-source security scan results from public intelligence providers. Missing, partial, or failed queries are shown explicitly and are not treated as clean.
OSV dependency advisories
Published findings- Last query
- Oct 4, 2026
- Scanner
- osv@v1
- Stored findings
- 64
OpenSSF Scorecard
Not queried- Scanner
- openssf-scorecard@v1
Weekly public scans omit some checks at scale.
View source evidenceDependency advisories (deduplicated)
GHSA-fw7p-63qq-7hpr
filippo.io/edwards25519@v1.1.0 · osv@v1
go.sum
GO-2026-4503
filippo.io/edwards25519@v1.1.0 · osv@v1
go.sum
GHSA-9jj7-4m8r-rfcm
github.com/jackc/pgx/v5@v5.7.5 · osv@v1
go.sum
GHSA-j88v-2chj-qfwx
github.com/jackc/pgx/v5@v5.7.5 · osv@v1
go.sum
GHSA-xgrm-4fwx-7qm8
github.com/jackc/pgx/v5@v5.7.5 · osv@v1
go.sum
GO-2026-4771
github.com/jackc/pgx/v5@v5.7.5 · osv@v1
go.sum
GO-2026-4772
github.com/jackc/pgx/v5@v5.7.5 · osv@v1
go.sum
GO-2026-5004
github.com/jackc/pgx/v5@v5.7.5 · osv@v1
go.sum
GHSA-mh2q-q3fh-2475
go.opentelemetry.io/otel@v1.38.0 · osv@v1
go.sum
GO-2026-5506
go.opentelemetry.io/otel@v1.38.0 · osv@v1
go.sum
GHSA-8wmf-6v46-5gfg
go.opentelemetry.io/otel/sdk@v1.38.0 · osv@v1
go.sum
GHSA-9h8m-3fm2-qjrq
go.opentelemetry.io/otel/sdk@v1.38.0 · osv@v1
go.sum
GHSA-hfvc-g4fc-pqhx
go.opentelemetry.io/otel/sdk@v1.38.0 · osv@v1
go.sum
GO-2026-4394
go.opentelemetry.io/otel/sdk@v1.38.0 · osv@v1
go.sum
GO-2026-5426
go.opentelemetry.io/otel/sdk@v1.38.0 · osv@v1
go.sum
GO-2026-6505
go.opentelemetry.io/otel/sdk@v1.38.0 · osv@v1
go.sum
GHSA-45gg-vh54-h5m9
golang.org/x/crypto@v0.41.0 · osv@v1
go.sum
GHSA-5cgq-3rg8-m6cv
golang.org/x/crypto@v0.41.0 · osv@v1
go.sum
GHSA-78mq-xcr3-xm33
golang.org/x/crypto@v0.41.0 · osv@v1
go.sum
GHSA-89gr-r52h-f8rx
golang.org/x/crypto@v0.41.0 · osv@v1
go.sum
GHSA-9m57-25v3-79x9
golang.org/x/crypto@v0.41.0 · osv@v1
go.sum
GHSA-f5wc-c3c7-36mc
golang.org/x/crypto@v0.41.0 · osv@v1
go.sum
GHSA-f6x5-jh6r-wrfv
golang.org/x/crypto@v0.41.0 · osv@v1
go.sum
GHSA-j5w8-q4qc-rx2x
golang.org/x/crypto@v0.41.0 · osv@v1
go.sum
GHSA-jppx-rxg9-jmrx
golang.org/x/crypto@v0.41.0 · osv@v1
go.sum
GHSA-q4h4-gmj2-qvw2
golang.org/x/crypto@v0.41.0 · osv@v1
go.sum
GHSA-qpw4-5x99-6vjp
golang.org/x/crypto@v0.41.0 · osv@v1
go.sum
GHSA-rm3j-f69w-wqmq
golang.org/x/crypto@v0.41.0 · osv@v1
go.sum
GHSA-vgwf-h737-ff37
golang.org/x/crypto@v0.41.0 · osv@v1
go.sum
GHSA-w879-237q-wc7r
golang.org/x/crypto@v0.41.0 · osv@v1
go.sum
GHSA-x527-x647-q7gg
golang.org/x/crypto@v0.41.0 · osv@v1
go.sum
GO-2025-4116
golang.org/x/crypto@v0.41.0 · osv@v1
go.sum
GO-2025-4134
golang.org/x/crypto@v0.41.0 · osv@v1
go.sum
GO-2025-4135
golang.org/x/crypto@v0.41.0 · osv@v1
go.sum
GO-2026-5005
golang.org/x/crypto@v0.41.0 · osv@v1
go.sum
GO-2026-5006
golang.org/x/crypto@v0.41.0 · osv@v1
go.sum
GO-2026-5013
golang.org/x/crypto@v0.41.0 · osv@v1
go.sum
GO-2026-5014
golang.org/x/crypto@v0.41.0 · osv@v1
go.sum
GO-2026-5015
golang.org/x/crypto@v0.41.0 · osv@v1
go.sum
GO-2026-5016
golang.org/x/crypto@v0.41.0 · osv@v1
go.sum
GO-2026-5017
golang.org/x/crypto@v0.41.0 · osv@v1
go.sum
GO-2026-5018
golang.org/x/crypto@v0.41.0 · osv@v1
go.sum
GO-2026-5019
golang.org/x/crypto@v0.41.0 · osv@v1
go.sum
GO-2026-5020
golang.org/x/crypto@v0.41.0 · osv@v1
go.sum
GO-2026-5021
golang.org/x/crypto@v0.41.0 · osv@v1
go.sum
GO-2026-5023
golang.org/x/crypto@v0.41.0 · osv@v1
go.sum
GO-2026-5033
golang.org/x/crypto@v0.41.0 · osv@v1
go.sum
GO-2026-5932
golang.org/x/crypto@v0.41.0 · osv@v1
go.sum
GO-2026-6303
golang.org/x/crypto@v0.41.0 · osv@v1
go.sum
GO-2026-6354
golang.org/x/crypto@v0.41.0 · osv@v1
go.sum
GO-2026-6355
golang.org/x/crypto@v0.41.0 · osv@v1
go.sum
GHSA-5cv4-jp36-h3mw
golang.org/x/net@v0.43.0 · osv@v1
go.sum
GO-2026-4440
golang.org/x/net@v0.43.0 · osv@v1
go.sum
GO-2026-4441
golang.org/x/net@v0.43.0 · osv@v1
go.sum
GO-2026-4918
golang.org/x/net@v0.43.0 · osv@v1
go.sum
GO-2026-5025
golang.org/x/net@v0.43.0 · osv@v1
go.sum
GO-2026-5026
golang.org/x/net@v0.43.0 · osv@v1
go.sum
GO-2026-5027
golang.org/x/net@v0.43.0 · osv@v1
go.sum
GO-2026-5028
golang.org/x/net@v0.43.0 · osv@v1
go.sum
GO-2026-5029
golang.org/x/net@v0.43.0 · osv@v1
go.sum
GO-2026-5030
golang.org/x/net@v0.43.0 · osv@v1
go.sum
GO-2026-5942
golang.org/x/net@v0.43.0 · osv@v1
go.sum
GO-2026-5024
golang.org/x/sys@v0.35.0 · osv@v1
go.sum
GO-2026-5970
golang.org/x/text@v0.28.0 · osv@v1
go.sum
Method and caveats: these are sourced, dated heuristics from public GitHub data and external security intelligence providers. A status like "no published findings from this source" is not a guarantee of safety. Read the full trust methodology · JSON report at /api/graphcanon/tools/mcpjungle-mcpjungle/trust.
Common questions
- Is MCPJungle maintained?
- GraphCanon rates MCPJungle "Steady" (60% maintenance signal from public GitHub metadata, computed Sep 20, 2026). Last push was 48 days ago. 1 GitHub releases in the last 90 days. This is a recency heuristic, not a guarantee the project will stay maintained.
- Is MCPJungle safe to use?
- Last scanned Oct 4, 2026 (deps profile). Status: 64 low - 64 low finding(s) in the latest scan. GraphCanon does not claim the project is safe or vulnerability-free; review findings on the trust report. GraphCanon does not certify MCPJungle as safe - review maintenance, provenance, and scan findings on this page before adopting.
- Is MCPJungle a fork?
- No. MCPJungle is not flagged as a fork in GitHub metadata at the time of the last refresh.
- Does MCPJungle have known security vulnerabilities?
- Last scanned Oct 4, 2026 (deps profile). Status: 64 low - 64 low finding(s) in the latest scan. GraphCanon does not claim the project is safe or vulnerability-free; review findings on the trust report.
- How often is the MCPJungle trust report updated?
- Trust signals refresh on GitHub ingest/refresh cycles and optional dependency/MCP scans. This report was computed Sep 20, 2026 (methodology github_public_v1).
- What does GraphCanon never claim about MCPJungle?
- We never publish a composite safety grade, pen-test endorsement, or "verified secure" label for MCPJungle. Signals are sourced heuristics with explicit limits - see trust methodology.
- How does GraphCanon assess trust for MCPJungle?
- Signals are sourced from public GitHub metadata and optional dependency/MCP manifest scans, each tagged with methodology version and computed date. GraphCanon does not publish a composite safety grade. Read trust methodology for full scope and limits.