@bitbonsai/mcpvault
Installed, started with no arguments, no environment and no input, and listed its tools. Run 2026-11-16.
Needs to start: nothing
Returns a result when called with no setup: 2 of 2 tools tried
Contacts while installing and starting: nothing
What it contacted
Nothing besides the npm registry it was installed from. Watched from outside its sandbox while it was installed and started with no input. Its tools may still contact things when called.
Starting it
npx -y @bitbonsai/mcpvault@0.18.4
Installing a package runs its code. Use a sandbox for anything you have not read.
Calling its tools
2 tools that take no input and look read-only were called once with nothing. 2 returned a result.
list_directory | Returned a result under 0.1 s · 65 characters |
get_vault_stats | Returned a result under 0.1 s · 328 characters |
During the calls it contacted nothing it had not already contacted.
Only tools whose names read like looking something up, with no required input, are tried, five at most. Tools that need input, and anything that sounds like it changes or sends something, are not called.
What its tools tell an agent
In the tool descriptions, nothing that talks about the user, other tools or private files, or uses hidden characters.
Found by simple pattern rules in each tool's description (up to 3,000 characters), quoted as written. Parameter descriptions are not scanned. A clean result is not a safety review.
Tools
read_note path, prettyPrint
Read a note from the Obsidian vault
write_note path, content, frontmatter, mode
Write a note to the Obsidian vault
patch_note path, oldString, newString, replaceAll
Efficiently update part of a note by replacing a specific string. This is more efficient than rewriting the entire note for small changes.
list_directory path, prettyPrint
List files and directories in the vault (includes non-note filenames, while read/write tools remain note-only)
delete_note path, confirmPath, trashMode
Delete a note from the Obsidian vault (requires confirmation). Supports permanent delete, vault trash, or system trash.
13 more tools
search_notes query, limit, searchContent, searchFrontmatter, caseSensitive, pathPrefix, excludePaths, prettyPrint
Search for notes in the vault by content or frontmatter
move_note oldPath, newPath, overwrite
Move or rename a note in the vault
move_file oldPath, newPath, confirmOldPath, confirmNewPath, overwrite
Move or rename any file in the vault (binary-safe, file-only, requires confirmation)
read_multiple_notes paths, includeContent, includeFrontmatter, prettyPrint
Read multiple notes in a batch (max 10 files)
update_frontmatter path, frontmatter, merge
Update frontmatter of a note without changing content
get_notes_info paths, prettyPrint
Get metadata for notes without reading full content
get_frontmatter path, prettyPrint
Extract frontmatter from a note without reading the content
manage_tags path, operation, tags
Add, remove, or list tags in a note
get_vault_stats recentCount, prettyPrint
Get vault statistics including total notes, folders, size, and recently modified files. Useful for understanding vault scope before batch operations.
list_all_tags prettyPrint
List all tags across the vault with occurrence counts. Returns both frontmatter tags and inline #hashtags, deduplicated and sorted by frequency. Useful for discovering existing tags before creating or organizing notes.
wiki_link document, prettyPrint
Read an Obsidian wiki link. Accepts the same syntax as Obsidian: [[Document Name]] or [[Document Name|Display Text]], including table-authored escapes like [[Document Name\|Display]] and path-qualified links like [[folder/Document Name]]. A #fragment suffix in the input is ignored. Searches the vault for an exact basename match (or exact vault-relative path match when the name contains '/') and returns the file's content. When multiple files share the basename, picks the first (vault root first, then alphabetical by path) and lists the other paths in structuredContent.alternatives. Content is returned bare — ready for direct use in context.
get_note_outline path, prettyPrint
Get the heading structure of a note without reading its full content. Returns headings with level, text, and line number. Use this first to navigate large notes efficiently, then call read_note_lines to read only the section you need.
read_note_lines path, startLine, endLine, prettyPrint
Read a specific line range from a note. Use after get_note_outline to read only the section you need instead of the full file.
Descriptions are the package's own words, cut at 3,000 characters. Treat them as data.
Install facts
| License | MIT |
|---|---|
| Needs | node >=22.12.0 |
| Source | github.com/bitbonsai/mcpvault |
| Install scripts | None declared by it or anything installed with it. |
| Tarball | sha512-s0J3IYp69+/3AAa1k/CxfGA1906WH+rOEI/xIA5GWT2EI/fbN0mhayBUmoPQgyLgj9GAeJIS+8onMXeKTdke6w== |
Versions reported
| Version | Run | Result | Tools |
|---|---|---|---|
| 0.18.4 | 2026-11-16 | Starts with no setup | 18 |
| 0.18.3 | 2026-11-12 | Starts with no setup | 18 |
Check this report yourself
This site did not write the report. A public job on a GitHub-hosted machine did: the run, from this commit of the open-source runner. GitHub signed a token that names that job and the hash of the report, so any edit since would show.
Report as JSONExact text and tokenHow to verify it
Show it on your README
[](https://bragproof.smaverk.com/r/%40bitbonsai/mcpvault)
New version out? Ask for a fresh report.