Obsidian Mcp Hsl Ce MCP Server

obsidian-mcp-hsl-ce npm v0.1.4

Published by hyunseung — 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.

Obsidian MCP Server - Community Edition by HSL

Trust grade
A
99/100
Last scanned get badge →
Trust
A · 99/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
Minimal
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 = 99/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 − 1 = 99. 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
−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 0

✓ No findings. The scan raised nothing on this surface — see Coverage for how deep it could look.

Tools 40

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

  • add_tag_to_noteno sensitive capability
  • create_daily_noteno sensitive capability
  • create_folderno sensitive capability
  • create_link_between_notesno sensitive capability
  • create_note_from_templateno sensitive capability
  • create_obsidian_noteno sensitive capability
  • delete_folderno sensitive capability
  • embed_noteno sensitive capability
  • find_broken_linksno sensitive capability
  • find_most_linked_notesno sensitive capability
Show 30 more tools ↓
  • find_orphaned_notesno sensitive capability
  • fuzzy_search_noteno sensitive capability
  • get_backlinksno sensitive capability
  • get_daily_noteno sensitive capability
  • get_folder_statisticsno sensitive capability
  • get_note_blocksno sensitive capability
  • get_note_embedsno sensitive capability
  • get_note_graph_datano sensitive capability
  • get_note_linksno sensitive capability
  • get_note_statisticsno sensitive capability
  • get_note_tagsno sensitive capability
  • get_server_infono sensitive capability
  • get_templateno sensitive capability
  • get_vault_statisticsno sensitive capability
  • list_all_tagsno sensitive capability
  • list_daily_notesno sensitive capability
  • list_foldersno sensitive capability
  • list_obsidian_notesno sensitive capability
  • list_templatesno sensitive capability
  • move_noteno sensitive capability
  • read_obsidian_noteno sensitive capability
  • remove_embedno sensitive capability
  • remove_tag_from_noteno sensitive capability
  • save_templateno sensitive capability
  • search_by_date_rangeno sensitive capability
  • search_by_regexno sensitive capability
  • search_by_tagno sensitive capability
  • search_obsidian_notesno sensitive capability
  • update_blockno sensitive capability
  • update_obsidian_noteno 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
v0.1.4 latest A 99/100 0 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 · 99/100
Markdown (GitHub README)
[![MCP Trust Score](https://mcptrustchecker.com/registry/obsidian-mcp-hsl-ce/badge.svg)](https://mcptrustchecker.com/registry/obsidian-mcp-hsl-ce)
HTML
<a href="https://mcptrustchecker.com/registry/obsidian-mcp-hsl-ce"><img src="https://mcptrustchecker.com/registry/obsidian-mcp-hsl-ce/badge.svg" alt="MCP Trust Score" height="20"></a>
Prefer shields.io styling? Point it at https://mcptrustchecker.com/registry/obsidian-mcp-hsl-ce/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 obsidian-mcp-hsl-ce --online

Use the free API → How scoring works

More in Productivity & Workflow