Genesys Cloud MCP Plus - Advanced Model Context Protocol server with 15 comprehensive tools for contact center analytics, real-time monitoring, and wrap-up code analysis. Enhanced with multi-media support and enterprise-grade features.
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.
6 critical findings reported by cisco-skill-scanner, agent-audit-kit, trivy, osv-scanner, 3 of them in the installed artifact. The composite score alone does not reflect this — read the per-scanner reports below.
npm: genesys-cloud-mcp-plus @ 1.0.0, 0 findings
Choose your runtime: the CLI writes the mcpServers config entry for that target.
nerlo install --target claude-code -- genesys-cloud-mcp-plus
Install respects the composite badge: Clean proceeds, Caution prompts for confirmation, and Flagged is refused. Write operations require an API token.
8 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
7 findings · 8.7s
v0.3.74
20 findings · 2.7s
v0.1.0
0 findings · 3.5s
v0.1.0
0 findings · 3.5s
v0.1.0
0 findings · 7.8s
v0.71.0
49 findings · 0.3s
v2.3.8
93 findings · 7.4s
vv0.3.2
No Go packages were found in this artifact. What each scanner covers
0 findings · 0.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 | Flagged43 | — | agentshield: completecisco-skill-scanner: completeagent-audit-kit: completenerlo-behavioral: completenerlo-install-instruction: completecapslock ·n/a: not applicablenerlo-multi-source: completetrivy: 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 169 findings across every scanner that examined this package. None of the 6 findings rated critical by their scanner were dismissed.
Not reviewed is not the same as clean. Those 124 findings stand exactly as their scanners reported them, at full severity, as they would have without this review.
Two keys had to turn. The model had to name a reason from a fixed list of six, and a deterministic check of ours — over which files this artifact actually installs — had to independently agree. Anything it could not corroborate is in “not reviewed” above, at full severity.
2 Documentation or example — The match is in documentation or sample code, confirmed by our own check to be outside the installed artifact.
Rules: SOCIAL_ENG_VAGUE_DESCRIPTION, MANIFEST_MISSING_LICENSE · Files: /repo/docs/SKILL.md · reported by cisco-skill-scanner
The model could have called any of these a false positive and did not.
2 CVE-2025-69873
Files: package-lock.json · reported by trivy
2 GHSA-2g4f-4pwh-qvx6
Files: /repo/package-lock.json · reported by osv-scanner
2 GHSA-f886-m6hf-6m8v
Files: /repo/package-lock.json · reported by osv-scanner
2 GHSA-r4q5-vmmm-2653
Files: package-lock.json, /repo/package-lock.json · reported by trivy, osv-scanner
1 AAK-OAUTH-3P-001
Files: package.json · reported by agent-audit-kit
1 AAK-SUPPLY-005
Files: package-lock.json · reported by agent-audit-kit
1 CVE-2025-13466
Files: package-lock.json · reported by trivy
1 CVE-2025-15284
Files: package-lock.json · reported by trivy
1 CVE-2025-62718
Files: package-lock.json · reported by trivy
1 CVE-2026-12590
Files: package-lock.json · reported by trivy
1 CVE-2026-2391
Files: package-lock.json · reported by trivy
1 CVE-2026-42034
Files: package-lock.json · reported by trivy
1 CVE-2026-42040
Files: package-lock.json · reported by trivy
1 CVE-2026-8723
Files: package-lock.json · reported by trivy
1 GHSA-3p68-rc4w-qgx5
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-3w6x-2g7m-8v23
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-42h9-826w-cgv3
Files: package-lock.json · reported by trivy
1 GHSA-48c2-rrv3-qjmp
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-4w7w-66w2-5vf9
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-5c9x-8gcm-mpgx
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-6rw7-vpxm-498p
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-7q8q-rj6j-mhjq
Files: package-lock.json · reported by trivy
1 GHSA-898c-q2cr-xwhg
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-fvcv-3m26-pcqx
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-fxqj-rqcc-2cmp
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-g4jq-h2w9-997c
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-h67p-54hq-rp68
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-jqfw-vq24-v9c3
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-jqh4-m9w3-8hp9
Files: package-lock.json · reported by trivy
1 GHSA-mh29-5h37-fv8m
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-mmx7-hfxf-jppx
Files: package-lock.json · reported by trivy
1 GHSA-qx2v-qp2m-jg93
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-v422-hmwv-36x6
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-v6wh-96g9-6wx3
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-w7fw-mjwx-w883
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-xffm-g5w8-qvg7
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-xhjh-pmcv-23jw
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-xx6v-rp6x-q39c
Files: /repo/package-lock.json · reported by osv-scanner
1 LOW_ANALYZABILITY
Files: /repo · reported by cisco-skill-scanner
121 The model's answer could not be read.
Rules: COMMAND_INJECTION_JS_CHILD_PROCESS, GHSA-5xrq-8626-4rwp, GHSA-fjxv-7rqg-78g4 and 94 more · Files: /repo/tests/serverRuns.test.ts, /repo/package-lock.json, package-lock.json and 13 more · reported by cisco-skill-scanner, osv-scanner, trivy and 1 more
3 The model called these false positives and our own check did not agree, so the dismissal was refused.
Rules: AAK-SEC-MD-001, SOCIAL_ENG_VAGUE_DESCRIPTION, MANIFEST_MISSING_LICENSE · Files: SECURITY.md, /repo/SKILL.md · reported by agent-audit-kit, cisco-skill-scanner
Critical vulnerabilities and command injection risks identified.
The artifact contains critical vulnerabilities in its dependencies, identified by `osv-scanner` and `trivy`, which could lead to various security compromises. It also includes code susceptible to command injection in `tests/serverRuns.test.ts`, potentially allowing shell execution. Furthermore, high-severity findings indicate potential credential exposure in `start-mcp.sh` and numerous other vulnerabilities in dependencies listed in `package-lock.json` and `package.json`.
Concern level assessed by the review: Critical. This is the review's scale, not the registry badge.
Showing 25 of 25; the rest are in the per-scanner reports above.
Reviewed by gemini-2.5-flash. The model sees the findings, not your code, and cannot change a score.