Query Markup Documents - On-device hybrid search for markdown files with BM25, vector search, and LLM reranking
Nothing to run from here
Mindcache 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.
99/100
trust score
2
downloads a day
local
runs on your machine
92
downloads in 30d
What it does
Your Obsidian vault, connected to AI. MCP server for bridging personal knowledge with LLMs.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user mindcache-mcp '--' npx -y @augmnt-sh/mindcache
# 2 — ask your agent for something these tools do
# add_link, suggest_connections, find_gaps and 41 more
Mindcache costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Publishernot claimed
ASAll 2 servers
@augmnt-sh2 servers
2 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 Mindcache 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 Node.js — the current LTS (24) is the safe choice; npx 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 mindcache-mcp '--' npx -y @augmnt-sh/mindcacheReconnect, 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 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
44 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.
Add a [[wikilink]] to a note, connecting it to another note in the vault. Appends the link under a
No parameter schema on file.
Analyze a note and suggest other notes that could be linked to it. Uses shared tags, mentions, and content similarity to find connections.
No parameter schema on file.
Find broken links in the vault — [[wikilinks]] that point to notes that don\
No parameter schema on file.
Find orphan notes — notes with no incoming or outgoing links. These are disconnected from the knowledge graph and might need connecting.
No parameter schema on file.
Add one or more tags to a note. Tags are added to the YAML frontmatter. If the note has no frontmatter, it will be created.
No parameter schema on file.
Update YAML frontmatter properties of a note. Can add new properties or modify existing ones.
No parameter schema on file.
Rename a note by creating a copy at the new path and deleting the original. Note: Obsidian will update backlinks if the app is running.
No parameter schema on file.
Move a note to a different folder in the vault. Preserves the filename.
No parameter schema on file.
Read the full content of a note by its path. Returns the complete markdown including frontmatter.
No parameter schema on file.
Read a specific section from a note, identified by its heading. Returns content from the heading to the next heading of the same or higher level.
No parameter schema on file.
Get a note with its metadata: frontmatter properties, tags, wikilinks, and word count. Useful for understanding a note without reading it fully.
No parameter schema on file.
Read only the YAML frontmatter properties of a note. Fast way to check metadata without reading the full content.
No parameter schema on file.
Read today
No parameter schema on file.
Read all daily notes from the current week (Monday to Sunday). Useful for getting a weekly overview of activity.
No parameter schema on file.
Extract all links from a note — both [[wikilinks]] to other vault notes and external URLs. Useful for seeing what a note references.
No parameter schema on file.
Quick capture — save a thought, note, or piece of information to the vault. Auto-saves to the inbox folder. Use this for quick, unstructured captures.
No parameter schema on file.
Create a structured meeting note with attendees, agenda, notes, and action items. Uses the meeting template.
No parameter schema on file.
Log a decision using the ADR (Architecture Decision Record) format. Captures the context, decision, consequences, and alternatives considered.
No parameter schema on file.
Capture an idea with context on why it matters and potential next steps.
No parameter schema on file.
Save something new you learned — a concept, technique, insight, or skill with examples and application notes.
No parameter schema on file.
Create or update a note about a person — their role, organization, context, and interactions.
No parameter schema on file.
Bookmark a URL or resource with a summary, tags, and personal notes. Great for saving articles, videos, tools, or documentation.
No parameter schema on file.
Get an overview of your Obsidian vault: total notes, folder structure, tag distribution, and general statistics.
No parameter schema on file.
List all tags used in the vault with their occurrence counts. Samples notes to build the tag list.
No parameter schema on file.
Get the folder structure of the vault as a tree with note counts per folder. Useful for understanding vault organization.
No parameter schema on file.
Create a new note in the vault. Supports optional templates, folder routing, and frontmatter. Will not overwrite existing notes unless explicitly requested.
No parameter schema on file.
Append content to the end of an existing note. The note must already exist.
No parameter schema on file.
Replace the content under a specific heading in a note. Useful for updating a section without modifying the rest of the note.
No parameter schema on file.
Permanently delete a note from the vault. This cannot be undone.
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 Mindcache 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 99 / 100
Release 0.3.1 · scanned 14 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 score99
Findings0 threat · 0 capability
Capabilityminimal
Coveragesource
Verificationrepo
Surface digest5e6a070486fda204ac322a5bceb303ecebdb896a88b2c38cda6846e0dfc528ee
Score vectorthreat 100 → client 99
| Term | Level | What it prices | Points |
|---|---|---|---|
| capability-exposure | minimal | capability blast radius (minimal) — client exposure if the model is manipulated | −0 |
| verification-discount | repo | publisher verification (public source) — no provenance, but the source is public and inspectable | −1 |
| 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 (44 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. minimal is the level these add up to.
| Tool | Capability tags | Why the tag was assigned |
|---|---|---|
| search | no tags | |
| ask | no tags | |
| find_related | no tags | |
| find_by_tag | no tags | |
| find_by_date | no tags | |
| find_recent | no tags | |
| find_mentions | no tags | |
| read_note | no tags | |
| read_section | no tags | |
| read_summary | no tags | |
| read_properties | no tags | |
| read_today | no tags | |
| read_this_week | no tags | |
| extract_links | no tags | |
| remember | no tags | |
| remember_meeting | no tags | |
| remember_decision | no tags | |
| remember_idea | no tags | |
| remember_learning | no tags | |
| remember_person | no tags | |
| remember_reference | no tags | |
| log | no tags | |
| log_task | no tags | |
| reflect | no tags | |
| create_note | no tags | |
| append_to_note | no tags | |
| update_section | no tags | |
| delete_note | no tags | |
| add_link | no tags | |
| suggest_connections | no tags | |
| find_gaps | no tags | |
| find_orphans | no tags | |
| add_tag | no tags | |
| update_properties | no tags | |
| rename_note | no tags | |
| move_note | no tags | |
| vault_overview | no tags | |
| list_tags | no tags | |
| get_vault_structure | no tags | |
| find_tasks | no tags | |
| complete_task | no tags | |
| bulk_tag | no tags | |
| daily_notes | no tags | |
| export_note | 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 digest5e6a070486fda204
Scanned2026-10-14
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 0.3.1. Pin a release below and the command asks for exactly that one.
0.3.1
undated
latestNo release note was published with this version.
—
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 Mindcache 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.