Is Obsidian MCP Server safe to use?

Obsidian MCP Server has an HVTrust score of 65.6/100 (Grade B), ranked #453 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 MCP Server?

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

Obsidian MCP Server

cyanheads/obsidian-mcp-server

Read, write, search, and surgically edit Obsidian vault notes, tags, and frontmatter via MCP. STDIO or Streamable HTTP.

MCP Servers TypeScript Listed Apache-2.0

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

OSSF Scorecard 3.8 / 10

Provenance None

Signed commits 98%

Last push 3d ago

Compare Obsidian MCP Server

How does it stack up against its MCP Servers neighbours?

Pick any agent to compare →

Suggest a correction

In detail: Obsidian MCP Server scores 65.6/100 (Grade B), ranked #453 of 1325 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 3.8/10; 98% 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 MCP Server compares in MCP Servers

#265 Airtable 65.7 +0.1
#266 Anilist MCP 65.7 +0.1
#267 Obsidian MCP Server 65.6 this agent
#268 Apache Pinot MCP Server 65.3 −0.3
#269 Google Workspace MCP 65.3 −0.3

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

Where the 65.6 comes from

HVTrust dimensions vs the MCP Servers average

65.6 / 100 · 100.0% confidence

Obsidian MCP Server MCP Servers average (775 agents)

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

9.7 / 25

0.6 below avg 10.3

Identity / Provenance60% listing status · 40% build provenance

10.8 / 18

2.6 below avg 13.4

Transparency50% declared license · 50% OSSF Scorecard

11.7 / 17

0.5 below avg 12.2

Maintenance60% last-push freshness · 40% commit activity

18.5 / 20

6.4 above avg 12.1

AdoptionLog-scaled stars · package downloads

12.2 / 20

5.0 above avg 7.2

Quick Trust Read

What Would Improve It

Publish package provenance or release attestations for stronger supply-chain evidence.

Recent Changes

2026-09-26

Rank Moved

Rank rose 18 spots (#471 → #453)

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

Maintainer Checklist

Raise Scorecard signals Current OSSF Scorecard is 3.8/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.

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

72.0

Activity sub-score · out of 100

#267

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

685

Forks

104

Last Push

2026-09-23

3 days ago

Commits (4 wk)

Downloads (7d)

11,296

npm

HN mentions (30d)

—

Open Issues

Rank Change

▲18

was #471

Analysis

Activity Inputs

72.0 / 100

StarsRepository reach

17.0 / 30

FreshnessLast push recency

24.6 / 25

ActivityRecent commits

20.9 / 25

CommunityFork signal

9.4 / 20

Supply Chain Trust

Package Provenance

None

No package attestations found

OSSF Scorecard

3.8 / 10

OpenSSF Scorecard · scanned Sep 18, 2026

Signed Commits

98%

of last 100 commits verified

Binary-Artifacts 10

Branch-Protection 0

CI-Tests -1

CII-Best-Practices 0

Code-Review 0

Contributors 3

Dangerous-Workflow -1

Dependency-Update-Tool 0

Fuzzing 0

License 10

Maintained 10

Packaging -1

Pinned-Dependencies 0

SAST 0

Security-Policy 10

Signed-Releases 0

Token-Permissions -1

Vulnerabilities 10

Common questions about Obsidian MCP Server

Obsidian MCP Server 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 MCP Server publish package provenance?

No published build provenance is currently detected for Obsidian 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 MCP Server have an OpenSSF Scorecard?

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

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

What license does Obsidian MCP Server use?

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

Are Obsidian MCP Server's commits signed?

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

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

high confidence

1 detected

Public provider/service dependencies detected.

Anthropic

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 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-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 MCP Server?

For maintainers

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

2026-09-26

Rank Moved

Rank rose 18 spots (#471 → #453)

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

Grade Changed

Trust grade D → B

2026-09-23

Rank Moved

Rank rose 329 spots (#802 → #473)

2026-09-23

HVTrust Changed

HVTrust up 36.2pts (28.8 → 65.0)

2026-09-22

Newly Listed

First tracked at rank #802

2026-09-21

Removed From Active Tracking

Removed from active tracking

2026-09-20

Grade Changed

Trust grade B → C

2026-09-20

Rank Moved

Rank dropped 12 spots (#459 → #471)

2026-09-19

Grade Changed

Trust grade C → B

2026-09-19

Rank Moved

Rank rose 27 spots (#486 → #459)

2026-09-13

Rank Moved

Rank rose 15 spots (#493 → #478)

2026-09-11

Rank Moved

Rank dropped 16 spots (#475 → #491)

2026-09-08

Rank Moved

Rank dropped 12 spots (#470 → #482)

2026-09-07

Rank Moved

Rank dropped 31 spots (#439 → #470)

2026-09-05

Rank Moved

Rank dropped 69 spots (#364 → #433)

2026-09-04

Rank Moved

Rank rose 23 spots (#387 → #364)

2026-09-03

Rank Moved

Rank dropped 24 spots (#363 → #387)

2026-09-02

Scorecard Added

OSSF Scorecard: 3.8/10

2026-09-02

Grade Changed

Trust grade D → C

2026-09-02

Rank Moved

Rank rose 878 spots (#1241 → #363)

2026-09-02

HVTrust Changed

HVTrust up 42.1pts (20.6 → 62.7)

2026-09-01

Rank Moved

Rank dropped 23 spots (#1218 → #1241)

2026-08-31

Rank Moved

Rank dropped 24 spots (#1194 → #1218)

2026-08-30

Rank Moved

Rank dropped 27 spots (#1167 → #1194)

2026-08-29

Rank Moved

Rank dropped 26 spots (#1141 → #1167)

2026-08-28

Rank Moved

Rank dropped 22 spots (#1119 → #1141)

2026-08-27

Rank Moved

Rank dropped 18 spots (#1101 → #1119)

2026-08-26

Rank Moved

Rank dropped 70 spots (#1031 → #1101)

2026-08-22

Rank Moved

Rank rose 11 spots (#1033 → #1022)

2026-08-21

Rank Moved

Rank rose 44 spots (#1077 → #1033)

2026-08-21

Activity Score Changed

Activity score up 6pts (61 → 67)

2026-08-17

Rank Moved

Rank rose 11 spots (#1079 → #1068)

2026-08-16

Rank Moved

Rank dropped 32 spots (#1047 → #1079)

2026-08-12

Rank Moved

Rank rose 11 spots (#1053 → #1042)

2026-08-10

Rank Moved

Rank dropped 56 spots (#992 → #1048)

2026-08-08

Newly Listed

First tracked at rank #979

GitHub → npm: obsidian-mcp-server

Embed Badge Badge guide for maintainers →

For maintainers

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