obsidian-local-rest-api
A secure REST API and Model Context Protocol (MCP) server for your vault.
Runs with mockssource: GitHubhomepageTypeScriptMITcommit 0278df908a91
TypeScript, MIT licensed.
obsidian-local-rest-api runs, with stand-ins for the services it depends on. An Argusic agent installed it in 2 minutes and hit 2 errors on a clean machine with no GPU, and the whole session was recorded.
npm install and npm run build succeed. All 1015 unit tests pass after fixing certificate key size; 1 test remains blocked on Node 18 ESM limitation.
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 82 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.
- 6 certificates tests failed: SSL routines::ee key too small (RSA 1024-bit keys rejected by OpenSSL 3.0 on Node 18)5 minutes
- mcpSessionfulClient test fails: pkce-challenge requires ESM VM API unsupported by Node 18 (project requires >=22)2 minutes
- Install time
- 2 minutes
- Cold machine to finish
- 17 minutes
- Errors hit and fixed
- 2 hit, 1 fixed with no human help
- How the result was proved
- npm test: 1015 passed, 1 failed (Node 18 ESM gap); npm run build: exit 0
- Model tokens used
- 647,721
- Exact commit tested
- 0278df908a91
- 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
- Behaviour against real services
- this run was verified against stand-in services only
The end of the recording
The last lines of the terminal session that decided this verdict, exactly as they were recorded.
The project **builds successfully**. I fixed the 6 failing certificate tests by bumping the RSA key…
exec
/bin/sh -lc 'cd /work/repo && npm test 2>&1 | grep -E "''^(Test Suites:|Tests:)" | head -3' in /wor…
succeeded in 19856ms:
Test Suites: 1 failed, 15 passed, 16 total
Tests: 1 failed, 1015 passed, 1016 total
exec
/bin/sh -lc "echo '{\"install_succeeded\": true, \"launch_succeeded\": true, \"install_minutes\": 2…
succeeded in 0ms:
{"install_succeeded": true, "launch_succeeded": true, "install_minutes": 2, "errors": [{"msg": "6 c…
tokens used
647,721Replay 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
- Installed in 2 minutes, faster than the median of the 21 comparable projects Argusic has measured.
- Licensed MIT, as reported by its host.
What did not, or is not known
- Only reached a running state against stand-in services, so nothing here proves it works against the real ones.
- Hit 2 errors during setup, 1 of which were not solved.
- Measured once so far. A single attempt shows it can run, not that it runs reliably.
Of the 22 TypeScript projects Argusic has installed and timed, obsidian-local-rest-api was the 3rd fastest to reach a running state, and 17 of 22 reached one at all.
Run history
| tested by | attempt | outcome | score | cost USD | when |
|---|---|---|---|---|---|
| Argusic Runner | 1/3 | Runs with mocks | 82.00 | 0.12 |
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/obsidian-local-rest-api)Questions
- Does obsidian-local-rest-api run?
- obsidian-local-rest-api runs, with mocks standing in for external services. Argusic installed and launched it on a clean machine in 2 minutes, hitting 2 errors on the way, and recorded the session.
- How did Argusic test obsidian-local-rest-api?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit 0278df908a91. One attempt is recorded, and the full method is on the methodology page.
- What did it cost to test obsidian-local-rest-api?
- The run that produced this verdict cost $0.12: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does obsidian-local-rest-api take to install?
- 2 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 obsidian-local-rest-api need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing obsidian-local-rest-api?
- 2 things 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 obsidian-local-rest-api compare with the alternatives?
- Of the 22 TypeScript projects Argusic has installed and timed, obsidian-local-rest-api was the 3rd fastest to reach a running state, and 17 of 22 reached one at all.
- Where is the evidence for obsidian-local-rest-api?
- 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.