Vitest Agent MCP Server
@vitest-agent/mcp
npm
v2.4.15
Source verified
Published by spencerbeggs — publish provenance cryptographically ties this package to that repository. That is proof of origin, not an official vendor package.
Model Context Protocol server for vitest-agent. Exposes 53 tools for agent access to test data, TDD lifecycle, and session management.
The grade answers one question — how safe is this server for you to adopt — so it is computed in two auditable stages. Nothing below is an opinion or an LLM's guess; every line is a real term the deterministic engine applied, and the same input always yields the same number.
1. Threat score — 100 − 0 = 100. What the published surface and source actually contain:
The deterministic scan raised no scored threat in the surface it inspected — the threat score stayed at 100. Capability observations and advisory notes are recorded but never lower it.
2. Client adoption risk — 100 − 0 = 100. Three small, subtract-only factors that reflect your risk in adopting it — a clean scan proves less on a powerful, unverified or barely-inspectable package, so the grade says so plainly:
✓ No adoption-risk deductions — minimal blast radius, verified enough, and fully inspected.
Capability observations and info notes are shown under Findings but never scored.
Open any row's finding below for the file, line and evidence behind a deduction.
Findings 2
low Shell/command execution in packaging/dev tooling (tools/run-tests.js)MTC-SRC-002
In a packaging/dev/install script (shipped, but not the server runtime) (`tools/run-tests.js:6`): Spawning a shell/process is command-execution capability; with unsanitized tool input it is command injection / RCE. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.
Evidence: { execFile } from "node:child_process"; import { existsSync, mkdtempSync, rmSync } from "node:fs"; import { realpath, st
Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.
Location: server tools/run-tests.js
low Dynamic module load from a non-literal in packaging/dev tooling (tools/run-tests.js)MTC-SRC-005
In a packaging/dev/install script (shipped, but not the server runtime) (`tools/run-tests.js:335`): Loading a module chosen at runtime (from a variable) can pull in and run attacker-influenced code paths. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.
Evidence: er = { load: (entry) => import(entry) }; const runTestsSemaphore = Effect.runSync(Semaphore.make(1)); function serialize
Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.
Location: server tools/run-tests.js
Tools 30
Each tool and what it can reach — statically extracted from the published source.
acceptance_metricsno sensitive capabilitycache_healthno sensitive capabilitycommit_changesno sensitive capabilityconfigureno sensitive capabilityfailure_signature_getno sensitive capabilityfile_coverageno sensitive capabilityhelpno sensitive capabilityhypothesisno sensitive capabilityinventoryno sensitive capabilitynoteno sensitive capability
Show 20 more tools ↓
pingno sensitive capabilityregister_agentno sensitive capabilityrun_testsno sensitive capabilitysettings_listno sensitive capabilitytdd_artifact_listno sensitive capabilitytdd_behaviorno sensitive capabilitytdd_goalno sensitive capabilitytdd_phase_transition_requestno sensitive capabilitytdd_progress_pushno sensitive capabilitytdd_taskno sensitive capabilitytestno sensitive capabilitytest_coverageno sensitive capabilitytest_errorsno sensitive capabilitytest_historyno sensitive capabilitytest_overviewno sensitive capabilitytest_statusno sensitive capabilitytest_trendsno sensitive capabilitytriage_briefno sensitive capabilityturn_searchno sensitive capabilitywrapup_promptno sensitive capability
What this scan could not see
- Tools were statically extracted from the published source (30 recovered), not enumerated from a running server. Tool-poisoning, Unicode-smuggling, capability and toxic-flow analysis ran on this inferred surface, but a mis-parsed registration could be missed or mis-attributed, so tool-derived findings are capped below “confirmed”. To grade the real runtime surface, scan the running server: --command "npx -y <package>".
Versions 10
Scan history per published version. The engine is deterministic — the same version always yields the same score, so a changed score means the package itself changed.
| Version | Score | Findings | Engine | Scanned |
|---|---|---|---|---|
v2.4.15 latest |
A 100/100 | 2 | 1.13.0 | 2026-09-07 |
v2.4.12 |
A 100/100 | 2 | 1.13.0 | 2026-09-05 |
v2.4.11 |
A 100/100 | 2 | 1.13.0 | 2026-08-31 |
v2.4.8 |
A 100/100 | 2 | 1.13.0 | 2026-08-28 |
v2.4.6 |
A 100/100 | 1 | 1.13.0 | 2026-08-25 |
Show 5 more versions ↓
v2.4.5 |
A 100/100 | 1 | 1.12.1 | 2026-08-25 |
v2.4.4 |
A 100/100 | 1 | 1.12.1 | 2026-08-24 |
v2.4.1 |
A 100/100 | 1 | 1.12.1 | 2026-08-23 |
v2.3.2 |
A 100/100 | 0 | 1.12.1 | 2026-08-21 |
v2.3.1 |
A 100/100 | 0 | 1.12.1 | 2026-08-20 |
Embed this score
Show this server's live Trust Score in your README, docs or website. The badge is served straight from the registry and updates automatically after every rescan — no API key needed. It links back to this page, so anyone who sees the grade can also read the findings behind it instead of taking a number on faith.
Verify this score yourself
The score above is reproducible: the same package version always yields the same result. Run it locally or over the free API — no account, no LLM, fully deterministic.
npx mcptrustchecker scan @vitest-agent/mcp --onlineMore in Learning & Documentation
stdio compatibility bridge for the hosted AgentMail MCP server
MCP server for Alfa documentation retrieval
MCP server providing Alpine.js documentation and reference
Search the official Astro framework documentation.
MCP server providing ATAG 2.0 (Authoring Tool Accessibility Guidelines) guidance for authoring tool developers
Aurais Research Reader as an MCP server — paste a paper or article, get a structured read with verbatim-verified quotes + a signed Vorion proof chain (via @vorionsys/aurais-core).