vitest-agentSAFE
A Vitest reporter that keeps results of test runs focused for LLMs
Overview
From the repository's own README, as read at the audited commit. Badges and raw HTML are left out.
Monorepo for the vitest-agent package family — a Vitest plugin, reporter, CLI, MCP server and Claude Code plugin that turn a test run into structured intelligence for LLM coding agents. It produces shape-tailored console output, persists every run to SQLite at an XDG-derived path and exposes test status, coverage, failure history and trends over a CLI and an MCP server.
User documentation lives at vitest-agent.dev. This README is the developer-facing hub for working in the repo itself.
Packages
The seven publishable packages live under packages/. @vitest-agent/sdk has no internal dependencies; the dependency flow is plugin → reporter → ui → sdk, with the sidecar reaching consumers through the CLI.
The sidecar's per-platform binaries ship as optionalDependencies from four sub-packages — @vitest-agent/sidecar-darwin-arm64, -linux-arm64
bf810af73936OBSERVED · 2026-10-12Connect
Built from this server's own package name, version and transport as found in its source — not copied from anyone's documentation, so it cannot drift against a page we do not control.
claude mcp add docs -- npx -y [email protected]
{
"mcpServers": {
"docs": {
"command": "npx",
"args": [
"-y",
"[email protected]"
]
}
}
}Exposed tools (2)
2 read · 0 write · 0 destructive.
| Tool | Risk | Description |
|---|---|---|
int | read | Integration |
vitest-agent | read | Vitest test data, coverage analysis, TDD orchestration and notes for LLM coding agents, served by the vitest-agent MCP server and recorded by lifecycle hooks. |
Trust audit
SAFEgrade B · trust 87/100 Nothing in the source contradicts what it says it does. Grade A is reserved for packages that have also passed the behavioural sandbox.
| Layer | What it checks | Result |
|---|---|---|
| L0 | Provenance & inventory | PASS |
| L1 | Static analysis of the code | PASS |
| L2 | Instruction surface (what it tells the agent) | PASS |
| L3 | Class-specific surface | PASS |
| L4 | Behavioural (sandbox) | SKIPPED |
What the source does
- Filesystem
- declared (4 observation(s))
- Network
- declared (1 observation(s))
- Shell
- declared (1 observation(s))
- Dependencies
- not all pinned
- Secrets in source
- none-found
Findings (19)
.markdownlint.json
.envrc
.gitmodules
.markdownlint-cli2.jsonc
.markdownlint.json
it("matches PM-mediated exec (pnpm exec, npm exec, yarn exec, bun x)", () => {import packageJson from "../../package.json" with { type: "json" };localPaths: ["../../website/lib/models/cli"],
import { makeTestLayer } from "../../utils/layers.js";export { DataStoreTestLayer, makeTestLayer } from "../../src/testing/layers.js";localPaths: ["../../website/lib/models/engine"],
@okfit/plugin, @savvy-web/silk
@savvy-web/bundler
@savvy-web/bundler
@savvy-web/bundler
magic-string, @savvy-web/bundler, vite
read `process.env` / `process.cwd()` to thread input into the engine's
3. The reporter, MCP server, and sidecar read `process.env.VITEST_AGENT_*` at startup. The reporter records `actor_type='agent'` plus the canonical UUIDs on every `test_runs` row. The MCP server popul
* [The MCP Server Survives Post-Connect Crashes](51-the-mcp-server-survives-post-connect-crashes.md) - unhandledRejection and uncaughtException guards keep the MCP process alive after a client connect
Gates applied: no_behavioural_pass.
bf810af73936full audit observations/trust-audit/mcp-server/spencerbeggs__vitest-agent.json · Report an issue / request a re-scanAudit history
Every audit this server has had. A grade with a past is a grade somebody is still checking.
| Date | Source | Verdict | Grade | Score | Change |
|---|---|---|---|---|---|
| 2026-10-12 | bf810af73936 | SAFE | B | 87 | first audit |
Questions
What is the @vitest-agent/mcp MCP server?
A Vitest reporter that keeps results of test runs focused for LLMs
What tools does @vitest-agent/mcp expose?
2 in total: 2 read-only, 0 that write, and 0 that can delete or overwrite. Every one is listed on this page with its risk.
Is @vitest-agent/mcp safe to connect to an agent?
The audit found nothing in the source that contradicts what it says it does, and graded it B (87/100). Grade A is held back for packages that have also passed a sandboxed behavioural run, which is why a clean server reads B.
What credentials does @vitest-agent/mcp need?
No credential environment variables were found in its source, so it appears to need none.
How current is this page?
The grade is for one exact copy of the source (bf810af73936), read on 2026-10-12. The repository is watched and re-audited when it changes.