Loading the registry…
MCP-style JSON-over-stdio server exposing an Obsidian vault as resources & tools (create/search/export)
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.
npm: @debjit_kundu/obsidian-mcp-server @ 0.1.1, 0 findings
Choose your runtime: the CLI writes the mcpServers config entry for that target.
nerlo install --target claude-code -- @debjit_kundu/obsidian-mcp-server
Install respects the composite badge: Clean proceeds, Caution prompts for confirmation, and Flagged is refused. Write operations require an API token.
8 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.7s
v2.0.11
22 findings · 9.0s
v0.3.74
1 finding · 1.2s
v0.1.0
0 findings · 4.3s
v0.1.0
0 findings · 4.3s
v0.1.0
0 findings · 9.9s
v0.71.0
2 findings · 0.2s
v2.3.8
2 findings · 8.3s
vv0.3.2
No Go packages were found in this artifact. What each scanner covers
0 findings · 0.1s
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 19, 2026 | Caution88 | — | agentshield: completecisco-skill-scanner: completeagent-audit-kit: completenerlo-behavioral: completenerlo-install-instruction: completecapslock ·n/a: not applicablenerlo-multi-source: completetrivy: 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 Caution badge are computed from those raw severities alone. Nothing below moved them.
Out of 27 findings across every scanner that examined this package.
Not reviewed is not the same as clean. Those 19 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.
1 ARCHIVE_FILE_DETECTED
Files: /repo/obsidian-mcp-server-0.1.0.tgz · reported by cisco-skill-scanner
1 CVE-2026-33671
Files: package-lock.json · reported by trivy
1 CVE-2026-33672
Files: package-lock.json · reported by trivy
1 FILE_MAGIC_MISMATCH
Files: /repo/obsidian-mcp-server-0.1.0.tgz!/package/dist/protocol/types.js · reported by cisco-skill-scanner
1 GHSA-3v7f-55p6-f55p
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-c2c7-rcm5-vvqj
Files: /repo/package-lock.json · reported by osv-scanner
1 LOW_ANALYZABILITY
Files: /repo · reported by cisco-skill-scanner
1 UNANALYZABLE_BINARY
Files: /repo/obsidian-mcp-server-0.1.0.tgz · reported by cisco-skill-scanner
18 The model called these false positives and our own check did not agree, so the dismissal was refused.
Rules: AAK-SEC-MD-001, DATA_EXFIL_JS_FS_ACCESS, MANIFEST_MISSING_LICENSE · Files: SECURITY.md, /repo/obsidian-mcp-server-0.1.0.tgz!/package/dist/index.js, /repo/src/index.ts and 1 more · reported by agent-audit-kit, cisco-skill-scanner
1 The model did not answer for these findings.
Rules: SOCIAL_ENG_VAGUE_DESCRIPTION · Files: /repo/SKILL.md · reported by cisco-skill-scanner
High-severity risks in core code and dependencies.
The artifact contains multiple high-severity findings, including potential for sensitive data exposure or insecure operations within `/repo/src/index.ts`. Additionally, high-severity vulnerabilities (CVE-2026-33671, GHSA-c2c7-rcm5-vvqj) are present in dependencies listed in `package-lock.json`. These findings indicate significant risks that could lead to system compromise or data exposure.
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.