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 Hybrid Search

NPM · OBSIDIAN-HYBRID-SEARCH · SCANNED SEP 20

Search Obsidian vaults with hybrid full-text, fuzzy, semantic, and graph retrieval.

+3 this week 49 Trust /100
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 Security98
  • No malware found by supply-chain analysis.Pass
  • No known CVEs affecting this package version or its production dependencies.Pass
  • No install/post-install scripts declared.Pass
  • 104 of 290 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 flowing-abyss/obsidian-hybrid-search). View diagnostics → Pass
  • Clear OSI-approved license (MIT).Pass
  • Actively maintained (last published 0 days ago).Pass
  • Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability0
  • Schema quality not yet verified: this server's registry entry declares environment variables (an API key or similar) that our sandbox does not supply, so we have no schema to assess.Unverified
Stability & Change Management0
  • Stability not yet verified: this server's registry entry declares environment variables (an API key or similar) that our sandbox does not supply, so we have no schema to compare.Unverified
Tool Coverage0
  • Tool coverage not yet verified: this server's registry entry declares environment variables (an API key or similar) that our sandbox does not supply, so we have no tool definitions to assess.Unverified
Tool Safety0
  • Tool safety not yet verified: this server's registry entry declares environment variables (an API key or similar) that our sandbox does not supply, so we have no tool text to scan.Unverified
Capabilities0
  • Protocol version not yet verified: this server's registry entry declares environment variables (an API key or similar) that our sandbox does not supply, so we never saw its MCP handshake.Unverified

Unverified: 5 categories

Categories scored 0 because our sandbox run of this package has not given us the schema these checks need 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 the capture succeeds. We are working through the fleet, so this normally clears without any action from you. How we score packages →

Install

How do I install the Obsidian Hybrid Search MCP server?

Obsidian Hybrid Search runs locally as an npm package, launched with npx -y obsidian-hybrid-search. 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-hybrid-search

# add to Claude Code
claude mcp add flowing-abyss-obsidian-hybrid-search -- npx -y obsidian-hybrid-search
// .cursor/mcp.json
{
  "mcpServers": {
    "flowing-abyss-obsidian-hybrid-search": {
      "command": "npx",
      "args": [
        "-y",
        "obsidian-hybrid-search"
      ]
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "flowing-abyss-obsidian-hybrid-search": {
      "command": "npx",
      "args": [
        "-y",
        "obsidian-hybrid-search"
      ]
    }
  }
}
# add to Codex CLI
codex mcp add flowing-abyss-obsidian-hybrid-search -- npx -y obsidian-hybrid-search
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "flowing-abyss-obsidian-hybrid-search": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "obsidian-hybrid-search"
      ],
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add flowing-abyss-obsidian-hybrid-search --command npx --arg -y --arg obsidian-hybrid-search
# ~/.hermes/config.yaml
mcp_servers:
  flowing-abyss-obsidian-hybrid-search:
    command: "npx"
    args: ["-y", "obsidian-hybrid-search"]
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "flowing-abyss-obsidian-hybrid-search": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "obsidian-hybrid-search"
      ]
    }
  }
}
# add to Vellum
assistant mcp add flowing-abyss-obsidian-hybrid-search -t stdio -c npx -a -y obsidian-hybrid-search
// mcp.json
{
  "mcpServers": {
    "flowing-abyss-obsidian-hybrid-search": {
      "command": "npx",
      "args": [
        "-y",
        "obsidian-hybrid-search"
      ]
    }
  }
}
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.

  • 20 Sept 26 0
    • Package version: 0.15.3 → 0.15.5 functional
  • 18 Sept 26 0
    • Stability: Stability not yet verified: this server's registry entry declares environment variables (an API key or similar) that our sandbox does not supply, so we have no schema to compare. security
    • Tool safety: Tool safety not yet verified: this server's registry entry declares environment variables (an API key or similar) that our sandbox does not supply, so we have no tool text to scan. security
    • Schema quality: Schema quality not yet verified: this server's registry entry declares environment variables (an API key or similar) that our sandbox does not supply, so we have no schema to assess. functional
    • Capabilities: Protocol version not yet verified: this server's registry entry declares environment variables (an API key or similar) that our sandbox does not supply, so we never saw its MCP handshake. functional
    • Tool coverage: Tool coverage not yet verified: this server's registry entry declares environment variables (an API key or similar) that our sandbox does not supply, so we have no tool definitions to assess. functional
  • 17 Sept 26 +3
    • GHSA-rgj7-g3m4-5g8c no longer affects this package security
    • GHSA-f88m-g3jw-g9cj no longer affects this package security
    • CVE-2026-39244 no longer affects this package security
    • Known CVEs: fail → pass security
    • Tool safety: Tool safety not yet verified: we do not have a sandbox capture of the tool definitions this version of the package serves yet. security
    • Stability: Stability not yet verified: we do not have a sandbox capture of the MCP schema this version of the package serves yet. security
    • Security disclosure: fail → unverified functional
    • Capabilities: Protocol version not yet verified: we do not have a sandbox capture of the MCP handshake this version of the package performs yet. functional
    • Tool coverage: Tool coverage not yet verified: we do not have a sandbox capture of the tool definitions this version of the package serves yet. functional
    • Schema quality: Schema quality not yet verified: we do not have a sandbox capture of the MCP schema this version of the package serves yet. functional
    • Package version: 0.15.2 → 0.15.3 functional
  • 11 Sept 26 0
    • Security disclosure: unverified → fail functional
  • 10 Sept 26 0
    • Security disclosure: fail → unverified functional
  • 9 Sept 26 0
    • GHSA-rgj7-g3m4-5g8c affects this package: high security
  • 1 Sept 26 0
    • Stability: Stability not yet verified: this server's registry entry declares environment variables (an API key or similar) that our sandbox does not supply, so we have no schema to compare. security
    • Tool safety: Tool safety not yet verified: this server's registry entry declares environment variables (an API key or similar) that our sandbox does not supply, so we have no tool text to scan. security
    • Schema quality: Schema quality not yet verified: this server's registry entry declares environment variables (an API key or similar) that our sandbox does not supply, so we have no schema to assess. functional
    • Capabilities: Protocol version not yet verified: this server's registry entry declares environment variables (an API key or similar) that our sandbox does not supply, so we never saw its MCP handshake. functional
    • Tool coverage: Tool coverage not yet verified: this server's registry entry declares environment variables (an API key or similar) that our sandbox does not supply, so we have no tool definitions to assess. functional
  • 31 Aug 26 0
    • Tool safety: Tool safety not yet verified: we do not have a sandbox capture of the tool definitions this version of the package serves yet. security
    • Stability: Stability not yet verified: we do not have a sandbox capture of the MCP schema this version of the package serves yet. security
    • Capabilities: Protocol version not yet verified: we do not have a sandbox capture of the MCP handshake this version of the package performs yet. functional
    • Tool coverage: Tool coverage not yet verified: we do not have a sandbox capture of the tool definitions this version of the package serves yet. functional
    • Schema quality: Schema quality not yet verified: we do not have a sandbox capture of the MCP schema this version of the package serves yet. functional
    • Package version: 0.15.1 → 0.15.2 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 20 Sept 2026 · Analysed npm/obsidian-hybrid-search@0.15.5

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 flowing-abyss/obsidian-hybrid-search
Certificate issuer https://token.actions.githubusercontent.com
Certificate SAN https://github.com/flowing-abyss/obsidian-hybrid-search/.github/workflows/release.yml@refs/tags/v0.15.5
Rekor log index 2897527913
Predicate type https://slsa.dev/provenance/v1
Subject digest sha512:86324437334122852e01ba7ba3531fde9bee53b206fdac02c1d259f300e230e28a45022c78ad1677affcfede256de86ed5f139dd94878102d1822a583

Background: How many MCP packages publish verified provenance →

Dependencies 290 packages
Packages resolved 290
Deprecated 1
Stale 103
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.

Common questions

What is the Obsidian Hybrid Search MCP server?

Obsidian Hybrid Search is an MCP server listed in the public MCP registry as io.github.flowing-abyss/obsidian-hybrid-search. Search Obsidian vaults with hybrid full-text, fuzzy, semantic, and graph retrieval. This page covers its npm package (obsidian-hybrid-search).

Is the Obsidian Hybrid Search MCP server safe to use?

Obsidian Hybrid Search scores 49 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 20 September 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 Hybrid Search MCP server still maintained?

Obsidian Hybrid Search is still listed as active in the MCP registry. We last reached this channel on 20 September 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 Hybrid Search MCP server under?

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