Vinv runs on your own machine — the client starts it, so there is no endpoint to ping. 34 installs a week from npm. Last commit 2 Sep 2026.
Vinv runs, tests, and finds issues in your services — with zero code changes.
We read the source, 10 d ago · rules ccca72095570
What this server is able to do. For an MCP server this is often the job itself — a terminal server runs commands because that is what it is for. Listed so you know what you are plugging in, not as an accusation.
proc = subprocess.run( # noqa: S603 (fixed argv, no shell)
exec(snippet, ns) # noqa: S102 — the corpus is our own fixed text
const child = spawn(bash, ['-lc', script], hiddenBackgroundOptions({
stats.push({ file, mtimeMs: fs.statSync(path.join(root, file)).mtimeMs });
env = dict(os.environ if base is None else base)
Is this your server and something here is wrong? Tell us — corrections are free and do not require a plan.
We found places where it runs commands, builds paths or queries from values it is given. None of that is a flaw by itself — it becomes one when the code changes, and code changes quietly between releases. We re-read it on every one.
This server runs on your own machine — install it with the package manager and the client starts it for you. Package name taken from the official registry entry.
claude mcp add vinv -- npx -y vinv-mcp
{
"mcpServers": {
"vinv": {
"args": [
"-y",
"vinv-mcp"
],
"command": "npx"
}
}
}
[mcp_servers.vinv]
command = "npx"
args = ["-y", "vinv-mcp"]
{
"mcpServers": {
"vinv": {
"args": [
"-y",
"vinv-mcp"
],
"command": "npx"
}
}
}
{
"mcpServers": {
"vinv": {
"args": [
"-y",
"vinv-mcp"
],
"command": "npx"
}
}
}
This one needs environment variables set before it will start:
VINV_WORKSPACE (Optional override for the repo/workspace Vinv analyzes. Normally unset — the server uses the folder your client exposes via MCP roots, falling back to the current working directory.).
The author declared them in the registry entry; get the values from the project itself.
Returns only the unit tests affected by your current Kotlin/Android code changes.
MCP server that uses TypeScript AST to find which tests are affected by a code change
Detect API breaking changes, scan your codebase for impact, and draft the fix. Runs locally.
Code changes and unit tests by local MLX models, behind a gate a machine can run.
Shared memory and mail for your AI agents. Verified with Claude Code; other MCP clients in testing.
Drop-in MCP proxy. 71% fewer tokens. Session dedup compounds to 92%. Zero code changes.
VibeLens MCP tool for AI to visualize code changes with inline annotations in VS Code/Cursor
Upgrade intelligence for AI agents: what an upgrade changes, where it touches your code, CVE scans.
Answers built from our own checks of this server.