MCP server for Hostinger 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.
14 critical findings reported by cisco-skill-scanner, agent-audit-kit. The composite score alone does not reflect this — read the per-scanner reports below.
This artifact ships from 2 sources and their verdicts differ. The worst is github (Flagged). Installing from a cleaner source does not mean the others are safe — check the source you actually install from.
github: https://github.com/hostinger/api-mcp-server, 208 findings
Choose your runtime: the CLI writes the mcpServers config entry for that target.
nerlo install --target claude-code -- hostinger-api-mcp
Install respects the composite badge: Clean proceeds, Caution prompts for confirmation, and Flagged is refused. Write operations require an API token.
6 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
44 findings · 10.1s
v0.3.74
20 findings · 9.7s
v0.1.0
43 findings · 10.9s
v0.1.0
0 findings · 10.9s
v0.1.0
0 findings · 19.8s
vv0.3.2
No Go packages were found in this artifact. What each scanner covers
0 findings · 0.1s
No report in this scan: govulncheck, osv-scanner, trivy, trivy_image.
8 scans 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: complete | rejected |
| Aug 2, 2026 | Scan Halted | — | agentshield: completecisco-skill-scanner: completeagent-audit-kit: completenerlo-behavioral: completenerlo-install-instruction: completenerlo-multi-source: complete | rejected |
| Jul 30, 2026 | Scan Halted | — | cisco-skill-scanner: completeagent-audit-kit: completenerlo-behavioral: completenerlo-install-instruction: completenerlo-multi-source: complete | rejected |
| Jul 21, 2026 | Scan Halted | — | agentshield: completecisco-skill-scanner: completeagent-audit-kit: completenerlo-behavioral: completenerlo-install-instruction: complete | rejected |
| Jul 20, 2026 | Scan Halted | — | agentshield: completecisco-skill-scanner: completeagent-audit-kit: complete | rejected |
| Jul 20, 2026 | Scan Halted | Clean → Flagged | agentshield: completecisco-skill-scanner: completeagent-audit-kit: complete | rejected |
| 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 107 findings across every scanner that examined this package. None of the 14 findings rated critical by their scanner were dismissed.
Not reviewed is not the same as clean. Those 8 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.
5 CI or editor configuration — The match is in build, CI or editor configuration, confirmed by our own check to be outside the installed artifact.
Rules: AAK-GHA-IMMUTABLE-001, MANIFEST_INVALID_NAME, SOCIAL_ENG_VAGUE_DESCRIPTION and 1 more · Files: .github/workflows/build-release.yaml, /repo/.github/ISSUE_TEMPLATE/SKILL.md · reported by agent-audit-kit, cisco-skill-scanner
The model could have called any of these a false positive and did not.
41 opt.nerlo-rules.nerlo-js-secret-to-network-egress
Files: /repo/src/core/oauth.js, /repo/src/core/oauth.ts, /repo/src/core/runtime.js and 1 more · reported by nerlo-behavioral
9 DATA_EXFIL_JS_NETWORK
Files: /repo/src/core/oauth.js, /repo/src/core/oauth.ts, /repo/src/core/runtime.js and 1 more · reported by cisco-skill-scanner
8 FILE_MAGIC_MISMATCH
Files: /repo/src/servers/domains.ts, /repo/src/servers/vps.ts, /repo/src/servers/hosting.ts and 5 more · reported by cisco-skill-scanner
6 COMMAND_INJECTION_JS_CHILD_PROCESS
Files: /repo/skills/headless/entry/bootstrap.mjs, /repo/build.js, /repo/src/core/oauth.ts and 1 more · reported by cisco-skill-scanner
6 DATA_EXFIL_JS_FS_ACCESS
Files: /repo/src/core/runtime.js, /repo/src/core/runtime.ts, /repo/build.js · reported by cisco-skill-scanner
3 COMMAND_INJECTION_EVAL
8 The model called these false positives and our own check did not agree, so the dismissal was refused.
Rules: AAK-SECRET-006, AAK-SEC-MD-001, MANIFEST_MISSING_LICENSE and 1 more · Files: .env.example, SECURITY.md, /repo/skills/headless/SKILL.md and 3 more · reported by agent-audit-kit, cisco-skill-scanner
Critical command injection and dynamic execution risks
The artifact contains critical command injection vulnerabilities in `build.js`, `bootstrap.mjs`, and `oauth.js/ts`, which could lead to shell execution. Dynamic code execution via `eval` is also present in `build.js` and `oauth.js/ts`. Critical findings also indicate potential DNS rebinding and standard I/O command injection in `runtime.js/ts`, alongside data tainting in `oauth.ts`. High severity findings further highlight secret exposure leading to network egress and additional dynamic execution.
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.
3 LOW_ANALYZABILITY
Files: /repo/skills/headless, /repo, /repo/skills/headless/entry · reported by cisco-skill-scanner
2 AAK-DNS-REBIND-001
Files: src/core/runtime.ts, src/core/runtime.js · reported by agent-audit-kit
2 AAK-MCP-HTTP-NOAUTH-SERVER-001
Files: src/core/runtime.ts, src/core/runtime.js · reported by agent-audit-kit
2 AAK-MCP-STDIO-CMD-INJ-002
Files: src/core/runtime.ts, src/core/runtime.js · reported by agent-audit-kit
2 AAK-OAUTH-006
Files: src/core/oauth.js, src/core/oauth.ts · reported by agent-audit-kit
2 AAK-OAUTH-007
Files: src/core/oauth.js, src/core/oauth.ts · reported by agent-audit-kit
2 AAK-OAUTH-008
Files: src/core/runtime.ts, src/core/runtime.js · reported by agent-audit-kit
2 opt.nerlo-rules.nerlo-dynamic-exec
Files: /repo/src/core/oauth.js, /repo/src/core/oauth.ts · reported by nerlo-behavioral
1 AAK-DNS-REBIND-002
Files: package.json · reported by agent-audit-kit
1 AAK-OAUTH-3P-001
Files: package.json · reported by agent-audit-kit
1 AAK-TAINT-001
Files: src/core/oauth.ts · reported by agent-audit-kit
1 AAK-TAINT-003
Files: src/core/oauth.ts · reported by agent-audit-kit
Showing 18 of 18; the rest are in the per-scanner reports above.