MCPVault (Obsidian)
Score = points from our five tests (install, handshake, maintenance, docs, license). Not a quality or security rating. Methodology
- Install20/20
- Handshake30/30
- Maintenance25/25
- Docs15/15
- License10/10
Tested npm @bitbonsai/mcpvault 0.18.3 (MIT; repo bitbonsai/mcpvault). Installed pinned with scripts off (npm --ignore-scripts) and launched: initialize and tools/list over stdio succeeded with no credentials and listed 18 tools (no tool annotations). Real calls: 3 of 3 real function calls passed. Real calls ran with the vault path argument the README documents (a one-note test vault).
Tool-call test (2026-11-13 UTC, direct MCP stdio client, no LLM): pass. 3 of 3 real function calls passed. Evidence: local test run, Nov 13, 2026 UTC.
Transport (tested 2026-11-13 UTC): stdio
Token cost (estimate): approx. 2152 tokens, cl100k estimate (18 tools, measured 2026-11-13 UTC, version 0.18.3). This is an estimate from our testing of the tool names, descriptions and input schemas, counted with cl100k_base.
Permissions: 10 read, 7 write (state-changing), 1 unclassified · Auth: none · Rate limit: unknown · Pricing unit: unknown
Auth: none. Rate limit: unknown. Pricing unit: unknown.
delete_note— write (state-changing)get_frontmatter— readget_note_outline— readget_notes_info— readget_vault_stats— readlist_all_tags— readlist_directory— readmanage_tags— write (state-changing)move_file— write (state-changing)move_note— write (state-changing)patch_note— write (state-changing)read_multiple_notes— readread_note— readread_note_lines— readsearch_notes— readupdate_frontmatter— write (state-changing)wiki_link— unclassifiedwrite_note— write (state-changing)
handshake and tools listed without a recorded key or OAuth
Score 100/100 · Tools 18 · Token cost approx. 2,152 tokens · Compare · Last tested 2026-11-13 UTC · Version tested 0.18.3 · Package @bitbonsai/mcpvault · Repo bitbonsai/mcpvault
Summary: MCPVault (Obsidian) completed an MCP handshake without credentials and exposed 18 tools.
Evidence summary
- Handshake
- pass
- Tools listed
- 18
- Context cost
- approx. 2152 tokens, cl100k estimate (18 tools, measured 2026-11-13 UTC, version 0.18.3; an estimate) ranking · add up your servers' context cost
- API key
- No key needed for the tools we called
- Tested
- 2026-11-13 UTC
Test results
| Test | Result | Points | Evidence |
|---|---|---|---|
| install | pass | 20 | npm install @bitbonsai/mcpvault (Node 20, Linux) succeeded in 1s. |
| handshake | pass | 30 | MCP initialize + tools/list over stdio succeeded with no credentials; 18 tools listed in 3.8s. |
| maintenance | pass | 25 | Repo pushed 2 days before test; 1,722 GitHub stars. |
| docs | pass | 15 | README over 3,000 chars; install instructions present; mcpServers config example present. Check of the package's own README (README shipped in npm package). |
| license | pass | 10 | MIT (OSI-approved). |
Local-model readiness
Token cost (estimate): approx. 2152 tokens, cl100k estimate for 18 tools · about 26% of an 8k context. This is an estimate from our testing (counted with cl100k_base).
Small-model friendly (schema heuristic, not a model result): unknown.
Not tested
Small-model task runs: Not yet tested.
What we tested and what we didn't
Tested on 2026-11-13 UTC
- Install from the registry
- We connected with no credentials and asked for its tool list: it listed 18 tools (Method details: MCP
initializethentools/list) - Maintenance signals (last push, archived/deprecated status)
- Docs (README length, install and config example)
- License (OSI-approved or not)
- Token cost (estimate)
Not tested
- Security: not audited (no code review, no permission or data-flow analysis)
- Real tasks (no functional task runs yet)
- Behaviour with real credentials or a real account
- Performance, rate limits or load
- Correctness of results beyond the listed tasks
Methodology: how we test. A high score means it installs and responds, not that giving it access to your data carries no risk.
Known security issues
Not yet checked.
Monthly roundup: MCP security issues, October 2026.
Tool list changes
Baseline recorded from the 2026-11-13 UTC test run; changes appear after the next test.
Snapshot hash (fingerprint of the tool list)
addecbe30683: SHA-256 of the canonical tool names, descriptions and input schemas. If it changes, the tool list changed.
Raw test record (JSON)
{
"name": "@bitbonsai/mcpvault",
"version": "0.18.3",
"registry": "npm",
"status": "working",
"tested": "2026-11-13",
"tools_count": 18,
"deprecated": false,
"archived": false,
"tests": {
"install": [
"pass",
20,
"`npm install @bitbonsai/mcpvault` (Node 20, Linux) succeeded in 1s."
],
"handshake": [
"pass",
30,
"MCP `initialize` + `tools/list` over stdio succeeded with no credentials; 18 tools listed in 3.8s."
],
"maintenance": [
"pass",
25,
"Repo pushed 2 days before test; 1,722 GitHub stars."
],
"docs": [
"pass",
15,
"README over 3,000 chars; install instructions present; `mcpServers` config example present. Check of the package's own README (README shipped in npm package)."
],
"license": [
"pass",
10,
"MIT (OSI-approved)."
]
}
}Install
npx -y @bitbonsai/mcpvault
Pin the version we tested
npx -y @bitbonsai/mcpvault@0.18.3
tested 2026-11-13 UTC. Newer versions may differ and were not tested by us.
{
"mcpServers": {
"mcpvault-obsidian": {
"command": "npx",
"args": [
"-y",
"@bitbonsai/mcpvault@0.18.3"
]
}
}
}Tools listed
read_note, write_note, patch_note, list_directory, delete_note, search_notes, move_note, move_file, read_multiple_notes, update_frontmatter, get_notes_info, get_frontmatter, manage_tags, get_vault_stats, list_all_tags, wiki_link, get_note_outline, read_note_lines
Quick config
{
"mcpServers": {
"mcpvault-obsidian": {
"command": "npx",
"args": [
"-y",
"@bitbonsai/mcpvault"
]
}
}
}Add to config Opens the config generator with this server selected.
Setup
- Install. Run
npm install @bitbonsai/mcpvault(Node 20). This is the exact command we ran on 2026-11-13 UTC. - Configure. Add the mcpServers entry below to your MCP client config.
- Verify. Restart the client and check that tools/list returns tools (18 in our test).
{
"mcpServers": {
"mcpvault-obsidian": {
"command": "npx",
"args": [
"-y",
"@bitbonsai/mcpvault"
]
}
}
}Test history
- 2026-11-13 UTC: New
Related: Best productivity MCP servers
FAQ
Is MCPVault (Obsidian) deprecated?
No. @bitbonsai/mcpvault was not deprecated or archived when we last tested it on 2026-11-13 UTC.
What replaces MCPVault (Obsidian)?
Nothing; MCPVault (Obsidian) is not deprecated as of 2026-11-13 UTC.
Does MCPVault (Obsidian) need an API key?
No. It completed an MCP handshake with no credentials and listed 18 tools.
Embed the badge
Every tested server gets a free embeddable badge. It shows the current score and test date and expires after 90 days. Testing is free; payment never changes a score.