updated 2026-11-11 00:08 UTC

Obsidian Vault MCP Server

Repository Website

MCP Server connected to Obsidian Vault with Local REST API. (re-write it completely with BUN to make it faster and more lightweight)

MCP Servers TypeScript Listed MIT

Is Obsidian Vault MCP Server safe? Thin or incomplete trust evidence. Review carefully before production use.

OSSF Scorecard 2.0 / 10
Provenance None
Signed commits 22%
Last push 17d ago
Advisories None known
Compare Obsidian Vault MCP Server

How does it stack up against its MCP Servers neighbours?

Pick any agent to compare →
Suggest a correction

In detail: Obsidian Vault MCP Server scores 48.0/100 (Grade D), ranked #1069 of 1387 tracked open-source AI agent projects, on evidence coverage B (3 of 5 independent signal types). The public evidence: no package-provenance attestation found; OSSF Scorecard rates its supply-chain practices 2.0/10; 22% of recent commits are signed; no published advisory affects its latest release (@oleksandrkucherenko/mcp-obsidian); last pushed 2026-10-25. Every point is earned from checkable signals — never paid placement. How scoring works →

How Obsidian Vault MCP Server could raise its score

Each line changes one public signal and recomputes with the live scoring function. The gains don't add up exactly, because the score is capped near the top.

Already done? Suggest a correctionAdd the trust badge

Chain of custody

Scanners check what the code says. This traces who ships Obsidian Vault MCP Server and whether that has changed: from the source repository, through how changes are reviewed and released, to the package you install. These are the checks for OWASP ASI04 Agentic Supply Chain Vulnerabilities.

  1. Source Partly signed

    github.com/OleksandrKucherenko/mcp-obsidian-via-rest, MIT, last pushed 2026-10-25. 22% of the last 100 commits carry a verified signature; the rest can't be tied to a verified identity.

  2. Review and release Weak

    OpenSSF Scorecard rates the repository's practices 2.0/10 (scanned Nov 10, 2026). The checks that decide who can get a change released:

    • Code Review0
    • Branch Protection0
    • Signed Releasesn/a
    • Dangerous Workflow0
    • Token Permissions0
    • Pinned Dependencies0
    All 18 Scorecard checks
    Binary-Artifacts 10
    Branch-Protection 0
    CI-Tests 10
    CII-Best-Practices 0
    Code-Review 0
    Contributors 6
    Dangerous-Workflow 0
    Dependency-Update-Tool 0
    Fuzzing 0
    License 10
    Maintained 1
    Packaging 10
    Pinned-Dependencies 0
    SAST 0
    Security-Policy 0
    Signed-Releases -1
    Token-Permissions 0
    Vulnerabilities 0

  3. Published packages Linked, not attested

    Without a build attestation, nothing proves the published files were built from this repository.

  4. What you install today No known advisories

    Latest release checked: @oleksandrkucherenko/mcp-obsidian 1.3.4. No published advisory affects it (OSV, checked 2026-11-10).

Changes to this chain

  • 2026-09-06 OSSF Scorecard: 1.9/10

Evidence behind this score

Coverage B: 3 of 5 independent evidence types found.

  • GitHub repository data
  • Package downloads
  • Supply-chain checks
  • Public actions (missing)
  • Community mentions (missing)

Verify this score yourself

Every build re-issues Obsidian Vault MCP Server’s score as an Ed25519-signed credential, valid for 7 days. You can check it offline against HVTracker’s published key; if anyone changes a number after signing, verification fails.

Signed credential (JSON) How to verify

What this score doesn’t check

It covers who ships the code, not what the code does. It doesn’t read tool descriptions or prompts for injected instructions, watch runtime behaviour, or find bugs nobody has disclosed yet. For that, run a content scanner before you connect it, such as Cisco MCP Scanner or Snyk Agent Scan.

How Obsidian Vault MCP Server compares in MCP Servers

  1. #601 MCPSpend 48.1 +0.1
  2. #602 Ads MCP 48.0 ±0
  3. #603 Obsidian Vault MCP Server 48.0 this agent
  4. #604 Ryaker Appstore Connect MCP 48.0 ±0
  5. #605 Druid MCP Server 47.9 −0.1

Bars show each HVTrust score; the tick marks Obsidian Vault MCP Server’s 48.0.

Where the 48.0 comes from

HVTrust dimensions vs the MCP Servers average

48.0 / 100 · 100.0% confidence

Obsidian Vault MCP Server MCP Servers average (779 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
3.6 / 25
7.2 below avg 10.8
Identity / Provenance60% listing status · 40% build provenance
10.8 / 18
2.9 below avg 13.7
Transparency50% declared license · 50% OSSF Scorecard
10.2 / 17
2.1 below avg 12.3
Maintenance60% last-push freshness · 40% commit activity
12.8 / 20
0.5 above avg 12.3
AdoptionLog-scaled stars · package downloads
5.9 / 20
1.7 below avg 7.6

Quick Trust Read

What Would Improve It
Publish package provenance or release attestations for stronger supply-chain evidence.
Recent Changes
2026-11-08
Rank Moved
Rank rose 10 spots (#1073 → #1063)
2026-10-26
Rank Moved
Rank dropped 13 spots (#1067 → #1080)
2026-10-25
Activity Resumed
Activity resumed
Maintainer Checklist
Raise Scorecard signals Current OSSF Scorecard is 2.0/10. Tighten the weakest checks to improve public safety evidence.
Publish provenance Add package provenance or release attestations so users can verify where shipped artifacts came from.
Increase signed commits Raise the share of verified-signed commits to make maintainer identity and release history easier to trust.
Compare with another agent
View MCP Servers Report missing data
37.1
Activity sub-score · out of 100
#603
In MCP Servers

How to read this: HVTrust (0–100) weighs supply-chain signals (provenance, OSSF Scorecard, signed commits, open license) alongside real-world adoption. Grade D reflects the trust score band: A ≥ 80, B ≥ 65, C ≥ 50, D < 50. Evidence coverage B is separate — it grades how many independent signal types back the score (3 of 5), so a high score on thin evidence stays visible. Full methodology →

Signals refreshed 2026-11-11 00:08 UTC · Repo last pushed 17 days ago

Rank Trend

2026-09-29 2026-11-10

Activity & Reach

Stars
13
Forks
1
Last Push
2026-10-25
17 days ago
Commits (4 wk)
2
Downloads (7d)
240
npm
HN mentions (30d)
—
Open Issues
5
Rank Change
▲2
was #1071

Analysis

Activity Inputs

37.1 / 100
StarsRepository reach
6.9 / 30
FreshnessLast push recency
22.6 / 25
ActivityRecent commits
6.0 / 25
CommunityFork signal
1.4 / 20

Common questions about Obsidian Vault MCP Server

Public trust evidence for Obsidian Vault MCP Server is thin: several supply-chain signals are missing or weak. This does not mean the project is unsafe — it means an outside observer cannot easily verify the usual integrity checks. Treat with extra scrutiny.
Does Obsidian Vault MCP Server publish package provenance?
No published build provenance is currently detected for Obsidian Vault MCP Server. This is common for open-source projects but means consumers cannot independently verify that the package on the registry matches the GitHub source.
Does Obsidian Vault MCP Server have an OpenSSF Scorecard?
Obsidian Vault MCP Server has an OpenSSF Scorecard score of 2.0/10. The Scorecard checks for branch protection, signed releases, dependency updates, fuzzing, code review, and other supply-chain hygiene items. See the full check breakdown on this page.
Is Obsidian Vault MCP Server actively maintained?
Maintained. Last push was 17 days ago.
What license does Obsidian Vault MCP Server use?
Obsidian Vault MCP Server ships under MIT. A declared, OSI-approved license is one of the transparency signals HVTrust scores.
Are Obsidian Vault MCP Server's commits signed?
22% of the last 100 commits to Obsidian Vault MCP Server are verified-signed (GPG, SSH, S/MIME, or GitHub's signing flow). Signed commits help confirm that code was authored by who the commit claims.

Not a safety endorsement. HVTracker describes what public signals show, not whether a project is safe for your use case. Run your own security review before adopting in production.

AI agent surface

MCP, providers, tool surface
Scored in HVTrust

These runtime-trust fields — detected from public repo docs and manifests — contribute a bounded adjustment to this project's HVTrust score alongside supply-chain evidence. The exact values each field can add or subtract are documented in the methodology → Compare this surface across every listed agent in the capability matrix →

MCP Server Support
high confidence
Implemented
Obsidian Vault MCP Server appears to expose MCP server capabilities.
Detailed evidence is not shown in the public view.
External Service Dependencies
low confidence
None detected
No clear third-party provider dependency detected.
Credential signal: API keys or service config markers documented.
Tool / Plugin Surface
high confidence
Declared
Declared plugin/integration surface detected.
Detailed evidence is not shown in the public view.
Package Provenance Drift
high confidence
Match
Published package metadata matches the tracked repo
Detailed evidence is not shown in the public view.
  • MCP signal live
  • External deps live
  • Tool / plugin surface live
  • Package provenance drift live
How this surface has changed

Detected changes to Obsidian Vault MCP Server's runtime surface and supply-chain posture, from daily public-signal snapshots. A change here means our detectors see something different — a genuinely changed capability, or better evidence of an existing one.

2026-10-25
Activity Resumed
Activity resumed
2026-09-23
Tool Surface Changed
Detected tool/plugin surface changed: none → declared
2026-09-23
Mcp Status Changed
Detected MCP server support changed: none → implemented

Maintain Obsidian Vault MCP Server?

For maintainers

HVTrust scores Obsidian Vault MCP Server from public signals only — we never contact maintainers first. If a signal is wrong, stale, or missing (provenance you publish, a Scorecard you run, signed releases), tell us and we'll review it. Corrections are public and tracked on GitHub.

Submit a correction → Add the trust badge

Reputation Timeline

Signal history
Rank 11HVTrust 4Scorecard 1Delisted 1Listed 1MCP 1Surface 1Score 1Fresh 1
2026-11-08
Rank Moved
Rank rose 10 spots (#1073 → #1063)
2026-10-26
Rank Moved
Rank dropped 13 spots (#1067 → #1080)
2026-10-25
Activity Resumed
Activity resumed
2026-10-25
Rank Moved
Rank rose 243 spots (#1310 → #1067)
2026-10-25
HVTrust Changed
HVTrust up 13.9pts (34.0 → 47.9)
2026-10-25
Activity Score Changed
Activity score up 31pts (8 → 39)
2026-10-09
Rank Moved
Rank dropped 11 spots (#1266 → #1277)
2026-09-23
Tool Surface Changed
Detected tool/plugin surface changed: none → declared
2026-09-23
Mcp Status Changed
Detected MCP server support changed: none → implemented
2026-09-23
Rank Moved
Rank rose 74 spots (#1309 → #1235)
2026-09-23
HVTrust Changed
HVTrust up 23.2pts (12.2 → 35.4)
2026-09-22
Newly Listed
First tracked at rank #1309
2026-09-21
Removed From Active Tracking
Removed from active tracking
2026-09-09
Rank Moved
Rank dropped 10 spots (#1198 → #1208)
2026-09-08
Rank Moved
Rank dropped 15 spots (#1183 → #1198)
2026-09-07
Rank Moved
Rank rose 108 spots (#1291 → #1183)
2026-09-07
HVTrust Changed
HVTrust up 12.7pts (23.9 → 36.6)
2026-09-06
Scorecard Added
OSSF Scorecard: 1.9/10
2026-09-06
Rank Moved
Rank rose 28 spots (#1319 → #1291)
2026-09-06
HVTrust Changed
HVTrust up 9.2pts (14.7 → 23.9)
2026-08-26
Rank Moved
Rank dropped 17 spots (#1269 → #1286)
2026-08-16
Rank Moved
Rank dropped 26 spots (#1239 → #1265)
GitHub → Website → npm: @oleksandrkucherenko/mcp-obsidian

Embed Badge Badge guide for maintainers →

For maintainers
HVTrust 48.0 Grade D
Markdown:
[![HVTrust](https://hvtracker.net/badge/obsidian-vault-mcp-server.svg)](https://hvtracker.net/agents/obsidian-vault-mcp-server)
HTML:
<a href="https://hvtracker.net/agents/obsidian-vault-mcp-server"><img src="https://hvtracker.net/badge/obsidian-vault-mcp-server.svg" alt="HVTrust"></a>

Other agents in MCP Servers

Data sources
GitHub REST API (repo, commits, stars, forks, license) · npm Registry (downloads, provenance) · OpenSSF Scorecard CLI
Each agent's signals refresh once daily across 6 staggered batches. Methodology v4.4 · Raw JSON