Loading the registry…
MCP server for AI-assisted Zettelkasten card creation with guided workflows
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 -- zettelkasten-card-mcp
Install respects the composite badge: Clean proceeds, Caution prompts for confirmation, and Flagged is refused. Write operations require an API token.
4 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.
v2.0.11
6 findings · 11.1s
v0.3.74
5 findings · 1.3s
v0.1.0
0 findings · 5.2s
v0.1.0
0 findings · 5.2s
v1.4.0
None of the entry points this scanner reads were found in this artifact. What each scanner covers
0 findings · 0.3s
vv0.3.2
No Go packages were found in this artifact. What each scanner covers
0 findings · 0.5s
v0.1.0
This scanner found nothing in this artifact that it assesses. What each scanner covers
0 findings · 2.3s
v0.71.0
No dependency manifest or lockfile was found in this artifact. What each scanner covers
0 findings · 0.2s
v2.3.8
No dependency manifest or lockfile was found in this artifact. What each scanner covers
0 findings · 0.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 21, 2026 | Flagged88 | — | agentshield ·n/a: not applicablecisco-skill-scanner: completeagent-audit-kit: completenerlo-behavioral: completenerlo-install-instruction: completecapslock ·n/a: not applicablenerlo-multi-source ·n/a: not applicabletrivy ·n/a: not applicableosv-scanner ·n/a: not applicabletrivy_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 11 findings across every scanner that examined this package.
These findings are in files this artifact installs and are not placeholder values. No false-positive basis can be corroborated for such a finding, so this review never dismisses one; they were not sent to the model and stand at their scanner's severity.
2 MANIFEST_MISSING_LICENSE
Files: /repo/SKILL.md, /repo/development_logs/SKILL.md · reported by cisco-skill-scanner
2 SOCIAL_ENG_VAGUE_DESCRIPTION
Files: /repo/SKILL.md, /repo/development_logs/SKILL.md · reported by cisco-skill-scanner
1 AAK-DNS-REBIND-002
Files: pyproject.toml · reported by agent-audit-kit
1 AAK-MCP-SDK-CVE-2026-52869-001
Files: pyproject.toml · reported by agent-audit-kit
1 AAK-OAUTH-3P-001
Files: pyproject.toml · reported by agent-audit-kit
1 AAK-SEC-MD-001
Files: SECURITY.md · reported by agent-audit-kit
1 AAK-SUPPLY-004
Files: pyproject.toml · reported by agent-audit-kit
1 FILE_MAGIC_MISMATCH
Files: /repo/template.md · reported by cisco-skill-scanner
1 MANIFEST_INVALID_NAME
Files: /repo/development_logs/SKILL.md · reported by cisco-skill-scanner
Artifact has high-severity DNS rebind and SDK vulnerabilities.
The artifact contains a high-severity DNS rebind vulnerability, which could permit network egress to unintended destinations. Additionally, a high-severity vulnerability (CVE-2026-52869) is present in an included SDK, which may allow for credential access or other system compromise. Multiple medium-severity findings also warrant attention, including potential supply chain risks and an OAuth 3rd-party integration issue. These findings are located within the `pyproject.toml` file and other installed code.
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.