Loading the registry…
ApiPost MCP - API文档管理工具，支持接口创建、修改、查看和批量操作
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 -- apipost-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
4 findings · 6.8s
v0.3.74
4 findings · 1.1s
v0.1.0
0 findings · 3.9s
v0.1.0
0 findings · 3.9s
v0.71.0
32 findings · 0.2s
v2.3.8
32 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 · 1.8s
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 | Flagged46 | — | 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 72 findings across every scanner that examined this package.
Not reviewed is not the same as clean. Those 47 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-mmx7-hfxf-jppx
Files: package-lock.json, /repo/package-lock.json · reported by trivy, 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 CVE-2025-58754
Files: package-lock.json · reported by trivy
1 CVE-2025-62718
Files: package-lock.json · reported by trivy
1 CVE-2025-66414
Files: package-lock.json · reported by trivy
1 CVE-2026-42034
Files: package-lock.json · reported by trivy
1 CVE-2026-42037
Files: package-lock.json · reported by trivy
1 CVE-2026-42042
Files: package-lock.json · reported by trivy
1 CVE-2026-44488
Files: package-lock.json · reported by trivy
1 GHSA-35jp-ww65-95wh
Files: /repo/package-lock.json · reported by osv-scanner
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-445q-vr5w-6q77
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-6chq-wfr3-2hj9
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-7q8q-rj6j-mhjq
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-898c-q2cr-xwhg
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-jqh4-m9w3-8hp9
Files: package-lock.json · reported by trivy
1 GHSA-pmv8-rq9r-6j72
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-pmwg-cvhr-8vh7
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-vf2m-468p-8v99
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-xx6v-rp6x-q39c
Files: /repo/package-lock.json · reported by osv-scanner
47 The model's answer could not be read.
Rules: GHSA-62hf-57xw-28j9, CVE-2026-42033, GHSA-pf86-5x62-jrwf and 43 more · Files: /repo/package-lock.json, package-lock.json, package.json and 5 more · reported by osv-scanner, trivy, agent-audit-kit and 1 more
High-severity vulnerabilities, including DNS rebinding and AI SDK usage
The artifact exhibits potential for DNS rebinding, as indicated by a high-severity finding in `package.json`. It also utilizes an Anthropic SDK in `src/index.ts`, which typically involves network egress for API communication and may handle credentials. Additionally, multiple high-severity supply chain vulnerabilities are present in the artifact's dependencies, as detailed in `package-lock.json`.
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 31; the rest are in the per-scanner reports above.