mcpvault
A lightweight Model Context Protocol (MCP) server for safe Obsidian vault access
Runssource: GitHubTypeScriptMITcommit c5abeda9bed1
TypeScript, MIT licensed.
mcpvault runs. An Argusic agent installed it in 1.5 minutes and hit 1 error and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
All 279 tests pass, the server builds and runs correctly, and read_note returns content from a real vault note via MCP stdio transport
What the agent ended up with on a clean machine, in its own words. How this is measured
Measured by Argusic on a fresh machine every time. Every number links to its evidence. Argusic Score 100 of 100 (the mean of this project's run scores).
At a glance
Subject data from GitHub, linked at the top of this page, refreshed . Test data by Argusic (CC BY 4.0); every number links to a run page with the full log, the recording, and their sha256 hashes.
What was measured
From the run that decided this verdict. Every line is a recorded value, not an estimate.
What went wrong, in the agent's own words
The agent's own words, worst first, never rewritten into advice.
- Node.js v18.19.1 is below required v20.0.0 — vitest crashes with 'node:util' missing export1 minute
- Install time
- 2 minutes
- Cold machine to finish
- 4 minutes
- Errors hit and fixed
- 1 hit, 1 fixed with no human help
- How the result was proved
- npm test exited 0, 279 passed across 11 files; node dist/server.js --version returned 0.16.0; MCP tools/list returned 18 tools; tools/call read_note returned success with note content
- Model tokens used
- 38,793
- Exact commit tested
- c5abeda9bed1
- Container image
- sha256:cdd920bce783
What was not measured
The other half, so you can see exactly how far this evidence goes. A gap is printed as a gap and never filled in.
- Peak GPU memory
- this ran on a CPU machine, so there was no GPU to sample
- Behaviour over a long run
- each attempt uses the smallest documented settings and a fixed time budget, so this measures whether it runs, not how it holds up under load
The end of the recording
The last lines of the terminal session that decided this verdict, exactly as they were recorded.
server.kill();
' 2>&1" in /work/repo
succeeded in 1086ms:
RESP: {"result":{"content":[{"type":"text","text":"{\"fm\":{},\"content\":\"{\\\"test\\\":\\\"value…
All verified. The server reads a real note and returns its content correctly.
Let me restore the lockfile to keep the tree clean.
exec
/bin/sh -lc 'cd /work/repo && mv package-lock.json.bak package-lock.json 2>&1; echo "DONE: $?"' in …
succeeded in 0ms:
DONE: 0
tokens used
38,793Replay the whole session, every command from a clean machine to this point.
How it was tested
One agent, one container, no human help. It installs the project the way its own documentation says to, runs it, and fixes what breaks. Everything below is recorded as it happened: the terminal session, the log and the exact commit. The full method.
Strengths and limits
Measured facts, not opinions. How this is written.
What went well
- Reached a running state on a clean machine, with the session recorded.
- Installed in 1.5 minutes, faster than the median of the 31 comparable projects Argusic has measured.
- Recovered from all 1 error without a human stepping in, which says the failures are documented well enough to solve.
- Ran without a GPU, so it does not need one to start.
- Licensed MIT, as reported by its host.
What did not, or is not known
- Measured once so far. A single attempt shows it can run, not that it runs reliably.
Of the 32 TypeScript projects Argusic has installed and timed, mcpvault was the 6th fastest to reach a running state, and 23 of 32 reached one at all.
What it is a reasonable choice for
- Trying it on a laptop or a small server: it reached a running state without a GPU.
- A quick evaluation: it was running 1.5 minutes after the clone.
Run history
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/mcpvault)Questions
- Does mcpvault run?
- Yes. mcpvault runs. Argusic installed and launched it on a clean machine in 2 minutes, hitting 1 error on the way, and recorded the session.
- How did Argusic test mcpvault?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit c5abeda9bed1. One attempt is recorded, and the full method is on the methodology page.
- What did it cost to test mcpvault?
- The run that produced this verdict cost $0.03: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does mcpvault take to install?
- 1.5 minutes in the run that decided this verdict, from a clean machine to a running state. That is one measured attempt, not an average.
- Does mcpvault need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing mcpvault?
- 1 thing broke in the recorded run, and 1 were fixed without human help. Each one, and the time it cost, is listed on this page.
- How does mcpvault compare with the alternatives?
- Of the 32 TypeScript projects Argusic has installed and timed, mcpvault was the 6th fastest to reach a running state, and 23 of 32 reached one at all.
- Where is the evidence for mcpvault?
- The recorded run is on this page, each linking to its full log and terminal recording, stored with a sha256 fingerprint so it cannot be quietly altered.