Vault Health Mcp

io.github.onetrueclaude-creatorPublished by GitHub account onetrueclaude-creatorv0.2.0Updated Oct 24, 2026

Obsidian vault structural health: broken links, orphans, missing frontmatter, safe auto-repair.

VerifiedSTDIODesktop onlyFiles & StorageKnowledge & Memory

Overview

AI-generated overview

A local MCP server that checks an Obsidian vault for structural problems — broken wikilinks, orphan notes and missing frontmatter — and can auto-repair safe, in

What you can do
Point the server at an Obsidian vault and run a full structural health scan covering broken links, orphans and missing frontmatter, or list orphans and broken wikilinks separately. Report vault statistics such as file count, link count, orphan percentage and frontmatter coverage. With a Pro license, run an auto-repair that replaces broken wikilinks with plain text and adds default frontmatter blocks.
When to use it
Useful when you keep notes in an Obsidian vault and want an assistant to audit its structure, find disconnected or badly linked notes, and optionally apply safe additive fixes without plugins.
Requirements
Runs locally as a Python package (Python 3.10+) via uvx or pip, with the vault path passed as an argument. No plugins needed. The optional Pro license is supplied through the VAULT_HEALTH_LICENSE environment variable, a CLI flag or a config file.
Before you install
The repair tool writes to vault files, though it is described as additive only: it replaces broken wikilinks with plain text and adds default frontmatter, and claims never to delete files or change existing frontmatter values. The Pro license is a paid credential; verification is offline. Back up the vault before running repairs.

Installation

In SourceWeft

  1. Open Vault Health Mcp in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

vault-health-mcp

MCP server for Obsidian vault structural health checks.

Find broken wikilinks, orphaned notes, and missing frontmatter — then auto-repair them. Works with any Obsidian vault, no plugins required.

Install

bash
pip install vault-health-mcp

Usage

Claude Code

bash
claude mcp add vault-health -- vault-health-mcp --vault ~/my-vault

Claude Desktop

json
{  "mcpServers": {    "vault-health": {      "command": "uvx",      "args": ["vault-health-mcp", "--vault", "/path/to/vault"]    }  }}

MCP Tools

ToolTierDescription
configure_vaultFreePoint the server at a vault at runtime
check_vault_healthFreeFull structural scan: broken links, orphans, missing frontmatter
find_orphansFreeList all structurally disconnected leaf notes
find_broken_linksFreeList all wikilinks pointing to non-existent files
vault_statisticsFreeFile count, link count, orphan %, frontmatter coverage
repair_vaultProAuto-fix safe issues (add-only, never deletes)

How auto-repair works (Pro)

repair_vault only makes additive changes:

  • Broken [[links]] → replaced with plain text (the link text is preserved)
  • Missing frontmatter → adds a default YAML block with title and type

It never deletes files, removes content, or modifies existing frontmatter values.

Pro tier

The free tier detects every category of vault rot. The Pro tier unlocks repair_vault — one call to fix the safe categories automatically.

License activation — any one of these works:

bash
# 1. Environment variableexport VAULT_HEALTH_LICENSE="eyJhbGc..."
# 2. CLI flagvault-health-mcp --license-key "eyJhbGc..." --vault ~/my-vault
# 3. Config fileecho "eyJhbGc..." > ~/.vault-health-mcp/license.jwt

Licenses are verified fully offline — no phone-home, no activation server. Get a license: [coming soon — Dodo Payments storefront in verification].

Requirements

  • Python 3.10+
  • An Obsidian vault (any size)

License

MIT

Source: README.md at commit 9a67a87

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v0.2.0LatestSep 16, 2026

Score

50% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts