Query Markup Documents - On-device hybrid search for markdown files with BM25, vector search, and LLM reranking
Nothing to run from here
Markdown Vault is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
94/100
trust score
8
downloads a day
local
runs on your machine
514
downloads in 30d
What it does
Generic markdown vault MCP with hybrid search
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user pvliesdonk-markdown-vault-mcp '--' uvx markdown-vault-mcp
# 2 — ask your agent for something these tools do
# get_history, get_diff, git_sync and 39 more
Markdown Vault costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Publishernot claimed
PVAll 5 servers
pvliesdonk5 servers
4 categories
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Installation
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. This one runs on your machine: your client starts Markdown Vault as a process under your own user, with your files and your network, so the tool surface below is what it can do to your computer rather than to a server somewhere else. Its scan result is on the Security tab — read the surface before you approve it.
Claude Codedeclared by this listing
This is a public server: you run it yourself and this marketplace is not in the path. You need uv (docs.astral.sh/uv): uvx comes with it. Claude Code registers it in one command; --scope user makes it available in every project. The '--' is in quotes so that PowerShell passes it on.
claude mcp add --scope user pvliesdonk-markdown-vault-mcp '--' uvx markdown-vault-mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
Free on mcprush, and it runs from its publisher’s own package: this marketplace is not in the path, so there is no key of ours to hold and no card to add.
What it asks of you
Nothing is required, but it can take MARKDOWN_VAULT_MCP_KV_STORE_URL (Persistent-state backend URL shared by every pvl-core subsystem that needs state. `memory://` is in-process and lost on restart; `file:///path` persists on one), MARKDOWN_VAULT_MCP_TOOLS_ALLOW (Comma-separated explicit tool names this instance exposes; every other tool is hidden from listings and cannot be invoked. Names matching no registered tool are), MARKDOWN_VAULT_MCP_TOOLS_DENY (Comma-separated explicit tool names hidden from this instance (absent from listings, cannot be invoked). Names matching no registered tool are inert. Mutually e), MARKDOWN_VAULT_MCP_SERVER_NAME (Rename this server instance; defaults to the project name.), MARKDOWN_VAULT_MCP_INSTRUCTIONS_EXTRA (Operator context appended to the generated MCP instructions.), MARKDOWN_VAULT_MCP_INSTRUCTIONS (Legacy: replaces the entire generated MCP instructions text (deprecated; prefer the _EXTRA variant).), FASTMCP_LOG_LEVEL (Log level for FastMCP internals and app loggers (DEBUG / INFO / WARNING / ERROR / CRITICAL). The -v CLI flag overrides to DEBUG.), FASTMCP_ENABLE_RICH_LOGGING (Set false for plain or structured JSON log output.), OLLAMA_HOST (Ollama server URL for the ollama embedding provider. Bare (not MARKDOWN_VAULT_MCP_-prefixed), matching the Ollama ecosystem convention.), OPENAI_API_KEY (OpenAI API key for the openai embedding provider, and the fallback key for the summarize tool when MARKDOWN_VAULT_MCP_SUMMARIZE_OPENAI_API_KEY is unset. Bare (n), VOYAGE_API_KEY (Voyage AI API key for the voyage embedding provider. Bare (not MARKDOWN_VAULT_MCP_-prefixed), matching the OPENAI_API_KEY / OLLAMA_HOST convention. Setting it n), OPENAI_BASE_URL (Bare fallback for MARKDOWN_VAULT_MCP_OPENAI_BASE_URL (embeddings). For the summarize tool it only routes traffic when an API key already enables the feature; it), OPENAI_EMBEDDING_MODEL (Bare fallback for MARKDOWN_VAULT_MCP_OPENAI_EMBEDDING_MODEL.), MARKDOWN_VAULT_MCP_BUILD_TIMEOUT_S (Maximum seconds an index-backed tool or resource waits for the FTS index to become queryable during a cold-start background build before raising IndexUnavailabl), MARKDOWN_VAULT_MCP_DRAIN_TIMEOUT_S (Maximum seconds an index-querying read tool waits for the IndexWriter to drain when called with wait_for_pending_writes=true. On timeout the tool answers from t), MARKDOWN_VAULT_MCP_SOURCE_DIR (Path to the markdown vault directory. Required — the server refuses to start without it. Symbolic links inside the vault are followed on Python 3.13+.), MARKDOWN_VAULT_MCP_READ_ONLY (Set to true to hide the write tools (write, edit, append, delete, rename, move_folder, fetch, git_sync, the okf_* tools, create_upload_link) and serve a search-), MARKDOWN_VAULT_MCP_WRITE_PROTECT_EXISTING (Set to true to refuse a write that would overwrite an existing file when no if_match etag is supplied. Deliberate replacement (read first, pass if_match) still), MARKDOWN_VAULT_MCP_DISABLE_APPS_UI (Hide the MCP Apps UI tools (browse_vault, show_context) from the tool listing for clients that do not render MCP Apps panels.), MARKDOWN_VAULT_MCP_INDEX_PATH (Path to the SQLite FTS5 index file; unset keeps the index in memory. Set it for persistence across restarts.), MARKDOWN_VAULT_MCP_STATE_PATH (Path to the change-tracking state file. Defaults to {SOURCE_DIR}/.markdown_vault_mcp/state.json.), MARKDOWN_VAULT_MCP_EMBEDDINGS_PATH (Path to the numpy embeddings file; required to enable semantic search.), MARKDOWN_VAULT_MCP_INDEXED_FIELDS (Comma-separated frontmatter fields promoted to the tag index for structured filtering. Changing it cold-rebuilds the index once on next startup; SEARCHABLE_FIEL), MARKDOWN_VAULT_MCP_REQUIRED_FIELDS (Comma-separated frontmatter fields required on every document; documents missing any are excluded from the index.) if you want to set them.
What it writes
One config entry your client uses to start the process locally. A local server runs with your file system and your network, which is why it is priced without metering.
What you approve
42 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
No parameter schema on file.
No parameter schema on file.
No parameter schema on file.
No parameter schema on file.
No parameter schema on file.
No parameter schema on file.
No parameter schema on file.
No parameter schema on file.
No parameter schema on file.
No parameter schema on file.
No parameter schema on file.
No parameter schema on file.
No parameter schema on file.
No parameter schema on file.
No parameter schema on file.
No parameter schema on file.
No parameter schema on file.
No parameter schema on file.
No parameter schema on file.
No parameter schema on file.
No parameter schema on file.
No parameter schema on file.
No parameter schema on file.
No parameter schema on file.
No parameter schema on file.
No parameter schema on file.
No parameter schema on file.
No parameter schema on file.
No parameter schema on file.
No parameter schema on file.
No parameter schema on file.
No parameter schema on file.
No parameter schema on file.
No parameter schema on file.
No parameter schema on file.
No parameter schema on file.
No parameter schema on file.
No parameter schema on file.
No parameter schema on file.
No parameter schema on file.
No parameter schema on file.
No parameter schema on file.
Free
$0 forever
- Every tool, no call limit
- No card, and mcprush charges nothing for it
- Source published under MIT
- Runs on your machine — nothing of it reaches our gateway
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install Markdown Vault or to call it, at any volume.
Call allowance · this installenforced at the gateway
Monthly allowance, in calls
—
—
Alert at 80% · then the tool returns a normal MCP error
Used this month: —
ATrust score 94 / 100
Release 5.1.0 · scanned 15 Oct 2026
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
Threat score100
Client score94
Findings11 threat · 1 capability
Capabilityhigh
Coveragesource
Verificationsource
Surface digest6b3dafebbc27eb17258babbb47914e3f63764660b92e1a5ef974fca4456be266
Score vectorthreat 100 → client 94
| Term | Level | What it prices | Points |
|---|---|---|---|
| capability-exposure | high | capability blast radius (high) — client exposure if the model is manipulated | −6 |
| verification-discount | source | publisher verification (provenance) — cryptographic build provenance ties the artifact to its source | −0 |
| coverage-honesty | source | inspection depth (source) — how much of the target the scan could see | −0 |
score = clamp(round(threatScore − E_cap − E_ver − E_cov), 0, 100). No model, no opinion, no network call at scoring time: the same methodology version against the same bytes always produces this number, and every line above is a field of the report rather than a summary of it.
What the scan could actually read
A grade is only as meaningful as its coverage, so the scanner publishes its own depth before it publishes its result.
Tool surfaceread
Implementation sourceread
Package metadataread
Live transportnot available
Tools were statically extracted from the published source (42 recovered), not enumerated from a running server. Tool-poisoning, Unicode-smuggling, capability and toxic-flow analysis ran on this inferred surface, but a mis-parsed registration could be missed or mis-attributed, so tool-derived findings are capped below “confirmed”. To grade the real runtime surface, scan the running server: --command "npx -y <package>".
Capability — what it could do if the model were manipulated
Tags derived from each tool’s schema and the implementation, not from what the tool calls itself. high is the level these add up to.
| Tool | Capability tags | Why the tag was assigned |
|---|---|---|
| get_history | no tags | |
| get_diff | no tags | |
| git_sync | no tags | |
| get_backlinks | no tags | |
| get_outlinks | no tags | |
| get_broken_links | no tags | |
| get_orphan_notes | no tags | |
| get_most_linked | no tags | |
| get_connection_path | no tags | |
| embeddings_status | no tags | |
| get_index_status | no tags | |
| search | no tags | |
| read | no tags | |
| list_documents | no tags | |
| list_folders | no tags | |
| list_tags | no tags | |
| stats | no tags | |
| get_similar | no tags | |
| get_toc | no tags | |
| get_recent | no tags | |
| get_context | no tags | |
| get_conventions | no tags | |
| okf_validate | no tags | |
| write | no tags | |
| edit | no tags | |
| append | no tags | |
| delete | no tags | |
| rename | no tags | |
| move_folder | no tags | |
| fetch | untrusted-input | untrusted-input: keyword "fetch" |
| okf_convert_links | no tags | |
| okf_generate_index | no tags | |
| okf_seed_log | no tags | |
| okf_verify | no tags | |
| browse_vault | untrusted-input | untrusted-input: keyword "browse" |
| vault_context | no tags | |
| show_context | no tags | |
| vault_graph_neighborhood | no tags | |
| vault_graph_hubs | no tags | |
| vault_list | no tags | |
| vault_read | no tags | |
| vault_search | no tags |
Toxic-flow graph
The lethal trifecta, checked as a graph rather than as a checklist: untrusted input, a sensitive source and an external sink have to meet before there is a path worth worrying about.
The public result for this release does not print the flow graph, so there is nothing to show here. That is not the same as "no paths were found": what the scan did read is above, under coverage.
Supply chain and provenance
Integrityfirst-seen
Surface digest6b3dafebbc27eb17
Scanned2026-10-15
This is the first scan of this surface here, so there is nothing yet to compare it against.
Every result on this tab comes from one deterministic pass over the published package — offline, rule by rule, and auditable line by line above. Same methodology version, same bytes, same score.
Release history
Always latest — the install command names no version, so it installs the newest release when it runs; the current release on file is 5.1.0. Pin a release below and the command asks for exactly that one.
5.1.0
7 Oct 2026
latestNo release note was published with this version.
5.0.0
27 Sep 2026
No release note was published with this version.
4.2.0
13 Sep 2026
No release note was published with this version.
4.1.0
undated
- The version this listing was on when mcprush began following its releases. The registry was not asked when it shipped, so this row carries no date.
—
no reviews yet
Who can review
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Sign in to write one
Any signed-in account that does not publish Markdown Vault can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
No reviews yet
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.