Lolmeida Mcp Obsidian MCP Server

lolmeida-mcp-obsidian npm v1.0.2

Published by lolmeida — no publish provenance, so origin is unverified, but the source is public: the repository link below is self-declared yet readable, so you can inspect the code before adopting it.

MCP server para Obsidian

Trust grade
A
93/100
Last scanned get badge →
Trust
A · 93/100
Adoption risk for you: the threat score, then adjusted down for blast radius, publisher verification and how much the scan could see. Deterministic; every point is auditable.
Capability
High
Blast radius if it went rogue — what the server’s tools could reach. Independent of trust.
Coverage
Source
How much the scan could actually inspect. Shallow coverage is stated, never hidden.
Share this Trust Score
𝕏 Share LinkedIn Reddit
A Why this grade threat 100 − adoption risk = 93/100

The grade answers one question — how safe is this server for you to adopt — so it is computed in two auditable stages. Nothing below is an opinion or an LLM's guess; every line is a real term the deterministic engine applied, and the same input always yields the same number.

1. Threat score — 100 − 0 = 100. What the published surface and source actually contain:

The deterministic scan raised no scored threat in the surface it inspected — the threat score stayed at 100. Capability observations and advisory notes are recorded but never lower it.

2. Client adoption risk — 100 − 7 = 93. Three small, subtract-only factors that reflect your risk in adopting it — a clean scan proves less on a powerful, unverified or barely-inspectable package, so the grade says so plainly:

PointsAdoption-risk factor
−6 capability blast radius (high) — client exposure if the model is manipulated
−1 publisher verification (public source) — no provenance, but the source is public and inspectable

Capability observations and info notes are shown under Findings but never scored. Open any row's finding below for the file, line and evidence behind a deduction.

Findings 4

high Tool "obsidian_execute_command" exposes command/code executionMTC-CAP-001

Tool "obsidian_execute_command" appears to run shell commands or evaluate code (keyword "execute command" in tool name). Arbitrary execution driven by model input is one of the most dangerous MCP capabilities; combined with any untrusted input it becomes RCE.

Fix: Sandbox execution, allowlist commands/arguments, and never pass model output to a shell unescaped.

Location: tool obsidian_execute_command

medium Tool "obsidian_delete_file" can modify the filesystemMTC-CAP-002

Tool "obsidian_delete_file" can write, overwrite or delete files (keyword "delete_file" in tool name). Verify it is scoped to a safe directory.

Fix: Constrain file operations to an explicit, non-sensitive root; reject path traversal.

Location: tool obsidian_delete_file

low Mutating tool "obsidian_execute_command" declares no destructiveHintMTC-CAP-005

Tool "obsidian_execute_command" can mutate/egress but declares no destructiveHint. Clients that don't default to spec-safe behavior may not prompt before running it.

Fix: Declare accurate annotations, and gate destructive tools on user confirmation regardless.

Location: tool obsidian_execute_command

low Mutating tool "obsidian_delete_file" declares no destructiveHintMTC-CAP-005

Tool "obsidian_delete_file" can mutate/egress but declares no destructiveHint. Clients that don't default to spec-safe behavior may not prompt before running it.

Fix: Declare accurate annotations, and gate destructive tools on user confirmation regardless.

Location: tool obsidian_delete_file

Tools 24

Each tool and what it can reach — statically extracted from the published source.

  • obsidian_delete_filewrites files
  • obsidian_execute_commandruns code / shell
  • obsidian_delete_activeno sensitive capability
  • obsidian_delete_periodicno sensitive capability
  • obsidian_get_activeno sensitive capability
  • obsidian_get_commandsno sensitive capability
  • obsidian_get_fileno sensitive capability
  • obsidian_get_periodicno sensitive capability
  • obsidian_list_vault_directoryno sensitive capability
  • obsidian_list_vault_rootno sensitive capability
Show 14 more tools ↓
  • obsidian_open_fileno sensitive capability
  • obsidian_patch_activeno sensitive capability
  • obsidian_patch_fileno sensitive capability
  • obsidian_patch_periodicno sensitive capability
  • obsidian_post_activeno sensitive capability
  • obsidian_post_fileno sensitive capability
  • obsidian_post_periodicno sensitive capability
  • obsidian_put_activeno sensitive capability
  • obsidian_put_fileno sensitive capability
  • obsidian_put_periodicno sensitive capability
  • obsidian_search_dataviewno sensitive capability
  • obsidian_search_json_logicno sensitive capability
  • obsidian_simple_searchno sensitive capability
  • obsidian_statusno sensitive capability

What this scan could not see

Versions 1

Scan history per published version. The engine is deterministic — the same version always yields the same score, so a changed score means the package itself changed.

VersionScoreFindingsEngineScanned
v1.0.2 latest A 93/100 4 1.13.0 2026-09-07

Embed this score

Show this server's live Trust Score in your README, docs or website. The badge is served straight from the registry and updates automatically after every rescan — no API key needed. It links back to this page, so anyone who sees the grade can also read the findings behind it instead of taking a number on faith.

MCP Trust Score: A · 93/100
Markdown (GitHub README)
[![MCP Trust Score](https://mcptrustchecker.com/registry/lolmeida-mcp-obsidian/badge.svg)](https://mcptrustchecker.com/registry/lolmeida-mcp-obsidian)
HTML
<a href="https://mcptrustchecker.com/registry/lolmeida-mcp-obsidian"><img src="https://mcptrustchecker.com/registry/lolmeida-mcp-obsidian/badge.svg" alt="MCP Trust Score" height="20"></a>
Prefer shields.io styling? Point it at https://mcptrustchecker.com/registry/lolmeida-mcp-obsidian/badge.json via https://img.shields.io/endpoint?url=…

Verify this score yourself

The score above is reproducible: the same package version always yields the same result. Run it locally or over the free API — no account, no LLM, fully deterministic.

npx mcptrustchecker scan lolmeida-mcp-obsidian --online

Use the free API → How scoring works

More in Productivity & Workflow