io.github.bezata/kobsidian-mcp

MCPattested
v0.2.1io.github.bezataUnknownUpdated 5mo agonpmGitHub

Filesystem-first MCP for Obsidian — an LLM-maintained wiki inspired by Karpathy's LLM Wiki.

Filesystem-first MCP server for Obsidian vaults — with an LLM-Wiki layer on top. Inspired by Andrej Karpathy's LLM Wiki idea. You curate the sources; the LLM does the bookkeeping. [](docs/tools.md#resources) [](docs/tools.md#prompts) Docs: 简体中文 / 日本語 / 한국어 🧰 The only Obsidian MCP with workspaces. / let an LLM discover and switch between your Obsidian vaults in-session — no restart, no config…

Works in
ClaudeCursorCopilotGemini

Inferred from the transports this listing declares (stdio). A client not listed here hasn’t been ruled out — it just isn’t something Forge can confirm.

Attested build
A verified provenance attestation binds this artifact to the listed repository. Nobody has claimed the listing yet — this proves where the code was built, not who stands behind it.
8GitHub stars
1Forks
5mo agoLast update
Package
Authorio.github.bezata
LicenseUnknown
Version0.2.1
Sourcemcp-registry
npmkobsidian-mcp
GitHubbezata/kObsidian
SBOMCycloneDX 1.6 ↓
Trust Status
A
85/100Trusted
✓Listed in Forge index+10/10
✓Identity verified · attested build+20/20
—Ed25519 publish signature+0/5
→ Included automatically when the publisher runs `forge publish`
—Domain verification+0/5
→ Publisher: host /.well-known/forge.json on the package homepage with { "publisher": "<github-login>" }
✓npm Trusted Publishing (Sigstore)+5/5
—npm maintainer match+0/5
→ Publisher: add the verified GitHub login to the npm package's maintainers (npm owner add <login>)
✓CVE scan · clean+30/30
✓Static analysis · clean+20/20
Paste into Claude Code, Cursor, or any AI assistant to fix all gaps
StatusIdentity verified
PublisherUnverified
SignatureUnsigned
Domain—
Provenance✓ Sigstore-verified · 6a84db0
Dependencies✓ 60 resolved+ · none vulnerable
Tool surface—
Security scan✓ Cleanv0.3.3 · 3mo agoHow well does this scan work?
EvalsNone
IndexedJun 13, 2026

Verification confirms publisher identity (repo ownership), not code safety. The security scan covers known CVEs and suspicious install scripts.

Tools

No tool declarations found in the source3mo ago

Forge read 0 source files from the published package tarball and matched no MCP tool registrations. Extraction is pattern-based over shipped source: a server that builds its tool list at runtime, or that ships only bundled or minified code, registers nothing this can see. Treat it as “not detected”, not as “exposes none”.

About

Filesystem-first MCP server for Obsidian vaults — with an LLM-Wiki layer on top. Inspired by Andrej Karpathy's LLM Wiki idea. You curate the sources; the LLM does the bookkeeping. [](docs/tools.md#resources) [](docs/tools.md#prompts) Docs: 简体中文 / 日本語 / 한국어 🧰 The only Obsidian MCP with workspaces. / let an LLM discover and switch between your Obsidian vaults in-session — no restart, no config edit, no per-tool path threading. Backwards compatible with . Added in v0.3.0. See docs/WORKSPACES.md.…

Keywords
mcp
Alternatives
Comparing tool surfaces…

No dependency coverage

This package was last scanned before Forge began storing the resolved tree. The next scan will record it.