Vinv MCP server

Read from the package source without running it. The installed server may list more.

• blast_radius

  Transitive callers (upstream) and callees (downstream) of a symbol in the observed call graph. Answers "if this is wrong, what could be implicated or affected".

• callers_of

  The observed direct callers of a symbol, with call counts. Answers "who calls this at runtime".

• coverage_of

  Execution coverage: with a symbol, its call count / ok-error / timing; without one, every executed symbol ranked by call volume. Answers "what ran and how much".

• rank_suspects

  Call FIRST when investigating a bug, error, or failing request/test: ranks symbols by fault suspiciousness (Ochiai SBFL) over the pass/fail spectra of all captured requests. Answers "which functions should I look at first for this failure" \u2014 cheaper and more targeted than reading source files.

• relevant_to

  Rank the codebase by graph relevance to one or more symbols you name \u2014 the SAME typed-edge personalized-PageRank walk that composed your context pack, re-anchored on your choice. Use when you have found symbols that matter and want what surrounds them, ranked: it answers "what else is relevant to THESE", which semantic search (vinv_query) and plain traversal (blast_radius) cannot. Returns wal

• slice

  Backward dynamic slice to a symbol: the caller chain from the request root down to it, annotated with the argument/return values observed at each frame. Answers "what flowed in to reach this call" \u2014 use when tracing how a bad value or state reached a function.

• values_of

  Value profile for a symbol across the captured run(s): per-argument and return type mix, null-rate, numeric/length ranges, and most-common values. Answers "what does this function actually receive and return at runtime" \u2014 use this for ground truth instead of inferring inputs/outputs from source.

• vinv_deadcode

  List Python definitions (functions, classes, methods) that NOTHING in the repository references \u2014 dead code \u2014 found by static analysis of the source. Needs no prebuilt index and no runtime, so it works immediately on any workspace and returns each unused symbol with its file and line. Use it to find safe-to-remove code; before deleting a reported symbol, still confirm it is not reference

• vinv_feedback

  After you have acted on vinv_query results (opened the files, made the edit), call this once to record whether they helped, passing the vinv_decision_id from that response. Use reward in [-1,1], where 1 is fully useful and -1 is harmful. This trains retrieval for this workspace.

• vinv_index

  Build or refresh Vinv's semantic code index for THIS workspace. The build runs in the BACKGROUND and this call returns IMMEDIATELY with status \u2014 it never blocks. Call with no arguments to start/refresh the index and read its status; pass rebuild=true to force a full rebuild from scratch. Until the first build completes, vinv_query returns a "still indexing" notice, so call this once up front

• vinv_ingest_runwrite action

  Report a test run you performed, so it appears in the Journey and Findings views. Supply one entry per check with the unit you exercised, a scenario name, and the pass/fail verdict \u2014 the verdict is the one thing traces cannot supply. A unit is usually an HTTP endpoint ("METHOD /path"), but a repo with no service has units too: a CLI invocation ("RUN <command>") or a driven function ("CALL mod

• vinv_list_candidates

  Ranked optimization candidates from the captured traces, each with the evidence behind it and a playbook for that class of waste (cache, fanout, n-plus-1, per-call, serial-async, wait, gc-pressure, alloc-churn, mem-leak). Read this before attempting any performance work \u2014 it reports what the traces actually measured, not a static guess.

• vinv_query

  Semantic code search over the prebuilt index of this workspace. Use INSTEAD of grep/glob when looking for code by meaning or behavior rather than an exact string \u2014 e.g. "where are auth tokens refreshed", "what validates uploads". Returns the most relevant symbols (functions/classes) ranked, with file paths and scores, in a single call.

• vinv_run_statuswrite action

  What vinv currently holds for this workspace: capture sessions, whether an external run has been ingested, endpoint/coverage/issue counts, and the number of ranked candidates. Call this to check whether an ingest landed.

• vinv_session

  Read what Vinv has observed about this workspace at runtime, and drive its automated fix/optimize runs ("episodes"), from chat. READ: action="requests" (what became of each sweep/fix you QUEUED \u2014 a queued sweep does not always dispatch, and this is the only durable record of why one did not), action="trajectory" (every episode so far \u2014 what was tried, whether it verified, the reward, the

• why_did_this_runwrite action

  The entry-point triggers and call paths that led to a symbol running. Answers "why was this function invoked".

• Code scan5 source files scanned25/25
• –Live reliabilityno gateway calls yet and no remote to proben/a
• –Tool poisoningtools not inspected (local package is not executed); not countedn/a
• Auth qualitylocal package, no credentials required12/15
• Maintenancelast push 12 days ago15/15
• Maintainer identityregistry namespace matches repository owner7/10

Safety score

91/100

higher than 85% of 48,255 servers

Tools

16

the typical server has 7

Tools that change things

19%

typical: 0%. Fewer write tools means less an agent can break

GitHub stars

48

more than 94% of 28,688 servers

Downloads a week

74

more than 55% of 12,191 servers with a package

Vinv: common questions

Is Vinv MCP server safe?

Yes, by our scan: it is graded A (91/100). Read the Vinv safety report

How do I install Vinv?

It runs on your machine. Copy the Claude Code, Cursor, VS Code or Claude Desktop config from the install section.

Does Vinv need an API key?

No secret keys are declared. It reads 1 setting from the environment.

Is Vinv maintained?

The last commit was 15 days ago (2026-10-20). The latest release is v0.0.5.

What can I use instead of Vinv?

Servers from other publishers that do the same job: Qase Test Management MCP server.

How does Vinv compare with other MCP servers?

safety score 91/100 (higher than 85% of 48,255 servers); tools 16 (the typical server has 7); tools that change things 19% (typical: 0%. Fewer write tools means less an agent can break). Full comparison.