io.github.iggredible/vim-mcp
NPM · VIM-MCP
Connect Claude Code to Vim/Neovim - query state, execute commands, search help, record macros
Available components
Last scanned (22 hours ago)
Scores higher than 61% of npm servers
Category Developer Tools
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security86
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- Install-script check failed: the install command fetches or executes arbitrary code (chmod_exec). An install hook runs on every machine, in CI, and on transitive installs, whether or not you ever run the server. View diagnostics → Fail
- 30 of 92 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency43
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 403 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability80
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 366 tokens (~45/item across 8 items; 7 tools + 1 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety75
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- 0 of 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "vim_execute" implies "execute" and declares no destructiveHint at all, which the MCP spec reads as destructive by default. See how to fix → Fail
- An AI judge read all 8 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 4 Nov 26 0
- Stability: 0.97 → pass security
- 3 Nov 26 0
- Stability: pass → 0.97 functional
- 28 Oct 26 0
- Stability: 0.97 → pass security
- 27 Oct 26 0
- Stability: pass → 0.97 functional
- 21 Oct 26 0
- Stability: 0.97 → pass security
- 20 Oct 26 0
- Stability: pass → 0.97 functional
- 17 Oct 26 +2
- Stability: 0.83 → pass security
- 15 Oct 26 −2
- Stability: pass → 0.80 functional
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 4 Nov 2026 · Analysed npm/vim-mcp@0.1.2
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Background: How many MCP packages publish verified provenance →
Install scripts 1 script
| Hook | Tier | Command |
|---|---|---|
| postinstall | dangerous | chmod +x ./bin/vim-mcp.js |
Background: Why install scripts are a supply-chain risk →
Dependencies 92 packages
| Packages resolved | 92 |
|---|---|
| Stale | 30 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
exit_vim ~64
Exit the selected Vim instance, with handling for unsaved changes
| Name | Type | Req | Description |
|---|---|---|---|
| action | string | – | Action to take: "check" (default - check for unsaved changes), "save_and_exit" (save all and exit), "force_exit" (exit without saving) |
No output schema declared.
No examples provided.
get_vim_state ~20
Get the current state of the selected Vim instance
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_vim_instances ~16
List all available Vim instances
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
select_vim_instance ~34
Select a Vim instance to connect to
| Name | Type | Req | Description |
|---|---|---|---|
| instance_id | string | yes | The ID of the Vim instance to select |
No output schema declared.
No examples provided.
vim_execute ~43
Execute an Ex command in the selected Vim instance
| Name | Type | Req | Description |
|---|---|---|---|
| command | string | yes | The Ex command to execute (e.g., "w", "q", "set number") |
No output schema declared.
No examples provided.
vim_record_macro ~128
Record a Vim macro from a sequence of keystrokes. Claude will translate natural language descriptions to Vim commands.
| Name | Type | Req | Description |
|---|---|---|---|
| execute | boolean | – | Whether to execute the macro immediately after recording (default: true) |
| macro_sequence | string | yes | The Vim keystroke sequence to record as a macro (e.g., "0gUwj2j" to go to start of line, uppercase word, go down 3 lines) |
| register | string | – | Register to save the macro in (default: "q"). Must be a single letter a-z or digit 0-9 |
No output schema declared.
No examples provided.
vim_search_help ~49
Search Vim help documentation for a topic and open the most relevant help section
| Name | Type | Req | Description |
|---|---|---|---|
| query | string | yes | The help topic to search for (e.g., "channel", "buffers", "windows") |
No output schema declared.
No examples provided.
How do I install the io.github.iggredible/vim-mcp server?
io.github.iggredible/vim-mcp runs locally as an npm package, launched with npx -y vim-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · vim-mcp
claude mcp add iggredible-vim-mcp -- npx -y vim-mcp
What is the io.github.iggredible/vim-mcp server?
io.github.iggredible/vim-mcp is listed in the public MCP registry as io.github.iggredible/vim-mcp. Connect Claude Code to Vim/Neovim - query state, execute commands, search help, record macros. This page covers its npm package (vim-mcp).
Is the io.github.iggredible/vim-mcp server safe to use?
io.github.iggredible/vim-mcp scores 79 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 4 November 2026. It declares an install script we flagged as high risk. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the io.github.iggredible/vim-mcp server expose?
io.github.iggredible/vim-mcp exposes 7 tools: list_vim_instances, select_vim_instance, get_vim_state, vim_execute, exit_vim, and 2 more. Their descriptions and schemas cost roughly 354 tokens of context every time the server is loaded.
Is the io.github.iggredible/vim-mcp server still maintained?
io.github.iggredible/vim-mcp is still listed as active in the MCP registry. We last reached this channel on 4 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the io.github.iggredible/vim-mcp server under?
io.github.iggredible/vim-mcp declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.