Vaara MCP server
io.github.vaaraio/vaara·v2.17.0·15 starsAccountable autonomy proxy: gating, tamper-evident audit, time anchor for every action
not scanned yet
15 stars1.8k downloads/wk
Reviews
Write oneNobody has reviewed Vaara yet.
If you have run it, two minutes of your experience saves the next person an afternoon.
Vaara tools
No tool declarations could be read from the package source. They show once the server is installed.
How Vaara compares
Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.
- Safety score
- 82/100
- higher than 63% of 48,243 servers
- GitHub stars
- 15
- more than 90% of 28,706 servers
- Downloads a week
- 1,807
- more than 95% of 12,306 servers with a package
Release history: 26 versions in the registry since 2026-09-16, latest 2026-10-29, typically one every 1 day.
Install Vaara in Claude Code, Cursor or VS Code
claude mcp add vaara -- uvx vaara
What the publisher says
From the Vaara repository's README, as published. We do not edit it. Read it on GitHub
Accountable Autonomy.
A verifiable receipt for every autonomous action, checkable by anyone.
Your AI agent transferred the funds, wrote the file, called the tool. Later, someone who does not trust you asks you to prove exactly what it did and why: a regulator, an auditor, a customer after an incident. Your own logs will not settle it, because you could have edited them.
Quick start
pip install vaara # Python: CLI, MCP proxy, server
brew tap vaaraio/tap && brew install vaara # macOS: CLI + menu-bar app (built from source)
npm install @vaara/client # TypeScript client for the HTTP APIimport vaara
@vaara.govern
def transfer_funds(to: str, amount: float) -> str:
...That is the whole thing. Every call to a governed function is risk-scored and decided against your policy before the body runs. An allowed call runs, and the decision, the call, and the outcome land in a hash-chained, tamper-evident record anyone can verify offline. Sign it at export (vaara trail export) for third-party proof. Records persist to ~/.vaara/trail/audit.db by default, so evidence survives restarts. Python 3.10+, zero runtime dependencies.
Both deny and escalate raise vaara.Blocked, since an escalation means a human has not answered yet. Run the example above on a fresh install and it will raise: with no outcome history the scorer's confidence interval is wide, and a tx.transfer escalates on the interval's upper bound even though its point estimate sits under the allow threshold. That is the intended direction to fail, and it settles. Feeding real outcomes back through report_outcome narrows the interval, and the same call starts allowing after a few dozen clean results. To watch decisions without acting on them while that happens, start with @vaara.govern(shadow=True).
Check a receipt with nothing installed
Shortened. The full README is on GitHub.
Nothing above is checked by us. What we check is on the safety report.
Grade history
- 2026-10-15downgradeA → Bscore 82: subprocess with shell=True
- 2026-09-19restoreB → Ascore 89
Vaara: common questions
- Is Vaara MCP server safe?
- Mostly: it is graded B (82/100). Read the Vaara safety report
- How do I install Vaara?
- It runs on your machine. Copy the Claude Code, Cursor, VS Code or Claude Desktop config from the install section.
- Does Vaara need an API key?
- Not as far as the registry entry and our scan can tell: no credentials are declared or required.
- Is Vaara maintained?
- The last commit was 21 days ago (2026-10-15). The latest release is v2.17.0.
- How does Vaara compare with other MCP servers?
- safety score 82/100 (higher than 63% of 48,243 servers); github stars 15 (more than 90% of 28,706 servers); downloads a week 1,807 (more than 95% of 12,306 servers with a package). Full comparison.