Loading the registry…
A Model Context Protocol server for querying Swagger/OpenAPI JSON documents
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.
1 critical finding reported by osv-scanner. The composite score alone does not reflect this — read the per-scanner reports below.
Choose your runtime: the CLI writes the mcpServers config entry for that target.
nerlo install --target claude-code -- swagger-json-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.8s
v2.0.11
4 findings · 8.8s
v0.3.74
4 findings · 2.4s
v0.1.0
0 findings · 4.5s
v0.1.0
0 findings · 4.5s
v0.71.0
11 findings · 0.2s
v2.3.8
50 findings · 6.8s
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.2s
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 | Flagged49 | — | 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 69 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 30 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.
2 GHSA-23c5-xmqv-rm74
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
2 GHSA-3jxr-9vmj-r5cp
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
2 GHSA-3ppc-4f35-3m26
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
2 GHSA-7r86-cg39-jmmj
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
2 GHSA-c2c7-rcm5-vvqj
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
2 GHSA-mh99-v99m-4gvg
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
2 GHSA-rgw5-rvv9-x895
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 AAK-ANTHROPIC-SDK-001
Files: src/index.ts · reported by agent-audit-kit
1 AAK-DNS-REBIND-002
Files: package.json · reported by agent-audit-kit
1 CVE-2026-12590
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-2391
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-25536
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-4926
Files: pnpm-lock.yaml · reported by trivy
1 GHSA-25h7-pfq9-p65f
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-28wg-ghj8-5hjv
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-2v37-7h3g-55p8
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-345p-7cg4-v4c7
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-52cp-r559-cp3m
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-5xrq-8626-4rwp
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-6g55-p6wh-862q
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-8r9q-7v3j-jr4g
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-fx2h-pf6j-xcff
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-g4jq-h2w9-997c
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-j3q9-mxjg-w52f
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-jqfw-vq24-v9c3
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-mw96-cpmx-2vgc
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-r28c-9q8g-f849
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-rf6f-7fwh-wjgh
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-v422-hmwv-36x6
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-w48q-cv73-mx4w
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-w7fw-mjwx-w883
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 LOW_ANALYZABILITY
Files: /repo · reported by cisco-skill-scanner
26 The model's answer could not be read.
Rules: GHSA-5p4m-2wfm-xmqj, CVE-2026-0621, CVE-2025-66414 and 21 more · Files: /repo/pnpm-lock.yaml, pnpm-lock.yaml, package.json · reported by osv-scanner, trivy, agent-audit-kit
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/.prettierrc.json, /repo/SKILL.md · reported by agent-audit-kit, cisco-skill-scanner
Critical vulnerability and high-risk capabilities detected.
A critical vulnerability (GHSA-5xrq-8626-4rwp) is present in a dependency listed in pnpm-lock.yaml. The artifact also includes capabilities for network egress, potential DNS rebind operations, and integrates an Anthropic SDK in src/index.ts, which may involve credential access. Multiple other high and medium severity vulnerabilities are identified across various dependencies.
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.
Showing 25 of 25; the rest are in the per-scanner reports above.