MCP server for stacktr.ee — publish HTML artifacts from agents.
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.
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/stevysmith/stacktree-mcp, 17 findings
Choose your runtime: the CLI writes the mcpServers config entry for that target.
nerlo install --target claude-code -- stacktree-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.6s
v2.0.11
7 findings · 8.4s
v0.3.74
8 findings · 1.1s
v0.1.0
2 findings · 3.8s
v0.1.0
0 findings · 3.8s
v0.1.0
0 findings · 8.3s
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.
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: complete | 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 17 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 6 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 DATA_EXFIL_JS_NETWORK
Files: /repo/src/index.ts · reported by cisco-skill-scanner
2 opt.nerlo-rules.nerlo-js-secret-to-network-egress
Files: /repo/src/index.ts · reported by nerlo-behavioral
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 AAK-MCP-001
Files: .mcp.json · reported by agent-audit-kit
1 AAK-MCP-ATTEST-001
Files: .mcp.json · reported by agent-audit-kit
1 AAK-OAUTH-3P-001
Files: package.json · reported by agent-audit-kit
1 AAK-SUPPLY-004
Files: package.json · reported by agent-audit-kit
1 LOW_ANALYZABILITY
Files: /repo · reported by cisco-skill-scanner
3 The model called these false positives and our own check did not agree, so the dismissal was refused.
Rules: AAK-SEC-MD-001, MANIFEST_MISSING_LICENSE · Files: SECURITY.md, /repo/skills/stacktree-publish/SKILL.md, /repo/SKILL.md · reported by agent-audit-kit, cisco-skill-scanner
2 The model did not answer for these findings.
Rules: SOCIAL_ENG_VAGUE_DESCRIPTION · Files: /repo/skills/stacktree-publish/SKILL.md, /repo/SKILL.md · reported by cisco-skill-scanner
1 The model gave no reason we were willing to publish, and a verdict without one is not usable evidence.
Rules: AAK-MCP-SSRF-001 · Files: src/index.ts · reported by agent-audit-kit
Critical configuration risk and high potential for sensitive data network egress.
The artifact contains a critical configuration finding in `.mcp.json` that warrants immediate attention. Additionally, high-severity findings indicate potential for sensitive data to be transmitted over the network from `src/index.ts`. The artifact also exhibits a DNS rebinding vulnerability in `package.json` and uses an Anthropic SDK in `src/index.ts`, which may involve external data exchange.
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.