QMD Local Search — Watchlist

MCP100 Assessment

Watchlist / Tracking

Why we’re tracking it

Track this specific mcp_server implementation and its adoption, setup drift, privilege model, and source activity.

Reviewed Oct 9, 2026 · Documentation review; complete setup workflow not independently tested

Best fit

On-device hybrid search across Markdown and document collections

What we know

On-device lexical/vector/hybrid document search with local index and MCP query/get tools, with optional shared HTTP transport.

Maintenance / activity evidence

238962 npm downloads during 2026-09-08 through 2026-10-07 for @tobilu/qmd

Tracking evidence observed Oct 9, 2026. These dated signals do not establish current maintenance. Reviewed enrichment confidence: high.

Verification gaps / watch-outs

Installation and comprehensive security have not been independently audited.
Search/retrieve document index Complete write authority is not verified.
Local environment; no provider credentials required for basic local search
Sensitive access: Private documents, Index metadata

Ensure local HTTP endpoint not exposed publicly
Local search index contains private material; do not expose HTTP listener without adequate authentication and network limits.
Local search indexes configured directories and caches document content into SQLite. Privacy depends on local machine and selected paths.
Unknown vulnerabilities, deployment environment and client privileges not exhaustively reviewed.

Full authority, access and evidence limits are available in Review context and Access & risk.

Popularity

· 239k package downloads / 30 days

Downloads observed Oct 9, 2026.

Exact npm package @tobilu/qmd; provider interval 2026-09-08–2026-10-07 (inclusive); observed 2026-10-09.

All limitations / Review context

What changed in documented permissions, distribution and MCP integration of QMD Local Search before the next review?

No substantiated blocker to accurately qualified PUBLIC RADAR TRACKING observed in the scoped cited documentation; material caveats are required on the public page.

Ensure local HTTP endpoint not exposed publicly
Local search index contains private material; do not expose HTTP listener without adequate authentication and network limits.
Local search indexes configured directories and caches document content into SQLite. Privacy depends on local machine and selected paths.
Search/retrieve document index
Local environment; no provider credentials required for basic local search
Depends on configured local process, connected account and remote APIs; review first-party privacy terms for any hosted component.
Sensitive access: Private documents, Index metadata
Complete write authority is not verified.
Installation, client compatibility and comprehensive security have not been independently audited. Authentication and access depend on the configured services.
Unknown vulnerabilities, deployment environment and client privileges not exhaustively reviewed.
Exact dated attributable activity evidence
Write actions/tool inventory not confirmed against exact tool documentation; listed action classes remain illustrative or context-dependent. Empty inventory does not establish read-only.
Local model/index setup needs resources
Shared HTTP MCP needs network security controls
Search index can contain private texts
No independent release lifecycle audit; do not claim precise activity date.

Original activity observations

238962 npm downloads during 2026-09-08 through 2026-10-07 for @tobilu/qmd

Technical identity

npm/@tobilu/qmd

Exact implementation source: https://www.npmjs.com/package/@tobilu%2Fqmd ↗
Reviewed resource type: MCP Server
Package identity: npm:@tobilu/qmd

Evidence & Sources

Evidence basis: Recorded source evidence
Setup runtime verification: Not independently runtime-tested by MCP100 for this setup workflow.

Reviewed Oct 9, 2026 · Latest source observation Oct 9, 2026

Package registry ↗
@tobilu/qmd
Recorded package identity, distribution or download evidence.
Includes references whose attribution is not established.
GitHub repository ↗
tobi/qmd
Recorded repository material and project history.

Setup · Watchlist

Install & Agents

Publisher instructions.

Source evidence observed Oct 14, 2026.

Additional setup details required — see the specific gaps below.

Warning

No third-party MCP installation, execution, connection, payment or mutation performed.
Official documentation may not prove currently operational service.
Installing CLI does not by itself create a collection.
Targeted 2026-10-13 re-research: Publisher provides qmd mcpServers launch config; must install and index collections first.
Publisher provides qmd mcpServers launch config; must install and index collections first.
Publisher MCP client config documented; collection creation/indexing are separate prerequisites.
Batch08 V3 source-specific finding: Local QMD status validates index, not MCP client registration.
Global installation alone is not registering QMD MCP; collection/index/model setup required.
Recorded publisher instruction; runtime not tested.
Client-specific example. Not interchangeable with VS Code servers or Codex TOML. No runtime test.

Install / connect
Publisher instructions
Install QMD CLI then configure qmd MCP subcommand; index your local collections before expecting results.
publisher documented install or connect · Publisher instructions
npm install -g @tobilu/qmd
Configure / authenticate
MCP100 setup guide
Install QMD CLI then configure qmd MCP subcommand; index your local collections before expecting results.
{ "mcpServers": { "qmd": { "args": [ "mcp" ], "command": "qmd" } } }
Check connection
Suggested check
Publisher CLI `qmd status` reports local index state; this is separate from MCP client tool discovery.
Remove / uninstall / revoke
MCP100 setup guide
Generic client guidance (not publisher-specific uninstall): unregister MCP entry in the chosen client. If installed globally, remove the npm package separately. Revoke provider access separately through account controls, where supported. This does not erase local data or revoke funds/credentials automatically.
Unregister the named MCP entry from the actual host separately from removing a global npm install; no claim that either revokes remote credentials.
Local QMD does not need a remote vendor credential in the documented on-device use; vendor credential revocation not applicable.

Official Documentation & Sources

What it does

On-device lexical/vector/hybrid document search with local index and MCP query/get tools, with optional shared HTTP transport.

Capability: Files & Knowledge
Resource type: MCP Server
Best fit: On-device hybrid search across Markdown and document collections

Representative uses

Index notes
Hybrid BM25/vector search
Fetch documents
Check index status

Limitations

Local model/index setup needs resources
Shared HTTP MCP needs network security controls
Search index can contain private texts
Ensure local HTTP endpoint not exposed publicly
No independent release lifecycle audit; do not claim precise activity date.

Reviewed access

Access & risk

Review the exact access boundary before connecting this MCP to accounts, credentials, or sensitive data.

Authentication: Local environment; no provider credentials required for basic local search
Permissions: Search/retrieve document index
Data handling: Depends on configured local process, connected account and remote APIs; review first-party privacy terms for any hosted component.
Cost: unknown
Risk and cautions: Ensure local HTTP endpoint not exposed publicly

Access scope and cautions

Write actions: Not verified
Sensitive access: Private documents Index metadata
Risk level: moderate
Security notes: Local search index contains private material; do not expose HTTP listener without adequate authentication and network limits. Local search indexes configured directories and caches document content into SQLite. Privacy depends on local machine and selected paths.

The reviewed evidence does not establish the complete write authority of this MCP. Consult the unresolved evidence before granting write access.

FAQ

Based on reviewed evidence as of 2026-10-09. Watchlist tracking is not a recommendation or a security certification.

Which tasks are documented for this implementation?

The reviewed tasks include: Index notes; Hybrid BM25/vector search; Fetch documents; Check index status.

What setup and authentication are documented?

Recorded installation/entrypoint step: qmd mcp. Recorded transport: stdio, streamable_http. Prerequisites: Compatible MCP client. Client notes: Source docs and package may evolve; install according to confirmed release. These are the documented setup details, not a claim that installation or client compatibility was independently tested. Authentication: Local environment; no provider credentials required for basic local search

Can it modify data or perform write operations?

Not verified. The available evidence does not establish the complete write authority. Recorded permission context: Search/retrieve document index

What data-handling boundary should I consider?

Depends on configured local process, connected account and remote APIs; review first-party privacy terms for any hosted component. Recorded sensitive-access context: Private documents; Index metadata.

What limitations and risks should I check before use?

Ensure local HTTP endpoint not exposed publicly. Local model/index setup needs resources. Shared HTTP MCP needs network security controls. Search index can contain private texts. No independent release lifecycle audit; do not claim precise activity date. Local search index contains private material; do not expose HTTP listener without adequate authentication and network limits. Local search indexes configured directories and caches document content into SQLite. Privacy depends on local machine and selected paths. Unknown vulnerabilities, deployment environment and client privileges not exhaustively reviewed.