updated 2026-11-10 04:07 UTC

Obsidian Local REST API

Repository Website

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

MCP Servers TypeScript Listed MIT

Is Obsidian Local REST API safe? Thin or incomplete trust evidence. Review carefully before production use.

OSSF Scorecard 4.2 / 10
Provenance None
Signed commits 46%
Last push 24d ago
Compare Obsidian Local REST API

How does it stack up against its MCP Servers neighbours?

Pick any agent to compare →
Suggest a correction

In detail: Obsidian Local REST API scores 54.9/100 (Grade C), ranked #853 of 1374 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 4.2/10; 46% of recent commits are signed; last pushed 2026-10-17. Every point is earned from checkable signals — never paid placement. How scoring works →

How Obsidian Local REST API 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 Local REST API and whether that has changed: from the source repository, through how changes are reviewed and released, to the code you run. These are the checks for OWASP ASI04 Agentic Supply Chain Vulnerabilities.

  1. Source Partly signed

    github.com/coddingtonbear/obsidian-local-rest-api, MIT, last pushed 2026-10-17. 46% 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.2/10 (scanned Nov 7, 2026). The checks that decide who can get a change released:

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

  3. Published packages None

    No registry package. Obsidian Local REST API is used from its repository, so what you run is whatever you check out: pin a release tag or commit.

Changes to this chain

  • 2026-08-26 OSSF Scorecard: 3.5/10

Evidence behind this score

Coverage C: 2 of 5 independent evidence types found.

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

Verify this score yourself

Every build re-issues Obsidian Local REST API’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 Local REST API compares in MCP Servers

  1. #470 Apollo.io 54.9 ±0
  2. #471 Paper Distill MCP 54.9 ±0
  3. #472 Obsidian Local REST API 54.9 this agent
  4. #473 Ris MCP Ts 54.8 −0.1
  5. #474 Autotask 54.7 −0.2

Bars show each HVTrust score; the tick marks Obsidian Local REST API’s 54.9.

Where the 54.9 comes from

HVTrust dimensions vs the MCP Servers average

54.9 / 100 · 100.0% confidence

Obsidian Local REST API MCP Servers average (778 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
7.6 / 25
3.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
12.1 / 17
in line with avg 12.3
Maintenance60% last-push freshness · 40% commit activity
14.0 / 20
1.8 above avg 12.2
AdoptionLog-scaled stars · package downloads
8.4 / 20
0.8 above 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-05
Rank Moved
Rank dropped 22 spots (#824 → #846)
2026-11-04
Rank Moved
Rank dropped 11 spots (#813 → #824)
2026-11-03
Rank Moved
Rank dropped 10 spots (#803 → #813)
Maintainer Checklist
Raise Scorecard signals Current OSSF Scorecard is 4.2/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
66.0
Activity sub-score · out of 100
#472
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 →

Signals refreshed 2026-11-10 04:07 UTC · Repo last pushed 24 days ago

Rank Trend

2026-09-29 2026-11-10

Activity & Reach

Stars
3.1k
Forks
363
Last Push
2026-10-17
24 days ago
Commits (4 wk)
7
Downloads (7d)
—
HN mentions (30d)
—
Open Issues
0
Rank Change
▼1
was #852

Analysis

Activity Inputs

66.0 / 100
StarsRepository reach
21.0 / 30
FreshnessLast push recency
21.7 / 25
ActivityRecent commits
11.3 / 25
CommunityFork signal
11.9 / 20

Common questions about Obsidian Local REST API

Public trust evidence for Obsidian Local REST API 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 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 4.2/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?
Maintained. Last push was 24 days ago.
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?
46% 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-23
Mcp Status Changed
Detected MCP server support changed: none → implemented
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
Rank 33HVTrust 2Grade 2Scorecard 1Surface 1Delisted 1Listed 1MCP 1
2026-11-05
Rank Moved
Rank dropped 22 spots (#824 → #846)
2026-11-04
Rank Moved
Rank dropped 11 spots (#813 → #824)
2026-11-03
Rank Moved
Rank dropped 10 spots (#803 → #813)
2026-10-28
Rank Moved
Rank dropped 22 spots (#776 → #798)
2026-10-27
Rank Moved
Rank dropped 15 spots (#761 → #776)
2026-10-25
Rank Moved
Rank dropped 13 spots (#746 → #759)
2026-10-22
Rank Moved
Rank dropped 10 spots (#730 → #740)
2026-10-20
Rank Moved
Rank dropped 16 spots (#708 → #724)
2026-10-17
Rank Moved
Rank rose 17 spots (#713 → #696)
2026-10-15
Rank Moved
Rank dropped 10 spots (#701 → #711)
2026-10-09
Rank Moved
Rank dropped 11 spots (#681 → #692)
2026-10-03
Rank Moved
Rank rose 49 spots (#738 → #689)
2026-09-28
Rank Moved
Rank rose 15 spots (#730 → #715)
2026-09-25
Rank Moved
Rank rose 17 spots (#746 → #729)
2026-09-24
Rank Moved
Rank dropped 23 spots (#723 → #746)
2026-09-23
Mcp Status Changed
Detected MCP server support changed: none → implemented
2026-09-23
Grade Changed
Trust grade D → C
2026-09-23
Rank Moved
Rank dropped 277 spots (#446 → #723)
2026-09-23
HVTrust Changed
HVTrust up 12.2pts (44.4 → 56.6)
2026-09-22
Newly Listed
First tracked at rank #446
2026-09-21
Removed From Active Tracking
Removed from active tracking
2026-09-09
Rank Moved
Rank dropped 18 spots (#738 → #756)
2026-09-07
Rank Moved
Rank dropped 45 spots (#691 → #736)
2026-09-06
Rank Moved
Rank dropped 13 spots (#678 → #691)
2026-09-05
Rank Moved
Rank dropped 71 spots (#607 → #678)
2026-09-04
Rank Moved
Rank dropped 19 spots (#588 → #607)
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)
GitHub → Website →

Embed Badge Badge guide for maintainers →

For maintainers
HVTrust 54.9 Grade C
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.4 · Raw JSON