obsidian-livesync-mcp

Provides AI agents and LLM tools with direct read/write access to Obsidian LiveSync vaults via CouchDB, including full end-to-end encryption support.

→ reejosamuel/obsidian-livesync-mcp · listed on glama

Is this your MCP?

Claim it to get a verified publisher badge, a free copy of our full audit findings, and direct contact for any high-priority issues we find.

Install from

Glama

M8ven verifies MCPs across every public registry — install directly from whichever one you prefer.

// key findings

🚨

Known vulnerabilities in dependencies: 2 critical, 1 high

Affects packages this MCP installs at runtime. Upgrade or remove the affected dependency.

⚠️

Tests do not pass

Either the test suite is broken or the code regressed. Either way the published behaviour can’t be verified by the publisher’s own tests.

🔐

You'll be asked for 2 credentials: MCP_API_KEY, password

These are read from process.env at runtime. Make sure you trust where they’ll be sent.

// known CVEs in dependencies2 critical1 high4 medium7 low

Disclosed vulnerabilities in this server's declared npm dependencies (via OSV). Whether each is reachable depends on the installed versions.

criticalvitest@3GHSA-5xrq-8626-4rwp

When Vitest UI server is listening, arbitrary file can be read and executed

criticalvitest@3GHSA-9crc-q9x8-hgqq

Vitest allows Remote Code Execution when accessing a malicious website while Vitest API server is listening

highvite@6GHSA-p9ff-h696-f583

Vite Vulnerable to Arbitrary File Read via Vite Dev Server WebSocket

mediumvite@6GHSA-356w-63v5-8wf4

Vite has an `server.fs.deny` bypass with an invalid `request-target`

mediumvite@6GHSA-4w7w-66w2-5vf9

Vite Vulnerable to Path Traversal in Optimized Deps `.map` Handling

Depend on this server? Get alerted when its CVEs change.Watch this server free →

// required environment variables

This server reads these from process.env. You'll be asked to provide them before it can run.

configCACHE_TTL— ${CACHE_TTL:-60}

configLOG_LEVEL— ${LOG_LEVEL:-info}

🔐 secretMCP_API_KEY— http — run as a long-lived HTTP server (Docker-friendly) using the modern Streamable HTTP transport from the MCP SDK (SSE transport is deprecated upstream). Optional Bearer auth.

configMCP_PORT— "${:-3100}:3100"

configMCP_TRANSPORT— http # or "stdio" (stdio rarely used in containers)

configPASSPHRASE— Everything stays on your infrastructure. The only secret that ever enters the MCP process is the E2EE you explicitly supply.

configREQUEST_TIMEOUT— ${REQUEST_TIMEOUT:-30000}

configdbname— ${DBNAME:?DBNAME is required} # e.g. my-obsidian-vault

confighostname— ${COUCHDB_URL:?COUCHDB_URL is required} # e.g. http://192.168.1.50:5984 or https://couch.example.com

🔐 secretpassword— CouchDB username/ (if you enabled HTTP auth — recommended)

configusername— CouchDB /password (if you enabled HTTP auth — recommended)

// full audit trail

The full breakdown of what we checked, the deductions that landed, the network hosts, the dependency advisories, and concrete fix guidance is available to verified publishers.

// improvement guidance — verified publishers only

We have 2 concrete improvements we can share with the publisher of this MCP. Each comes with specific guidance to raise the trust score.

// embed badge in your README

[![M8ven Score](https://m8ven.ai/badge/mcp/reejosamuel-obsidian-livesync-mcp-eohgcv)](https://m8ven.ai/mcp/reejosamuel-obsidian-livesync-mcp-eohgcv)

commit: 39064e25578aa7f171d5f57b4ca582cfcf7f7c29

code hash: d4caa651a7a25fa9c11a9441227a5d34d9b406c1a4d60fd0e6db001594f8dd6f

verified: 6/14/2026, 9:46:40 AM

view raw JSON →