updated 2026-10-11 12:08 UTC

Obsidian Vault MCP

Repository Website

obsidian-vault-mcp

MCP Servers Python Listed MIT

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

OSSF Scorecard 4.6 / 10
Provenance None
Signed commits 11%
Last push 61d ago
Advisories None known
Compare Obsidian Vault MCP

How does it stack up against its MCP Servers neighbours?

Pick any agent to compare →
Suggest a correction

In detail: Obsidian Vault MCP scores 48.2/100 (Grade D), ranked #1029 of 1371 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 4.6/10; 11% of recent commits are signed; no published advisory affects its latest release (zotero-obsidian-mcp); last pushed 2026-08-11. Every point is earned from checkable signals — never paid placement. How scoring works →

How Obsidian Vault MCP 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 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/luffysolution-svg/obsidian-vault-mcp, MIT, last pushed 2026-08-11. 11% of the last 100 commits carry a verified signature; the rest can't be tied to a verified identity.

  2. Review and release Mixed

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

    • Code Review0
    • Branch Protection0
    • Signed Releases0
    • Dangerous Workflow10
    • Token Permissions10
    • Pinned Dependencies10
    All 18 Scorecard checks
    Binary-Artifacts 10
    Branch-Protection 0
    CI-Tests 10
    CII-Best-Practices 0
    Code-Review 0
    Contributors 3
    Dangerous-Workflow 10
    Dependency-Update-Tool 0
    Fuzzing 0
    License 10
    Maintained 10
    Packaging 10
    Pinned-Dependencies 10
    SAST 0
    Security-Policy 0
    Signed-Releases 0
    Token-Permissions 10
    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: zotero-obsidian-mcp 3.0.2. No published advisory affects it (OSV, checked 2026-10-10).

Changes to this chain

  • 2026-09-08 OSSF Scorecard: 4.7/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’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 compares in MCP Servers

  1. #589 Linkup MCP Server 48.3 +0.1
  2. #590 Home Assistant Vibecode Agent 48.3 +0.1
  3. #591 Obsidian Vault MCP 48.2 this agent
  4. #592 Appstore Connect MCP 48.2 ±0
  5. #593 Kylas CRM 48.1 −0.1

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

Where the 48.2 comes from

HVTrust dimensions vs the MCP Servers average

48.2 / 100 · 100.0% confidence

Obsidian Vault MCP MCP Servers average (781 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
6.3 / 25
4.1 below avg 10.4
Identity / Provenance60% listing status · 40% build provenance
10.8 / 18
2.7 below avg 13.5
Transparency50% declared license · 50% OSSF Scorecard
12.4 / 17
in line with avg 12.2
Maintenance60% last-push freshness · 40% commit activity
7.9 / 20
4.3 below avg 12.2
AdoptionLog-scaled stars · package downloads
7.1 / 20
in line with avg 7.4

Quick Trust Read

What Would Improve It
Publish package provenance or release attestations for stronger supply-chain evidence.
Recent Changes
2026-10-10
Rank Moved
Rank dropped 10 spots (#1015 → #1025)
2026-10-09
Rank Moved
Rank dropped 12 spots (#1003 → #1015)
2026-10-05
Rank Moved
Rank dropped 10 spots (#988 → #998)
Maintainer Checklist
Raise Scorecard signals Current OSSF Scorecard is 4.6/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.
Refresh maintenance signals The repo was last pushed 61 days ago. Fresh activity helps separate stable projects from stale ones.
Compare with another agent Get email alerts for Obsidian Vault MCP View MCP Servers Report missing data
32.5
Activity sub-score · out of 100
#591
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-10-11 12:08 UTC · Repo last pushed 61 days ago

Rank Trend

2026-09-29 2026-10-11

Activity & Reach

Stars
93
Forks
7
Last Push
2026-08-11
61 days ago
Commits (4 wk)
0
Downloads (7d)
62
pypi
HN mentions (30d)
—
Open Issues
1
Rank Change
▼4
was #1025

Analysis

Activity Inputs

32.5 / 100
StarsRepository reach
11.8 / 30
FreshnessLast push recency
16.5 / 25
ActivityRecent commits
0.0 / 25
CommunityFork signal
4.2 / 20

Common questions about Obsidian Vault MCP

Public trust evidence for Obsidian Vault MCP 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 publish package provenance?
No published build provenance is currently detected for Obsidian Vault MCP. 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 have an OpenSSF Scorecard?
Obsidian Vault MCP has an OpenSSF Scorecard score of 4.6/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 actively maintained?
Slowing down. Last push was 61 days ago — keep an eye on whether activity resumes.
What license does Obsidian Vault MCP use?
Obsidian Vault MCP ships under MIT. A declared, OSI-approved license is one of the transparency signals HVTrust scores.
Are Obsidian Vault MCP's commits signed?
11% of the last 100 commits to Obsidian Vault MCP 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
medium confidence
Declared
MCP support appears present, but direct server implementation is less certain.
Detailed evidence is not shown in the public view.
External Service Dependencies
medium confidence
1 detected
Public provider/service dependencies detected.
Credential signal: No explicit API-key/config marker detected.
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'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-09-23
Tool Surface Changed
Detected tool/plugin surface changed: none → declared
2026-09-23
Provider Added
Runtime surface grew — new detected provider dependency: Anthropic
2026-09-23
Mcp Status Changed
Detected MCP server support changed: none → declared

Maintain Obsidian Vault MCP?

For maintainers

HVTrust scores Obsidian Vault MCP 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 25HVTrust 3Listed 2Score 2Grade 2Scorecard 1Delisted 1MCP 1Surface 1Surface 1
2026-10-10
Rank Moved
Rank dropped 10 spots (#1015 → #1025)
2026-10-09
Rank Moved
Rank dropped 12 spots (#1003 → #1015)
2026-10-05
Rank Moved
Rank dropped 10 spots (#988 → #998)
2026-09-30
Rank Moved
Rank dropped 14 spots (#958 → #972)
2026-09-25
Rank Moved
Rank dropped 14 spots (#929 → #943)
2026-09-23
Tool Surface Changed
Detected tool/plugin surface changed: none → declared
2026-09-23
Provider Added
Runtime surface grew — new detected provider dependency: Anthropic
2026-09-23
Mcp Status Changed
Detected MCP server support changed: none → declared
2026-09-23
Rank Moved
Rank rose 128 spots (#1061 → #933)
2026-09-23
HVTrust Changed
HVTrust up 26.6pts (23.1 → 49.7)
2026-09-22
Newly Listed
First tracked at rank #1061
2026-09-21
Removed From Active Tracking
Removed from active tracking
2026-09-20
Grade Changed
Trust grade C → D
2026-09-11
Rank Moved
Rank dropped 11 spots (#903 → #914)
2026-09-10
Rank Moved
Rank dropped 66 spots (#837 → #903)
2026-09-10
Activity Score Changed
Activity score down 6pts (43 → 36)
2026-09-09
Rank Moved
Rank dropped 13 spots (#824 → #837)
2026-09-08
Scorecard Added
OSSF Scorecard: 4.7/10
2026-09-08
Grade Changed
Trust grade D → C
2026-09-08
Rank Moved
Rank rose 446 spots (#1270 → #824)
2026-09-08
HVTrust Changed
HVTrust up 22.7pts (29.8 → 52.5)
2026-09-07
Rank Moved
Rank dropped 10 spots (#1260 → #1270)
2026-09-06
Rank Moved
Rank dropped 15 spots (#1245 → #1260)
2026-09-05
Rank Moved
Rank rose 59 spots (#1304 → #1245)
2026-09-05
HVTrust Changed
HVTrust up 11.5pts (18.4 → 29.9)
2026-09-02
Rank Moved
Rank dropped 17 spots (#1274 → #1291)
2026-09-01
Rank Moved
Rank dropped 13 spots (#1261 → #1274)
2026-08-31
Rank Moved
Rank dropped 11 spots (#1250 → #1261)
2026-08-30
Rank Moved
Rank dropped 12 spots (#1238 → #1250)
2026-08-29
Rank Moved
Rank dropped 95 spots (#1143 → #1238)
2026-08-29
Activity Score Changed
Activity score down 18pts (61 → 44)
2026-08-28
Rank Moved
Rank dropped 23 spots (#1120 → #1143)
2026-08-27
Rank Moved
Rank dropped 18 spots (#1102 → #1120)
2026-08-26
Rank Moved
Rank dropped 69 spots (#1033 → #1102)
2026-08-16
Rank Moved
Rank dropped 30 spots (#1000 → #1030)
2026-08-13
Rank Moved
Rank dropped 12 spots (#991 → #1003)
2026-08-12
Rank Moved
Rank rose 14 spots (#1005 → #991)
2026-08-10
Rank Moved
Rank dropped 58 spots (#958 → #1016)
2026-08-08
Newly Listed
First tracked at rank #952
GitHub → Website → PyPI: zotero-obsidian-mcp

Embed Badge Badge guide for maintainers →

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

Other agents in MCP Servers

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