Loading the registry…
MCP server for creating HTML forms and collecting responses
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.
3 critical findings reported by cisco-skill-scanner, agent-audit-kit, 2 of them in the installed artifact. 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 -- mcp-form-server
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
4 findings · 7.8s
v0.3.74
25 findings · 1.3s
v0.1.0
0 findings · 3.2s
v0.1.0
0 findings · 3.2s
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.1s
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 29 findings across every scanner that examined this package. None of the 3 findings rated critical by their scanner were dismissed.
Not reviewed is not the same as clean. Those 29 findings stand exactly as their scanners reported them, at full severity, as they would have without this review.
29 The model's answer could not be read.
Rules: AAK-DNS-REBIND-001, COMMAND_INJECTION_JS_CHILD_PROCESS, AAK-AGENT-002 and 10 more · Files: test/mcp-server.test.ts, /repo/tcp-bridge.js, src/mcp-server.ts and 5 more · reported by agent-audit-kit, cisco-skill-scanner
Critical risks: shell execution, network egress, and DNS rebinding
The artifact contains critical findings related to shell execution in `/repo/tcp-bridge.js`, allowing arbitrary command execution. Network egress is also identified as a critical risk in `/repo/tcp-bridge.js`. Additionally, DNS rebinding vulnerabilities are present in `src/mcp-server.ts`, which could lead to unauthorized access or data manipulation. High severity findings include potential unauthenticated server access and stateless server operations in `src/mcp-server.ts`.
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 22 of 22; the rest are in the per-scanner reports above.