obsidian-mcp-server

The server demonstrates strong security practices including robust path validation (using `isPathSafe`) to prevent directory traversal attacks, explicit Zod schema validation for all tool inputs, and optional, opt-in write operations (`enableWrite: false` by default) that also employ strict path and existence checks, including a `confirm: true` parameter for deletions. Communication is via local stdio, and embedding generation is performed locally using Transformers.js, minimizing external network exposure. No 'eval' or other highly dangerous patterns were observed. The use of a detached indexing worker is standard practice.