Vigil

● Active

io.github.LevapVeeskela/vigil

Local-first security auditor: 263 deterministic rules, LLM triage, fixes and MCP tools

Connect this server

One click to install, or copy the config below. Suits: Claude Desktop · Cursor.

Add to Cursor Add to VS CodeClaude Desktop / Claude Code: paste the config below.

Or add it manually — claude_desktop_config.json (Claude Desktop) or .cursor/mcp.json (Cursor):

{
  "mcpServers": {
    "vigil": {
      "command": "npx",
      "args": [
        "-y",
        "lv24-vigil@0.9.3",
        "mcp"
      ]
    }
  }
}
One line, from the terminal
Claude Code
claude mcp add vigil -- npx -y lv24-vigil@0.9.3 mcp
OpenAI Codex CLI
codex mcp add vigil -- npx -y lv24-vigil@0.9.3 mcp
VS Code
code --add-mcp '{"name":"vigil","type":"stdio","command":"npx","args":["-y","lv24-vigil@0.9.3","mcp"]}'

Syntax from each client's docs (Claude Code: claude mcp add; Codex: codex mcp add; VS Code: code --add-mcp). Placeholders in angle brackets are values you fill in.

A starting point — check the repository for exact arguments and setup. Restart your client after editing the config.

Category
AI & Agents
Version
0.9.3
Registry
active
Published
11/15/2026
Listed in:Official MCP registry ↗how this is checked

Is it safe? Is it maintained?

Serverdex check: Nov 17, 2026

Looks healthy: Vigil is maintained, open source.

Maintained
Active
Last commit 5 days ago (Nov 17, 2026), 0 open issues.
Official registry
Active
Published as io.github.LevapVeeskela/vigil in the official MCP registry, version 0.9.3.
Source
Open source, Apache-2.0
Public repository under the Apache-2.0 licence, 0 stars, 0 forks.
Runs
On your machine
A local npm package started by your client; it can reach whatever your user account can.
Credentials
None declared
The registry entry declares no required environment variables.
Owner
Unclaimed
Nobody has claimed this page yet; the data above comes from the registry, GitHub and the live check.

Facts only: last commit and licence from GitHub, the entry's status from the official registry, credentials from the live check. Not a code audit — run the security scan on the endpoint yourself.

On GitHub

read Nov 17, 2026
Stars
0
Forks
0
Last push
Nov 17, 2026
License
Apache-2.0

Goaigollmmcpsastsecuritystatic-analysisvulnerability-scanner

From the README

Vigil Docs: English · Русский · Documentation · llms.txt Your code. Your model. Your findings. Vigil runs 263 deterministic security rules over a repository, then — only if you ask — sends the minimum context to the model you already pay for to triage findings, review risky code, propose fixes and write a threat model. One static Go binary, one MCP server, no account, no telemetry, no Docker for a normal scan. Status: 0.10.3. If you are on 0.10.1 or older, upgrade: 0.10.2 was a security patch release with the fixes from an adversarial review and a patched Go toolchain, and 0.10.3 is the same code with refreshed package pages (changelog). The deterministic engine, CLI and MCP server are usable today. LLM output is advisory, rule coverage keeps growing, and Vigil is not a replacement for a pentest. Treat every finding as a lead to verify, not a verdict. See it work A nine-line Python file with a string-built SQL query and MD5 password hashing: No key, no network, no Docker. Add a model and the same findings get triage, context and a proposed diff: Why Vigil • Your model, your keys. OpenAI, Anthropic, Gemini, OpenRouter, Groq, DeepSeek, Mistral, xAI, OpenCode Go, Ollama, LM Studio, a local CLI or any OpenAI-compatible endpoint. No proxy, no Vigil account, no telemetry. • Deterministic first. All 263 rules run before any model call. A provider outage cannot hide a hardcoded secret, a shell injection or a disabled JWT check. • Fits the agent you already use.…

Read the full README on GitHub →

The most-starred AI & Agents servers in the index, with their live-check result.

ServerStarsLast pushLive check
Ruflo81,994Nov 2026Local / not checked
Claude Flow81,985Nov 2026Local / not checked
CodeBurn11,880Nov 2026Local / not checked
Kaneo9,825Nov 2026Local / not checked
Ha MCP7,958Nov 2026Local / not checked

Vigil: questions people ask

Is Vigil a remote or a local MCP server?
According to its entry in the official MCP registry, Vigil ships as a local package (npm) that your client starts on your machine.
Is Vigil safe to use?
Looks healthy: Vigil is maintained, open source. In detail — maintained: Active; official registry: Active; source: Open source, Apache-2.0; runs: On your machine; credentials: None declared. Serverdex check of Nov 17, 2026. This is a reading of the repository, the registry entry and the live check, not a code audit; run the Serverdex security scan on the endpoint before trusting it with real data.
Is Vigil still maintained?
Active: the repository's last commit 5 days ago. Last push Nov 17, 2026, 0 GitHub stars, Apache-2.0 licence. Read from GitHub on Nov 17, 2026.
How do I add Vigil to Claude, Cursor or VS Code?
Copy the config in "Connect this server" into your client's MCP config file (claude_desktop_config.json, ~/.cursor/mcp.json or .vscode/mcp.json), or use the one-click Add to Cursor / Add to VS Code buttons and the one-line commands for Claude Code and Codex; then restart the client.

More from LevapVeeskela

All 2 servers by LevapVeeskela →
  1. LV24 SEOFree-first SEO for agents: GSC, Yandex Webmaster/Metrika, Bing, CrUX, PSI, crawl.
Browse all AI & Agents →

Add the badge to your site

Show visitors that Vigil is listed here — it’s also the link we check for a free listing.

Vigil — listed on Serverdex

HTML — for your website

<a href="https://serverdex.io/server/io-github-levapveeskela-vigil?utm_source=badge"><img src="https://serverdex.io/brand/badge.svg" alt="Vigil — listed on Serverdex" width="123" height="40" loading="lazy"></a>

Recommended. A dofollow link from your own domain is the one that counts for search engines, and it's the link we check for a free listing.

Markdown — for your README

[![Vigil — listed on Serverdex](https://serverdex.io/brand/badge.svg)](https://serverdex.io/server/io-github-levapveeskela-vigil?utm_source=badge)

Nice for visibility, but GitHub marks README links nofollow, so it doesn't pass authority. Use the HTML badge on your site as well.

Add to CursorAdd to VS CodeOpen in Claude Code

Install buttons — for your README

[![Add to Cursor](https://serverdex.io/brand/install-cursor.svg)](https://serverdex.io/install/cursor/io-github-levapveeskela-vigil) [![Add to VS Code](https://serverdex.io/brand/install-vscode.svg)](https://serverdex.io/install/vscode/io-github-levapveeskela-vigil) [![Open in Claude Code](https://serverdex.io/brand/install-claude-code.svg)](https://serverdex.io/install/claude-code/io-github-levapveeskela-vigil)

One click opens Cursor or VS Code with this server's config prefilled; the Claude Code button lands on the one-line command. The links point at Serverdex, so when your config changes the buttons keep working.

Install buttons — HTML for your docs

<a href="https://serverdex.io/install/cursor/io-github-levapveeskela-vigil"><img src="https://serverdex.io/brand/install-cursor.svg" alt="Add to Cursor — via Serverdex" width="140" height="28"></a>
<a href="https://serverdex.io/install/vscode/io-github-levapveeskela-vigil"><img src="https://serverdex.io/brand/install-vscode.svg" alt="Add to VS Code — via Serverdex" width="147" height="28"></a>
<a href="https://serverdex.io/install/claude-code/io-github-levapveeskela-vigil"><img src="https://serverdex.io/brand/install-claude-code.svg" alt="Open in Claude Code — via Serverdex" width="180" height="28"></a>

Same buttons as plain links for a docs page or website.

Prefer a live badge with the score, stars and live check? Score badge (links to a page that explains the number and back to this listing).