io.github.OleksandrKucherenko/mcp-obsidian-via-rest

Name: io.github.OleksandrKucherenko/mcp-obsidian-via-rest
Author: io.github.OleksandrKucherenko

MCPcommunity

v1.3.3io.github.OleksandrKucherenkoUnknownUpdated 7mo agonpm GitHub

Access Obsidian vaults via Local REST API - read, search, and interact with notes

[]( []( []( []( []( []( []( [](LICENSE) MCP Tools \& Resources Multi-URL Configuration (Recommended) HTTP Transport Configuration Decoupled Configuration with Authentication Stdio Transport Configuration Legacy Single-URL Configuration CLI Tools Configuration Setup and Troubleshooting Verify that the Obsidian REST API is running (Windows Host, MacOS, Linux) WSL2, Docker hosted on Ubuntu Verify…

Automatically indexed from public sources. Not yet verified by the developer on Forge.Claim this listing →

7mo agoLast update

Package

Authorio.github.OleksandrKucherenko

LicenseUnknown

Version1.3.3

Sourcemcp-registry

npm@oleksandrkucherenko/mcp-obsidian

GitHubOleksandrKucherenko/mcp-obsidian-via-rest

Trust Status

60/100Good

✓Listed in Forge index+10/10

—Publisher identity verified+0/20

→ Publisher: run `forge publish` from the package repo to claim ownership

—Ed25519 publish signature+0/5

→ Included automatically when the publisher runs `forge publish`

—Domain verification+0/5

→ Publisher: host /.well-known/forge.json on the package homepage with { "publisher": "<github-login>" }

—npm Trusted Publishing (Sigstore)+0/5

→ Publish from GitHub Actions with --provenance so the attestation binds this package to this repo

—npm maintainer match+0/5

→ Earned once your identity is verified above and that login is an npm maintainer of this package

✓CVE scan · clean+30/30

✓Static analysis · clean+20/20

Paste into Claude Code, Cursor, or any AI assistant to fix all gaps

StatusCommunity-indexed

PublisherUnverified

SignatureUnsigned

Domain—

Provenance—

Dependencies✓ 60 resolved+ · none vulnerable

Tool surface3 tools · none privileged

Security scan✓ Cleanv1.3.4 · 2mo ago

EvalsNone

IndexedJun 13, 2026

Verification confirms publisher identity (repo ownership), not code safety. The security scan covers known CVEs and suspicious install scripts — it cannot prove the absence of malicious code.

About

Keywords

mcp