Chargebee AgentKit Repository (Deprecated - see https://www.chargebee.com/docs/billing/2.0/ai-in-chargebee/chargebee-mcp)
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 -- @chargebee/agentkit-repo
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.5s
v2.0.11
21 findings · 6.6s
v0.3.74
1 finding · 1.9s
v0.2.0
0 findings · 3.4s
v0.2.0
0 findings · 3.4s
v0.71.0
13 findings · 0.2s
v2.3.8
33 findings · 6.4s
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.0s
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
6 scans on record. Every scan's full results are retained immutably for 24 months.
| Completed | Composite | Change | Scanners | Status |
|---|---|---|---|---|
| Sep 11, 2026 | Flagged50 | — | 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 |
| Jul 21, 2026 | Flagged46 | — | agentshield: completecisco-skill-scanner: completeagent-audit-kit: completenerlo-behavioral: completenerlo-install-instruction: completetrivy: completeosv-scanner: complete | completed |
| Jul 20, 2026 | Flagged39 | Clean → Flagged | agentshield: completecisco-skill-scanner: completeagent-audit-kit: completetrivy: completeosv-scanner: complete | completed |
| Jul 20, 2026 | Clean100 | — | agentshield ·n/a: not applicablecisco-skill-scanner ·n/a: not applicableagent-audit-kit: completetrivy: completeosv-scanner ·n/a: not applicable | completed |
| Jul 20, 2026 | Clean100 | — | agentshield ·n/a: not applicablecisco-skill-scanner ·n/a: not applicableagent-audit-kit: completetrivy: completeosv-scanner ·n/a: not applicable | completed |
| Jul 20, 2026 | Clean100 | — | agentshield ·n/a: not applicablecisco-skill-scanner ·n/a: not applicableagent-audit-kit: completetrivy: completeosv-scanner ·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 68 findings across every scanner that examined this package.
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.
3 Agent instruction file — The match is in a file that instructs an AI coding agent — a CLAUDE.md or similar. It is documentation of intent, and our own check confirmed it is not part of what gets installed.
Rules: SOCIAL_ENG_VAGUE_DESCRIPTION, MANIFEST_INVALID_NAME, MANIFEST_MISSING_LICENSE · Files: /repo/.github/SKILL.md · reported by cisco-skill-scanner
These findings are in files this artifact installs and are not placeholder values. No false-positive basis can be corroborated for such a finding, so this review never dismisses one; they were not sent to the model and stand at their scanner's severity.
4 HIDDEN_DATA_FILE
Files: /repo/modelcontextprotocol/.env.production, /repo/modelcontextprotocol/.env.development · reported by cisco-skill-scanner
2 CVE-2025-15284
Files: modelcontextprotocol/pnpm-lock.yaml · reported by trivy
2 CVE-2026-2391
Files: modelcontextprotocol/pnpm-lock.yaml · reported by trivy
2 CVE-2026-82417
Files: modelcontextprotocol/pnpm-lock.yaml · reported by trivy
2 CVE-2026-8723
Files: modelcontextprotocol/pnpm-lock.yaml · reported by trivy
2 DATA_EXFIL_JS_FS_ACCESS
Files: /repo/modelcontextprotocol/tsup.config.ts · reported by cisco-skill-scanner
2 DATA_EXFIL_JS_NETWORK
Files: /repo/modelcontextprotocol/src/chargebee-ai-client/index.ts · reported by cisco-skill-scanner
Multiple high-severity vulnerabilities in dependencies
This artifact contains numerous high-severity vulnerabilities within its dependencies, as identified by `osv-scanner` and `trivy`. These include issues like GHSA-7r86-cg39-jmmj, GHSA-mh99-v99m-4gvg, and CVE-2026-4926, primarily located in the `pnpm-lock.yaml` file. Such vulnerabilities could introduce risks including remote code execution, denial of service, or information disclosure, depending on the specific flaw. Further review of these findings is recommended to understand their potential impact on the artifact's operation.
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.
2 GHSA-23c5-xmqv-rm74
Files: /repo/modelcontextprotocol/pnpm-lock.yaml · reported by osv-scanner
2 GHSA-3jxr-9vmj-r5cp
Files: /repo/modelcontextprotocol/pnpm-lock.yaml · reported by osv-scanner
2 GHSA-3ppc-4f35-3m26
Files: /repo/modelcontextprotocol/pnpm-lock.yaml · reported by osv-scanner
2 GHSA-4mjr-xmp4-gh2g
Files: /repo/modelcontextprotocol/pnpm-lock.yaml · reported by osv-scanner
2 GHSA-6rw7-vpxm-498p
Files: /repo/modelcontextprotocol/pnpm-lock.yaml · reported by osv-scanner
2 GHSA-7r86-cg39-jmmj
Files: /repo/modelcontextprotocol/pnpm-lock.yaml · reported by osv-scanner
2 GHSA-f886-m6hf-6m8v
Files: /repo/modelcontextprotocol/pnpm-lock.yaml · reported by osv-scanner
2 GHSA-mh99-v99m-4gvg
Files: /repo/modelcontextprotocol/pnpm-lock.yaml · reported by osv-scanner
2 GHSA-q8mj-m7cp-5q26
Files: /repo/modelcontextprotocol/pnpm-lock.yaml · reported by osv-scanner
2 GHSA-rgw5-rvv9-x895
Files: /repo/modelcontextprotocol/pnpm-lock.yaml · reported by osv-scanner
2 GHSA-v6h2-p8h4-qcjw
Files: /repo/modelcontextprotocol/pnpm-lock.yaml · reported by osv-scanner
2 GHSA-w7fw-mjwx-w883
Files: /repo/modelcontextprotocol/pnpm-lock.yaml · reported by osv-scanner
2 LOW_ANALYZABILITY
Files: /repo/modelcontextprotocol, /repo · reported by cisco-skill-scanner
2 MANIFEST_MISSING_LICENSE
Files: /repo/SKILL.md, /repo/modelcontextprotocol/SKILL.md · reported by cisco-skill-scanner
2 SOCIAL_ENG_VAGUE_DESCRIPTION
Files: /repo/SKILL.md, /repo/modelcontextprotocol/SKILL.md · reported by cisco-skill-scanner
1 AAK-MCP-018
Files: modelcontextprotocol/src/mcp.ts · reported by agent-audit-kit
1 BINARY_FILE_DETECTED
Files: /repo/media/mcp-cursor-demo.mp4 · reported by cisco-skill-scanner
1 CVE-2025-66414
Files: modelcontextprotocol/pnpm-lock.yaml · reported by trivy
1 CVE-2026-0621
Files: modelcontextprotocol/pnpm-lock.yaml · reported by trivy
1 CVE-2026-12590
Files: modelcontextprotocol/pnpm-lock.yaml · reported by trivy
1 CVE-2026-4923
Files: modelcontextprotocol/pnpm-lock.yaml · reported by trivy
1 CVE-2026-4926
Files: modelcontextprotocol/pnpm-lock.yaml · reported by trivy
1 GHSA-27v5-c462-wpq7
Files: /repo/modelcontextprotocol/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-3v7f-55p6-f55p
Files: /repo/modelcontextprotocol/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-5j98-mcp5-4vw2
Files: /repo/modelcontextprotocol/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-8r9q-7v3j-jr4g
Files: /repo/modelcontextprotocol/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-c2c7-rcm5-vvqj
Files: /repo/modelcontextprotocol/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-j3q9-mxjg-w52f
Files: /repo/modelcontextprotocol/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-mw96-cpmx-2vgc
Files: /repo/modelcontextprotocol/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-v422-hmwv-36x6
Files: /repo/modelcontextprotocol/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-w48q-cv73-mx4w
Files: /repo/modelcontextprotocol/pnpm-lock.yaml · reported by osv-scanner
1 OVERSIZED_FILE
Files: /repo/media/mcp-demo.gif · reported by cisco-skill-scanner
1 UNANALYZABLE_BINARY
Files: /repo/media/mcp-cursor-demo.mp4 · reported by cisco-skill-scanner
1 YARA_prompt_injection_unicode_steganography
Files: /repo/media/mcp-demo.gif · reported by cisco-skill-scanner