Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Vigil

NPM · LV24-VIGIL

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

Available components

84 Trust /100

Last scanned (14 hours ago)

Scores higher than 75% of npm servers

Category Security

Trust breakdown (7 categories)

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 Security100
  • No malware found by supply-chain analysis.Pass
  • No known CVEs affecting this package version or its production dependencies.Pass
  • No install/post-install scripts declared.Pass
  • 0 of 6 dependencies flagged as unhealthy. View diagnostics → Pass
Provenance & Transparency100
  • Source repository is publicly reachable at the declared URL. View diagnostics → Pass
  • Cryptographically verified build provenance (signed, bound to LevapVeeskela/lv24-vigil). View diagnostics → Pass
  • Clear OSI-approved license (Apache-2.0).Pass
  • Actively maintained (last published 2 days ago).Pass
  • Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability82
  • 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
  • Context-footprint check failed: tool/resource definitions use about 2009 tokens (~118/item across 17 items; 14 tools + 3 resources), over budget; trim descriptions and params. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management20
  • Stability observed for 6 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
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 Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 14 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 16 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
  • Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
What we tested

Checks we ran (16)

  • Malware scan
  • Known CVEs
  • Install scripts
  • Dependency health
  • Source repository
  • Provenance
  • License
  • Maintenance
  • Security disclosure
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Does not apply to this package (2)

  • Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
  • Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.

The score does not measure everything. What the score does not measure →

Changelog

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.

  • 20 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.

  • 18 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.

  • 16 Nov 26 +1
    • Tool safety: pass → unverified ▼ security
    • Stability: Stability not yet verified: we do not have a sandbox capture of the MCP schema this version of the package serves yet. security
    • Capabilities: fail → unverified ▼ functional
    • Tool coverage: 100 → unverified ▼ functional
    • Schema quality: 100 → unverified ▼ functional
    • Stability: unverified → 0.03 ▲ functional
    • Package version: 0.9.3 → 0.10.1 functional
  • 15 Nov 26 81

    First indexed and scored.

Diagnostics

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 21 Nov 2026 · Analysed npm/lv24-vigil@0.10.1

Provenance Verified

A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.

Result Verified
Ecosystem npm
Reason Verified
Discovered via Registry attestation endpoint
Source repo LevapVeeskela/lv24-vigil
Certificate issuer https://token.actions.githubusercontent.com
Certificate SAN https://github.com/LevapVeeskela/lv24-vigil/.github/workflows/npm-publish.yml@refs/heads/main
Rekor log index 3931097433
Predicate type SLSA build provenance https://slsa.dev/provenance/v1
Subject digest sha512:d10eb00fe54343802cfb5f9d286c9bfb922407b97732b46a4e752fe5be589ed54af120c9f2c9386d887a37536e22d26198e720426c54ad6ac60bac84f

Background: How many MCP packages publish verified provenance →

Dependencies 6 packages
Packages resolved 6
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 14 exposed · ~1,928 tokens

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 →

Tool Tokens
vigil_baseline ~123

List, add, remove or clear accepted findings in the project baseline. Adding requires a finding ID and a reason; removed entries stop being suppressed on the next scan.

NameTypeReqDescription
actionstring–Baseline operation. Defaults to list.
findingIdstring–Finding ID (VGL-...), fingerprint (fp_...) or a unique prefix. Required for add and remove.
reasonstring–Why the finding is accepted. Required for add.
scanIdstring–Scan to resolve the finding in. Defaults to the most recent scan.

No output schema declared.

No examples provided.

vigil_dependencies ~181

Read dependency manifests and lockfiles, query the public OSV.dev database for the exact versions found and report known public advisories. Returns a text summary and the inventory, findings, coverage errors and limitations as structuredContent. Read-only: no package manager runs, no writes and no telemetry.

NameTypeReqDescription
includeDevboolean–Also query dev dependencies. Defaults to true.
maxPackagesinteger–Maximum distinct packages to query (default 200, capped at 1000).
osvBaseUrlstring–Override the OSV API root. Defaults to https://api.osv.dev; must be https, or http on a loopback host (127.0.0.1, ::1, localhost). Credentials in the URL are refused.
pathstring–Directory or repository to audit. Defaults to the server's project root.

No output schema declared.

No examples provided.

vigil_explain ~89

Explain one finding: what the rule detected, why it matters, an exploit scenario and the remediation direction. Uses the configured model when available; otherwise returns the deterministic rule description and remediation.

NameTypeReqDescription
findingIdstringyesFinding ID (VGL-...), fingerprint (fp_...) or a unique prefix.
scanIdstring–Scan to look in. Defaults to the most recent scan.

No output schema declared.

No examples provided.

vigil_fix ~113

Ask the configured model for a validated unified diff that fixes one finding. With apply=false (the default) nothing is written; with apply=true the diff is applied to the working tree and never committed.

NameTypeReqDescription
applyboolean–Apply the proposed diff to the working tree. Defaults to false (dry run).
findingIdstringyesFinding ID (VGL-...), fingerprint (fp_...) or a unique prefix.
scanIdstring–Scan to look in. Defaults to the most recent scan.

No output schema declared.

No examples provided.

vigil_hardening ~187

Run only the anti-RE hardening rules (VGL-ARE-*): release minification, debug signing, debuggable builds, backup and cleartext settings, plist transport exceptions, release obfuscation, Electron/Node isolation, inspector flags and production source maps. Reports hardening gaps, not vulnerabilities. Optionally narrow the review to one platform. Returns a text summary grouped by platform and the full scan result as structuredContent.

NameTypeReqDescription
maxFindingsinteger–Maximum findings to return (default 50, capped at 500).
minSeveritystring–Minimum severity to report.
noBaselineboolean–Ignore the baseline and report suppressed findings as active.
pathstring–Mobile or desktop project to review. Defaults to the server's project root.
platformstring–Only report findings for this platform. Defaults to all.

No output schema declared.

No examples provided.

vigil_history ~64

List the most recent stored scans with their finding, critical and high counts. Scan IDs can be passed to vigil_explain, vigil_fix, vigil_report and vigil_verify.

NameTypeReqDescription
limitinteger–Maximum number of scans to list (default 10, capped at 100).

No output schema declared.

No examples provided.

vigil_mcp_audit ~219

Run only the MCP configuration rules (VGL-MCP-*): unpinned server packages, literal secrets in env/headers/args, cleartext remote endpoints, disabled TLS verification, dangerous mounts, auto-approval and prompt-injection surfaces. Reads .mcp.json, mcp.json, mcp-config.json, claude_desktop_config.json, opencode.json[c], *.mcp.json and YAML variants; with includeUser it also reads known home-directory configs. Deterministic and offline: no configured server is started, no endpoint is contacted and nothing is written. Returns a text summary and the full audit result as structuredContent.

NameTypeReqDescription
includeUserboolean–Also read known user-level MCP configs under the home directory.
maxFindingsinteger–Maximum findings to return (default 50, capped at 500).
minSeveritystring–Minimum severity to report.
pathstring–Directory to audit. Defaults to the server's project root; the resolved path must stay inside it.

No output schema declared.

No examples provided.

vigil_report ~103

Render a stored scan as Markdown, JSON, SARIF or HTML. Without path the report is returned as text; with path it is written inside the app root and the absolute path is returned.

NameTypeReqDescription
formatstring–Report format. Defaults to md.
pathstring–Relative path inside the app root to write the report to (for example reports/vigil.md).
scanIdstring–Scan to render. Defaults to the most recent scan.

No output schema declared.

No examples provided.

vigil_review ~148

Scan only the added lines of a diff: the working-tree changes against a git ref, or a unified diff supplied by the client. Returns a text summary and the full scan result.

NameTypeReqDescription
baseRefstring–Git ref to diff against (default HEAD).
changedOnlyboolean–Review only changed files. Defaults to true; ignored when diff is supplied.
diffstring–Unified diff to review. When omitted, changed files are read from git.
pathstring–Directory or repository to review. Defaults to the server's project root.
useLlmboolean–Use the configured model for triage. Omit to use the server default.

No output schema declared.

No examples provided.

vigil_rules ~119

List the deterministic detection rules with their severity, category, languages and title. Optionally filter by category, language, severity or a free-text query.

NameTypeReqDescription
categorystring–Only rules in this category.
languagestring–Only rules that apply to this language (for example go, python, javascript, yaml). Generic rules are included.
querystring–Case-insensitive text matched against the ID, title, description, tags, CWE and OWASP fields.
severitystring–Only rules with this base severity.

No output schema declared.

No examples provided.

vigil_scan ~373

Run Vigil's deterministic security rules over a repository or directory, optionally with model triage, deep review and a threat model. Returns a text summary and the full scan result as structuredContent. Scanned code is treated as data, never executed.

NameTypeReqDescription
baseRefstring–Git ref to diff against when changedOnly is set (default HEAD).
changedOnlyboolean–Scan only files changed against baseRef (requires a git repository).
deepReviewboolean–Run the LLM deep review over high-risk files (requires a model).
diffstring–Unified diff to scan instead of the working tree. Overrides changedOnly.
disableRulesarray–Skip these rule IDs.
excludearray–Glob patterns to exclude in addition to the project defaults.
includearray–Glob patterns to include in addition to the project defaults.
maxFindingsinteger–Maximum findings to return (default 50, capped at 500).
minSeveritystring–Minimum severity to report.
modestring–Scan depth. All modes run the deterministic rules; quick is the fastest LLM budget, standard is the default, deep adds an LLM deep review when a model is configured.
noBaselineboolean–Ignore the baseline and report suppressed findings as active.
onlyRulesarray–Run only these rule IDs (for example VGL-SEC-001).
pathstring–Directory or repository to scan. Defaults to the server's project root.
threatModelboolean–Also generate an LLM threat model and attach it to the result (requires a model).
useLlmboolean–Use the configured model. Omit to use the server default; false forces deterministic rules only.

No output schema declared.

No examples provided.

vigil_status ~41

Report the engine version, project root, model configuration (with the key redacted), rule count, categories, store directory, the last scan summary and startup warnings.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

vigil_threat_model ~60

Ask the configured model for a repository threat model: assets, trust boundaries, entry points and the most likely attack paths. Requires a model.

NameTypeReqDescription
pathstring–Directory to model. Must match the server's project root; defaults to it.

No output schema declared.

No examples provided.

vigil_verify ~108

Re-scan the finding's file (or explicit paths) with the deterministic rules and report whether the same fingerprint is still present. Useful after a fix.

NameTypeReqDescription
findingIdstringyesFinding ID (VGL-...), fingerprint (fp_...) or a unique prefix.
pathsarray–Files to re-scan, relative to the scan root. Defaults to the finding's file.
scanIdstring–Scan the finding belongs to. Defaults to the most recent scan.

No output schema declared.

No examples provided.

Install

How do I install the Vigil MCP server?

Vigil runs locally as an npm package, launched with npx -y lv24-vigil 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 · lv24-vigil

# add to Claude Code
claude mcp add levapveeskela-vigil -- npx -y lv24-vigil mcp
Common questions

What is the Vigil MCP server?

Vigil is an MCP server listed in the public MCP registry as io.github.LevapVeeskela/vigil. Local-first security auditor: 263 deterministic rules, LLM triage, fixes and MCP tools. This page covers its npm package (lv24-vigil).

Is the Vigil MCP server safe to use?

Vigil scores 84 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 21 November 2026. It declares no install or post-install scripts. Its build provenance is signed and verified. 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 Vigil MCP server expose?

Vigil exposes 14 tools: vigil_scan, vigil_review, vigil_dependencies, vigil_hardening, vigil_mcp_audit, and 9 more. Their descriptions and schemas cost roughly 1,928 tokens of context every time the server is loaded.

Is the Vigil MCP server still maintained?

Vigil is still listed as active in the MCP registry. We last reached this channel on 21 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 Vigil MCP server under?

Vigil declares the Apache-2.0 licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.

What did VerifyMCP test on the Vigil MCP server?

VerifyMCP ran 16 checks on Vigil, covering Malware scan, Known CVEs, Install scripts, Dependency health and 12 more. Endpoint Security and Transport & Reachability do not apply to an npm package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.