Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Obsidian Everywhere

NPM · OBSIDIAN-EVERYWHERE

Graph context, semantic search, guarded edits, and reviewable Git for local Obsidian vaults.

Available components

−1 this week 43 Trust /100

Last scanned (9 hours ago)

Scores higher than 22% of npm servers

Category Memory and Knowledge

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →

Supply Chain Security80
  • No malware found by supply-chain analysis.Pass
  • CVE check failed: a known high-severity CVE affects adm-zip 0.6.0, a direct dependency. A fixed version is available. View diagnostics → Fail
  • No install/post-install scripts declared.Pass
  • 73 of 192 dependencies flagged as unhealthy (1 deprecated). View diagnostics → Partial
Provenance & Transparency97
  • Source repository is publicly reachable at the declared URL. View diagnostics → Pass
  • Cryptographically verified build provenance (signed, bound to junnnnnw00/obsidian-everywhere). View diagnostics → Pass
  • Clear OSI-approved license (MIT).Pass
  • Actively maintained (last published 69 days ago).Pass
  • Security-disclosure policy not yet verified: we couldn't inspect the source repository.Unverified
Schema Quality & AI Usability0
  • Schema quality not yet verified: our sandbox could not run this package, so we have no schema to assess.Unverified
Stability & Change Management0
  • Stability not yet verified: our sandbox could not run this package, so we have no schema to compare.Unverified
Tool Coverage0
  • Tool coverage not yet verified: our sandbox could not run this package, so we have no tool definitions to assess.Unverified
Tool Safety0
  • Tool safety not yet verified: our sandbox could not run this package, so we have no tool text to scan.Unverified
Capabilities0
  • Protocol version not yet verified: our sandbox could not run this package, so we never saw its MCP handshake.Unverified

Unverified: 5 categories

Categories scored 0 because our sandbox could not run this package, so we have no schema for these checks to read. That is a gap on our side rather than a finding about the package, and we only credit what we can confirm, so the score stands at 0 until we can run it. How we score packages →

Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 5 Nov 26 −1
    • Security disclosure: pass → unverified ▼ functional
  • 1 Nov 26 +1
    • Security disclosure: unverified → pass ▲ functional
  • 31 Oct 26 −1
    • Security disclosure: pass → unverified ▼ functional
  • 24 Oct 26 0
    • CVE-2023-54404 affects this package: high ▼ security
  • 22 Oct 26 0
    • CVE-2026-114104 affects this package: high ▼ security
    • CVE-2026-114102 affects this package: high ▼ security
    • CVE-2026-114103 affects this package: high ▼ security
    • GHSA-8238-w5pm-2374 no longer affects this package ▲ security
    • GHSA-c6fg-446q-cg94 no longer affects this package ▲ security
    • GHSA-p634-w6r4-rjp2 no longer affects this package ▲ security
  • 15 Oct 26 +1
    • Security disclosure: unverified → pass ▲ functional
  • 14 Oct 26 −1
    • Security disclosure: pass → unverified ▼ functional
  • 12 Oct 26 +1
    • Security disclosure: unverified → pass ▲ functional
Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 5 Nov 2026 · Analysed npm/obsidian-everywhere@0.9.2

Provenance Verified

A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.

Result Verified
Ecosystem npm
Reason Verified
Discovered via Registry attestation endpoint
Source repo junnnnnw00/obsidian-everywhere
Certificate issuer https://token.actions.githubusercontent.com
Certificate SAN https://github.com/junnnnnw00/obsidian-everywhere/.github/workflows/release.yml@refs/tags/v0.9.2
Rekor log index 2620961483
Predicate type SLSA build provenance https://slsa.dev/provenance/v1
Subject digest sha512:9235f0bf199b4098c44614d6499a3a71c09f170119852e3734e5f91d6277e45f5786d9152ef381e61e5de4dc41deddac73d4263ffe6c57c805e11f83a

Background: How many MCP packages publish verified provenance →

Vulnerabilities 8 findings
ID CVE Severity Vector Fix available
GHSA-7q85-xj36-vmfc CVE-2026-77301 high CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H yes
GHSA-8238-w5pm-2374 CVE-2026-114102 high CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H yes
GHSA-c6fg-446q-cg94 CVE-2026-114103 medium CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L yes
GHSA-j5f4-cc29-5x44 CVE-2026-102282 high CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N yes
GHSA-p634-w6r4-rjp2 CVE-2026-114104 medium CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:H/A:N yes
GHSA-rcw4-f5rp-g42v CVE-2026-92000 high CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H yes
GHSA-vwc7-r8mq-g2x9 CVE-2026-76845 medium CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:N/I:H/A:N no
GHSA-mrhx-c7xc-m3w5 CVE-2023-54404 high CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H yes

Background: What a vulnerability scan can and cannot prove →

Dependencies 192 packages
Packages resolved 192
Deprecated 1
Stale 72
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tools for package channels are captured by running the package in an isolated sandbox. The most recent sandbox run could not capture a tool list from this package.

Install

How do I install the Obsidian Everywhere MCP server?

Obsidian Everywhere runs locally as an npm package, launched with npx -y obsidian-everywhere. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

npm · obsidian-everywhere

# add to Claude Code
claude mcp add junnnnnw00-obsidian-everywhere -- npx -y obsidian-everywhere
Common questions

What is the Obsidian Everywhere MCP server?

Obsidian Everywhere is an MCP server listed in the public MCP registry as io.github.junnnnnw00/obsidian-everywhere. Graph context, semantic search, guarded edits, and reviewable Git for local Obsidian vaults. This page covers its npm package (obsidian-everywhere).

Is the Obsidian Everywhere MCP server safe to use?

Obsidian Everywhere scores 43 out of 100 on VerifyMCP. We recorded 8 known advisories against it as of 5 November 2026. It declares no install or post-install scripts. Its build provenance is signed and verified. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

Is the Obsidian Everywhere MCP server still maintained?

Obsidian Everywhere is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What licence is the Obsidian Everywhere MCP server under?

Obsidian Everywhere declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.