Loading the registry…
Multitenant Streamable HTTP bridge over Nutanix's official v4 API MCP server (stdio)
The publisher performed an authenticated act of publication — proving control of a namespace in the official MCP registry, or appearing in a first-party catalogue an operator curates. That establishes WHO published it. It is not a security finding, and attested artifacts carry Flagged verdicts too.
1 critical finding reported by agent-audit-kit. The composite score alone does not reflect this — read the per-scanner reports below.
github: https://github.com/wyre-technology/nutanix-mcp, 16 findings
Choose your runtime: the CLI writes the mcpServers config entry for that target.
nerlo install --target claude-code -- @wyre-technology/nutanix-mcp
Install respects the composite badge: Clean proceeds, Caution prompts for confirmation, and Flagged is refused. Write operations require an API token.
5 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
10 findings · 7.5s
v0.3.74
4 findings · 1.3s
v0.1.0
1 finding · 3.3s
v0.1.0
0 findings · 3.3s
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 · 1.9s
No report in this scan: govulncheck, osv-scanner, trivy, trivy_image.
1 scan on record. Every scan's full results are retained immutably for 24 months.
| Completed | Composite | Change | Scanners | Status |
|---|---|---|---|---|
| Aug 20, 2026 | Scan Halted | — | agentshield: completecisco-skill-scanner: completeagent-audit-kit: completenerlo-behavioral: completenerlo-install-instruction: completecapslock ·n/a: not applicablenerlo-multi-source ·n/a: not applicable | rejected |
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 15 findings across every scanner that examined this package. None of the 1 finding rated critical by their scanner were dismissed.
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.
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.
7 Test or fixture file — The match is in a test or fixture. Our own check confirmed the file is not part of what gets installed.
Rules: opt.nerlo-rules.nerlo-js-secret-to-network-egress, DATA_EXFIL_JS_NETWORK · Files: /repo/src/__tests__/http-gate.test.ts · reported by nerlo-behavioral, cisco-skill-scanner
The model could have called any of these a false positive and did not.
1 AAK-MCP-018
Files: src/http.ts · reported by agent-audit-kit
1 AAK-MCP-STDIO-CMD-INJ-002
Files: src/pool.ts · reported by agent-audit-kit
1 AAK-SUPPLY-005
Files: package-lock.json · reported by agent-audit-kit
1 LOW_ANALYZABILITY
Files: /repo · reported by cisco-skill-scanner
4 The model called these false positives and our own check did not agree, so the dismissal was refused.
Rules: AAK-SEC-MD-001, HIDDEN_DATA_FILE, SOCIAL_ENG_VAGUE_DESCRIPTION and 1 more · Files: SECURITY.md, /repo/.releaserc.json, /repo/SKILL.md · reported by agent-audit-kit, cisco-skill-scanner
Critical command injection vulnerability identified
The artifact contains a critical command injection vulnerability in `src/pool.ts`, which could allow for shell execution. Additionally, a medium severity finding from the Bearer scanner suggests potential sensitive data handling concerns. Another medium severity finding from Agent Audit Kit indicates a process control risk. Low severity findings also point to security misconfiguration and the presence of hidden data files.
Concern level assessed by the review: Critical. 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.