Loading the registry…
Unofficial MCP server for Ganjinex.com cryptocurrency exchange
We found this by crawling public sources and nobody has attested to it. That is how most of the registry gets here, and it is not a mark against the artifact — it only means no authenticated act of publication is on record. An artifact can be the vendor's own and still appear here.
Choose your runtime: the CLI writes the mcpServers config entry for that target.
nerlo install --target claude-code -- ganjinex-mcp
Install respects the composite badge: Clean proceeds, Caution prompts for confirmation, and Flagged is refused. Write operations require an API token.
7 of 11 scanners examined this package. The rest do not apply to it — language, ecosystem and packaging decide which analyzers can say anything, and a scanner that cannot examine an artifact reports nothing rather than passing it.
v1.4.0
0 findings · 0.6s
v2.0.11
17 findings · 7.2s
v0.3.74
3 findings · 0.8s
v0.1.0
26 findings · 3.5s
v0.1.0
0 findings · 3.5s
v0.71.0
29 findings · 0.2s
v2.3.8
29 findings · 7.2s
vv0.3.2
No Go packages were found in this artifact. What each scanner covers
0 findings · 0.1s
v0.1.0
This scanner found nothing in this artifact that it assesses. What each scanner covers
0 findings · 2.1s
v0.71.0
No container image was published for this artifact. What each scanner covers
0 findings · 0.0s
vv1.6.0
No Go modules were found in this artifact. What each scanner covers
0 findings · 0.1s
1 scan on record. Every scan's full results are retained immutably for 24 months.
| Completed | Composite | Change | Scanners | Status |
|---|---|---|---|---|
| Aug 20, 2026 | Flagged38 | — | agentshield: completecisco-skill-scanner: completeagent-audit-kit: completenerlo-behavioral: completenerlo-install-instruction: completecapslock ·n/a: not applicablenerlo-multi-source ·n/a: not applicabletrivy: completeosv-scanner: completetrivy_image ·n/a: not applicablegovulncheck ·n/a: not applicable | completed |
Findings in files this artifact installs stand as reported; a model re-read the rest and said which ones it believes are false positives. This is a second opinion published beside the evidence, not a correction to it: the per-scanner reports above are unchanged, every dismissed finding is still listed there at its original severity, and the score and the Flagged badge are computed from those raw severities alone. Nothing below moved them.
Out of 104 findings across every scanner that examined this package.
Not reviewed is not the same as clean. Those 4 findings stand exactly as their scanners reported them, at full severity, as they would have without this review.
The model could have called any of these a false positive and did not.
14 DATA_EXFIL_JS_NETWORK
Files: /repo/index.ts · reported by cisco-skill-scanner
14 opt.nerlo-rules.nerlo-js-secret-to-network-egress
Files: /repo/index.ts · reported by nerlo-behavioral
12 opt.nerlo-rules.nerlo-hardcoded-external-egress
Files: /repo/index.ts · reported by nerlo-behavioral
1 AAK-MCP-SSRF-001
Files: index.ts · reported by agent-audit-kit
1 AAK-SUPPLY-004
Files: package.json · reported by agent-audit-kit
1 CVE-2025-13466
Files: bun.lock · reported by trivy
1 CVE-2025-15284
Files: bun.lock · reported by trivy
1 CVE-2025-66414
Files: bun.lock · reported by trivy
1 CVE-2025-69873
Files: bun.lock · reported by trivy
1 CVE-2026-0621
Files: bun.lock · reported by trivy
1 CVE-2026-11525
Files: bun.lock · reported by trivy
1 CVE-2026-12151
Files: bun.lock · reported by trivy
1 CVE-2026-12590
Files: bun.lock · reported by trivy
1 CVE-2026-13697
Files: bun.lock · reported by trivy
1 CVE-2026-14643
Files: bun.lock · reported by trivy
1 CVE-2026-15157
Files: bun.lock · reported by trivy
1 CVE-2026-1525
Files: bun.lock · reported by trivy
1 CVE-2026-1526
Files: bun.lock · reported by trivy
1 CVE-2026-1527
Files: bun.lock · reported by trivy
1 CVE-2026-1528
Files: bun.lock · reported by trivy
1 CVE-2026-16728
Files: bun.lock · reported by trivy
1 CVE-2026-16729
Files: bun.lock · reported by trivy
1 CVE-2026-22036
Files: bun.lock · reported by trivy
1 CVE-2026-2229
Files: bun.lock · reported by trivy
1 CVE-2026-2391
Files: bun.lock · reported by trivy
1 CVE-2026-25536
Files: bun.lock · reported by trivy
1 CVE-2026-31808
Files: bun.lock · reported by trivy
1 CVE-2026-32630
Files: bun.lock · reported by trivy
1 CVE-2026-4923
Files: bun.lock · reported by trivy
1 CVE-2026-4926
Files: bun.lock · reported by trivy
1 CVE-2026-6733
Files: bun.lock · reported by trivy
1 CVE-2026-8723
Files: bun.lock · reported by trivy
1 CVE-2026-9678
Files: bun.lock · reported by trivy
1 CVE-2026-9679
Files: bun.lock · reported by trivy
1 GHSA-27v5-c462-wpq7
Files: /repo/bun.lock · reported by osv-scanner
1 GHSA-2g4f-4pwh-qvx6
Files: /repo/bun.lock · reported by osv-scanner
1 GHSA-2mjp-6q6p-2qxm
Files: /repo/bun.lock · reported by osv-scanner
1 GHSA-345p-7cg4-v4c7
Files: /repo/bun.lock · reported by osv-scanner
1 GHSA-35p6-xmwp-9g52
Files: /repo/bun.lock · reported by osv-scanner
1 GHSA-4992-7rv2-5pvq
Files: /repo/bun.lock · reported by osv-scanner
1 GHSA-4cwx-7wf7-3272
Files: /repo/bun.lock · reported by osv-scanner
1 GHSA-5v7r-6r5c-r473
Files: /repo/bun.lock · reported by osv-scanner
1 GHSA-6rw7-vpxm-498p
Files: /repo/bun.lock · reported by osv-scanner
1 GHSA-8r9q-7v3j-jr4g
Files: /repo/bun.lock · reported by osv-scanner
1 GHSA-8xcm-r25x-g524
Files: /repo/bun.lock · reported by osv-scanner
1 GHSA-f269-vfmq-vjvj
Files: /repo/bun.lock · reported by osv-scanner
1 GHSA-g8m3-5g58-fq7m
Files: /repo/bun.lock · reported by osv-scanner
1 GHSA-g9mf-h72j-4rw9
Files: /repo/bun.lock · reported by osv-scanner
1 GHSA-j47w-4g3g-c36v
Files: /repo/bun.lock · reported by osv-scanner
1 GHSA-jr45-8vmc-qm54
Files: /repo/bun.lock · reported by osv-scanner
1 GHSA-m8rv-5g2x-5cg5
Files: /repo/bun.lock · reported by osv-scanner
1 GHSA-p88m-4jfj-68fv
Files: /repo/bun.lock · reported by osv-scanner
1 GHSA-pr7r-676h-xcf6
Files: /repo/bun.lock · reported by osv-scanner
1 GHSA-q8mj-m7cp-5q26
Files: /repo/bun.lock · reported by osv-scanner
1 GHSA-v3r7-h72x-cjcm
Files: /repo/bun.lock · reported by osv-scanner
1 GHSA-v422-hmwv-36x6
Files: /repo/bun.lock · reported by osv-scanner
1 GHSA-v9p9-hfj2-hcw8
Files: /repo/bun.lock · reported by osv-scanner
1 GHSA-vrm6-8vpv-qv8q
Files: /repo/bun.lock · reported by osv-scanner
1 GHSA-vxpw-j846-p89q
Files: /repo/bun.lock · reported by osv-scanner
1 GHSA-w48q-cv73-mx4w
Files: /repo/bun.lock · reported by osv-scanner
1 GHSA-w7fw-mjwx-w883
Files: /repo/bun.lock · reported by osv-scanner
1 GHSA-wqch-xfxh-vrr4
Files: /repo/bun.lock · reported by osv-scanner
1 LOW_ANALYZABILITY
Files: /repo · reported by cisco-skill-scanner
2 The model did not answer for these findings.
Rules: GHSA-j3q9-mxjg-w52f, SOCIAL_ENG_VAGUE_DESCRIPTION · Files: /repo/bun.lock, /repo/SKILL.md · reported by osv-scanner, cisco-skill-scanner
2 The model called these false positives and our own check did not agree, so the dismissal was refused.
Rules: AAK-SEC-MD-001, MANIFEST_MISSING_LICENSE · Files: SECURITY.md, /repo/SKILL.md · reported by agent-audit-kit, cisco-skill-scanner
Artifact accesses secrets, performs network egress, and has dependency vulnerabilities.
The artifact contains code in `/repo/index.ts` that accesses secrets and subsequently performs network egress. Additionally, multiple high and medium severity vulnerabilities are present in dependencies listed in `bun.lock`. These findings indicate potential for sensitive data exposure and compromise through vulnerable components. Attention is warranted for the behavioral finding related to secret access and network egress, as well as the numerous dependency vulnerabilities.
Concern level assessed by the review: High. This is the review's scale, not the registry badge.
Reviewed by gemini-2.5-flash. The model sees the findings, not your code, and cannot change a score.
Showing 25 of 32; the rest are in the per-scanner reports above.