Is Obsidian Local REST API safe to use?

Obsidian Local REST API has an HVTrust score of 55.3/100 (Grade C), ranked #597 of 1320 tracked AI agent projects. This score reflects verifiable supply-chain integrity, transparency, maintenance, and adoption signals.

What is the trust score for Obsidian Local REST API?

Obsidian Local REST API scores 55.3/100 on HVTracker's evidence-weighted HVTrust scale. It has 2.9k GitHub stars and is categorized under MCP Servers.

Obsidian Local REST API

coddingtonbear/obsidian-local-rest-api

A secure REST API and Model Context Protocol (MCP) server for your vault.

MCP Servers TypeScript Grade C Listed MIT

55.3/100

Rank #597 of 1320

Compare Obsidian Local REST API

How does it stack up against its MCP Servers neighbours?

Pick any agent to compare →

Promising trust profile, but some evidence still deserves review.

Open compare tool Suggest correction

Listing state

Listed

Evidence coverage

Grade C · 2/5 signals

Last push

2026-08-31 · 4d ago

Recent change

Rank +6

Is Obsidian Local REST API safe? Obsidian Local REST API scores 55.3/100 (Grade C), ranked #597 of 1320 tracked open-source AI agent projects, on evidence coverage C (2 of 5 independent signal types). The public evidence: no package-provenance attestation found; OSSF Scorecard rates its supply-chain practices 3.7/10; 30% of recent commits are signed; last pushed 2026-08-31. Every point is earned from checkable signals — never paid placement. How scoring works →

Ranked neighbours in MCP Servers

#281 Better Notion MCP — 55.4 (C) → #282 MCP Documentation Server — 55.3 (C) → #284 Local FAISS MCP Server — 55.3 (C) → #285 Mistral MCP — 55.2 (C) →

Quick Trust Read

What Would Improve It

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

Recent Changes

2026-09-03

Rank Moved

Rank dropped 37 spots (#551 → #588)

2026-09-02

Tool Surface Changed

Detected tool/plugin surface changed: extension-based → none

2026-09-02

Rank Moved

Rank rose 11 spots (#562 → #551)

Maintainer Checklist

Raise Scorecard signals Current OSSF Scorecard is 3.7/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 Get email alerts for Obsidian Local REST API View MCP Servers Report missing data

72.0

Activity sub-score · out of 100

#283

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 C reflects the trust score band: A ≥ 80, B ≥ 65, C ≥ 50, D < 50. Evidence coverage C is separate — it grades how many independent signal types back the score (2 of 5), so a high score on thin evidence stays visible. Full methodology →

Rank Trend

2026-08-11 2026-09-04

Activity & Reach

Stars

2.9k

Forks

340

Last Push

2026-08-31

4 days ago

Commits (4 wk)

Downloads (7d)

—

HN mentions (30d)

—

Open Issues

Rank Change

▼9

was #588

Analysis

HVTrust Dimensions vs MCP Servers

55.3 / 100 · 100.0% confidence

Obsidian Local REST API MCP Servers average (778 agents)

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

6.1 / 25

3.4 below avg 9.5

Identity / Provenance60% listing status · 40% build provenance

10.8 / 18

2.6 below avg 13.4

Transparency50% declared license · 50% OSSF Scorecard

11.6 / 17

in line with avg 11.8

Maintenance60% last-push freshness · 40% commit activity

16.5 / 20

4.3 above avg 12.2

AdoptionLog-scaled stars · package downloads

8.3 / 20

2.1 above avg 6.2

Activity Inputs

72.0 / 100

StarsRepository reach

20.8 / 30

FreshnessLast push recency

24.4 / 25

ActivityRecent commits

15.0 / 25

CommunityFork signal

11.8 / 20

Supply Chain Trust

Package Provenance

None

No package attestations found

OSSF Scorecard

3.7 / 10

OpenSSF Scorecard · scanned Aug 29, 2026

Signed Commits

30%

of last 100 commits verified

Binary-Artifacts 10

Branch-Protection 0

CI-Tests 5

CII-Best-Practices 0

Code-Review 1

Contributors 10

Dangerous-Workflow 10

Dependency-Update-Tool 0

Fuzzing 0

License 10

Maintained 10

Packaging -1

Pinned-Dependencies 0

SAST 2

Security-Policy 0

Signed-Releases 0

Token-Permissions 0

Vulnerabilities 5

Is Obsidian Local REST API safe?

Obsidian Local REST API 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 Local REST API publish package provenance?

No published build provenance is currently detected for Obsidian Local REST API. 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 Local REST API have an OpenSSF Scorecard?

Obsidian Local REST API has an OpenSSF Scorecard score of 3.7/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 Local REST API actively maintained?

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

What license does Obsidian Local REST API use?

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

Are Obsidian Local REST API's commits signed?

30% of the last 100 commits to Obsidian Local REST API 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 Local REST API appears to expose MCP server capabilities.

Detailed evidence is not shown in the public view.

External Service Dependencies

None detected

No clear third-party provider dependency detected.

Credential signal: No explicit API-key/config marker detected.

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

N/A

No package source configured

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 Local REST API'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-02

Tool Surface Changed

Detected tool/plugin surface changed: extension-based → none

Maintain Obsidian Local REST API?

For maintainers

HVTrust scores Obsidian Local REST API 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-03

Rank Moved

Rank dropped 37 spots (#551 → #588)

2026-09-02

Tool Surface Changed

Detected tool/plugin surface changed: extension-based → none

2026-09-02

Rank Moved

Rank rose 11 spots (#562 → #551)

2026-09-01

Rank Moved

Rank dropped 16 spots (#546 → #562)

2026-08-31

Rank Moved

Rank dropped 40 spots (#506 → #546)

2026-08-30

Rank Moved

Rank dropped 12 spots (#494 → #506)

2026-08-29

Rank Moved

Rank dropped 17 spots (#477 → #494)

2026-08-27

Rank Moved

Rank dropped 12 spots (#459 → #471)

2026-08-26

Scorecard Added

OSSF Scorecard: 3.5/10

2026-08-26

Grade Changed

Trust grade D → C

2026-08-26

Rank Moved

Rank rose 387 spots (#846 → #459)

2026-08-26

HVTrust Changed

HVTrust up 30.7pts (24.8 → 55.5)

2026-08-24

Rank Moved

Rank rose 12 spots (#864 → #852)

2026-08-23

Rank Moved

Rank dropped 14 spots (#850 → #864)

2026-08-16

Rank Moved

Rank dropped 17 spots (#834 → #851)

2026-08-13

Rank Moved

Rank dropped 11 spots (#823 → #834)

2026-08-12

Rank Moved

Rank rose 10 spots (#833 → #823)

2026-08-10

Newly Listed

First tracked at rank #827

GitHub →

Embed Badge Badge guide for maintainers →

For maintainers

Markdown:
            [![HVTrust](https://hvtracker.net/badge/obsidian-local-rest-api.svg)](https://hvtracker.net/agents/obsidian-local-rest-api)
            
HTML:
            <a href="https://hvtracker.net/agents/obsidian-local-rest-api"><img src="https://hvtracker.net/badge/obsidian-local-rest-api.svg" alt="HVTrust"></a>

Other agents in MCP Servers

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