obsidian-hybrid-search

MCPcommunity
v0.13.16flowing-abyssMITUpdated 4d agonpmGitHub

[![npm version](https://img.shields.io/npm/v/obsidian-hybrid-search)](https://www.npmjs.com/package/obsidian-hybrid-search) [![Tests](https://github.com/flowing-abyss/obsidian-hybrid-search/actions/workflows/ci.yml/badge.svg)](https://github.com/flowing-a

Automatically indexed from public sources. Not yet verified by the developer on Forge.Claim this listing →
1kDownloads/wk
4d agoLast update
Package
Authorflowing-abyss
LicenseMIT
Version0.13.16
Sourcenpm+mcp-registry
npmobsidian-hybrid-search
GitHubflowing-abyss/obsidian-hybrid-search
Trust Status
A
95/100Trusted
✓Listed in Forge index+10/10
—Publisher identity verified+0/25
→ Publisher: run `forge publish` from the package repo to claim ownership
—Ed25519 publish signature+0/10
→ 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>" }
✓CVE scan · clean+30/30
✓Static analysis · clean+20/20
✓npm provenance (Sigstore)+5/5
Paste into Claude Code, Cursor, or any AI assistant to fix all gaps
StatusCommunity-indexed
PublisherUnverified
SignatureUnsigned
Domain—
Provenance✓ Sigstore-verified · 8dee1a2
Dependencies✓ 60 resolved+ · none vulnerable
Tool surface—
Security scan✓ Cleanv0.13.8 · 19d ago
PROMPTdescriptionLinks to undeclared domains: img.shields.io, npmjs.com
EvalsNone
IndexedJun 12, 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

[![npm version](https://img.shields.io/npm/v/obsidian-hybrid-search)](https://www.npmjs.com/package/obsidian-hybrid-search) [![Tests](https://github.com/flowing-abyss/obsidian-hybrid-search/actions/workflows/ci.yml/badge.svg)](https://github.com/flowing-a

Keywords
obsidiansearchhybrid-searchsemantic-searchfulltext-searchsqlitemcp