Is Obsidian Sync MCP safe to use?

Obsidian Sync MCP has an HVTrust score of 73.3/100 (Grade B), ranked #258 of 1325 tracked AI agent projects. This score reflects verifiable supply-chain integrity, transparency, maintenance, and adoption signals.

What is the trust score for Obsidian Sync MCP?

Obsidian Sync MCP scores 73.3/100 on HVTracker's evidence-weighted HVTrust scale. It has 56 GitHub stars and is categorized under MCP Servers.

Obsidian Sync MCP

es617/obsidian-sync-mcp

MCP server for Obsidian — access your vault from any AI agent, even when your machine is off. Powered by Self-hosted LiveSync.

MCP Servers TypeScript Listed MIT

Is Obsidian Sync MCP safe? Promising trust profile, but some evidence still deserves review.

OSSF Scorecard 4.9 / 10

Provenance Attested

Signed commits 9%

Last push 3d ago

Compare Obsidian Sync MCP

How does it stack up against its MCP Servers neighbours?

Pick any agent to compare →

Suggest a correction

In detail: Obsidian Sync MCP scores 73.3/100 (Grade B), ranked #258 of 1325 tracked open-source AI agent projects, on evidence coverage B (3 of 5 independent signal types). The public evidence: its packages ship with cryptographic provenance; OSSF Scorecard rates its supply-chain practices 4.9/10; 9% of recent commits are signed; last pushed 2026-09-23. Every point is earned from checkable signals — never paid placement. How scoring works →

How Obsidian Sync MCP compares in MCP Servers

#153 Hunch MCP 73.4 +0.1
#154 Hound MCP 73.3 ±0
#155 Obsidian Sync MCP 73.3 this agent
#156 Brandsystem MCP — Brand Guidelines for AI 73.2 −0.1
#157 Lotus Wisdom 73.1 −0.2

Bars show each HVTrust score; the tick marks Obsidian Sync MCP’s 73.3.

Where the 73.3 comes from

HVTrust dimensions vs the MCP Servers average

73.3 / 100 · 100.0% confidence

Obsidian Sync MCP MCP Servers average (775 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits

14.1 / 25

3.8 above avg 10.3

Identity / Provenance60% listing status · 40% build provenance

18.0 / 18

4.6 above avg 13.4

Transparency50% declared license · 50% OSSF Scorecard

12.7 / 17

in line with avg 12.2

Maintenance60% last-push freshness · 40% commit activity

16.1 / 20

4.0 above avg 12.1

AdoptionLog-scaled stars · package downloads

7.4 / 20

in line with avg 7.2

Quick Trust Read

What Would Improve It

Increase the share of verified signed commits for clearer maintainer identity.

Recent Changes

2026-09-23

Mcp Status Changed

Detected MCP server support changed: none → implemented

2026-09-23

Provenance Added

Package provenance attestation detected

2026-09-23

Grade Changed

Trust grade D → B

Maintainer Checklist

Raise Scorecard signals Current OSSF Scorecard is 4.9/10. Tighten the weakest checks to improve public safety evidence.

Increase signed commits Raise the share of verified-signed commits to make maintainer identity and release history easier to trust.

Compare with another agent Get email alerts for Obsidian Sync MCP View MCP Servers Report missing data

55.2

Activity sub-score · out of 100

#155

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 B 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 →

Rank Trend

2026-08-11 2026-09-26

Activity & Reach

Stars

Forks

Last Push

2026-09-23

3 days ago

Commits (4 wk)

Downloads (7d)

250

npm

HN mentions (30d)

—

Open Issues

Rank Change

▼2

was #256

Analysis

Activity Inputs

55.2 / 100

StarsRepository reach

10.5 / 30

FreshnessLast push recency

24.6 / 25

ActivityRecent commits

13.5 / 25

CommunityFork signal

6.5 / 20

Supply Chain Trust

Package Provenance

Verified

npm attestation

OSSF Scorecard

4.9 / 10

OpenSSF Scorecard · scanned Sep 25, 2026

Signed Commits

of last 100 commits verified

Binary-Artifacts 10

Branch-Protection 3

CI-Tests 10

CII-Best-Practices 0

Code-Review 2

Contributors 0

Dangerous-Workflow 10

Dependency-Update-Tool 0

Fuzzing 0

License 10

Maintained 10

Packaging 10

Pinned-Dependencies 4

SAST 0

Security-Policy 10

Signed-Releases 0

Token-Permissions 0

Vulnerabilities 8

Common questions about Obsidian Sync MCP

Obsidian Sync MCP has a mixed signal profile. Some trust indicators are present, others are missing. Whether it is safe for your use case depends on which gaps matter to you — review the breakdown below before adopting in production.

Does Obsidian Sync MCP publish package provenance?

Yes. Obsidian Sync MCP's package releases carry build provenance attestations, which cryptographically link the published package back to its source repository and CI workflow.

Does Obsidian Sync MCP have an OpenSSF Scorecard?

Obsidian Sync MCP has an OpenSSF Scorecard score of 4.9/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 Sync MCP actively maintained?

Actively maintained. The repository was pushed to within the last 3 day(s).

What license does Obsidian Sync MCP use?

Obsidian Sync MCP ships under MIT. A declared, OSI-approved license is one of the transparency signals HVTrust scores.

Are Obsidian Sync MCP's commits signed?

9% of the last 100 commits to Obsidian Sync 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

high confidence

Implemented

Obsidian Sync MCP 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

None detected

No clear plugin system or broad tool 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 Sync 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

Mcp Status Changed

Detected MCP server support changed: none → implemented

2026-09-23

Provenance Added

Package provenance attestation detected

Maintain Obsidian Sync MCP?

For maintainers

HVTrust scores Obsidian Sync 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

2026-09-23

Mcp Status Changed

Detected MCP server support changed: none → implemented

2026-09-23

Provenance Added

Package provenance attestation detected

2026-09-23

Grade Changed

Trust grade D → B

2026-09-23

Rank Moved

Rank rose 614 spots (#866 → #252)

2026-09-23

HVTrust Changed

HVTrust up 46.0pts (27.5 → 73.5)

2026-09-22

Newly Listed

First tracked at rank #866

2026-09-21

Removed From Active Tracking

Removed from active tracking

2026-09-20

Rank Moved

Rank rose 13 spots (#286 → #273)

2026-09-16

Rank Moved

Rank rose 31 spots (#314 → #283)

2026-09-11

Rank Moved

Rank dropped 10 spots (#299 → #309)

2026-09-07

Grade Changed

Trust grade D → B

2026-09-07

Rank Moved

Rank rose 636 spots (#921 → #285)

2026-09-07

HVTrust Changed

HVTrust up 23.7pts (47.3 → 71.0)

2026-09-06

Rank Moved

Rank dropped 23 spots (#898 → #921)

2026-09-05

Rank Moved

Rank dropped 56 spots (#842 → #898)

2026-09-04

Rank Moved

Rank dropped 35 spots (#807 → #842)

2026-09-03

Rank Moved

Rank dropped 47 spots (#760 → #807)

2026-09-02

Rank Moved

Rank dropped 35 spots (#725 → #760)

2026-09-01

Rank Moved

Rank dropped 33 spots (#692 → #725)

2026-08-31

Rank Moved

Rank dropped 39 spots (#653 → #692)

2026-08-30

Scorecard Added

OSSF Scorecard: 4.8/10

2026-08-30

Rank Moved

Rank rose 144 spots (#797 → #653)

2026-08-30

HVTrust Changed

HVTrust up 7.1pts (41.4 → 48.5)

2026-08-29

Rank Moved

Rank dropped 42 spots (#755 → #797)

2026-08-28

Rank Moved

Rank dropped 26 spots (#729 → #755)

2026-08-27

Rank Moved

Rank dropped 24 spots (#705 → #729)

2026-08-26

Rank Moved

Rank dropped 98 spots (#607 → #705)

2026-08-15

Rank Moved

Rank rose 17 spots (#615 → #598)

2026-08-10

Rank Moved

Rank dropped 23 spots (#582 → #605)

2026-08-08

Newly Listed

First tracked at rank #579

GitHub → npm: obsidian-sync-mcp

Embed Badge Badge guide for maintainers →

For maintainers

Markdown:
            [![HVTrust](https://hvtracker.net/badge/obsidian-sync-mcp.svg)](https://hvtracker.net/agents/obsidian-sync-mcp)
            
HTML:
            <a href="https://hvtracker.net/agents/obsidian-sync-mcp"><img src="https://hvtracker.net/badge/obsidian-sync-mcp.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.3 · Raw JSON