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.

Vigilis

NPM · VIGILIS-MCP · SCANNED SEP 20

Gate AI-written tests: heal safe drift, refuse to hide real bugs, sign a verifiable receipt.

Available components

npm · vigilis-mcp 80
0 this week 80 Trust /100
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 Security98
  • 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
  • 34 of 107 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
Schema Quality & AI Usability69
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 374 tokens (~34/item across 11 items; 11 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management83
  • Stability observed for 25 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 11 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 11 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
Install

How do I install the Vigilis MCP server?

Vigilis runs locally as an npm package, launched with npx -y vigilis-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 · vigilis-mcp

# add to Claude Code
claude mcp add piyushpathakqa-vigilis-mcp -- npx -y vigilis-mcp
// .cursor/mcp.json
{
  "mcpServers": {
    "piyushpathakqa-vigilis-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "vigilis-mcp"
      ]
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "piyushpathakqa-vigilis-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "vigilis-mcp"
      ]
    }
  }
}
# add to Codex CLI
codex mcp add piyushpathakqa-vigilis-mcp -- npx -y vigilis-mcp
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "piyushpathakqa-vigilis-mcp": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "vigilis-mcp"
      ],
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add piyushpathakqa-vigilis-mcp --command npx --arg -y --arg vigilis-mcp
# ~/.hermes/config.yaml
mcp_servers:
  piyushpathakqa-vigilis-mcp:
    command: "npx"
    args: ["-y", "vigilis-mcp"]
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "piyushpathakqa-vigilis-mcp": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "vigilis-mcp"
      ]
    }
  }
}
# add to Vellum
assistant mcp add piyushpathakqa-vigilis-mcp -t stdio -c npx -a -y vigilis-mcp
// mcp.json
{
  "mcpServers": {
    "piyushpathakqa-vigilis-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "vigilis-mcp"
      ]
    }
  }
}
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 Sept 26 0
    • Security disclosure: unverified → fail ▼ functional
  • 19 Sept 26 −3
    • Security disclosure: fail → unverified ▼ functional
    • Stability: pass → 0.80 functional
  • 18 Sept 26 +1
    • Stability: 0.97 → pass security
  • 16 Sept 26 +1

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

  • 14 Sept 26 +1

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

  • 11 Sept 26 −3
    • Stability: pass → 0.77 functional
  • 10 Sept 26 +1
    • Stability: 0.97 → pass security
  • 8 Sept 26 +1

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

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 20 Sept 2026 · Analysed npm/vigilis-mcp@0.4.1

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 →

Dependencies 107 packages
Packages resolved 107
Stale 34
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 11 exposed · ~374 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
browser_click ~28

Click the first element matching a selector.

NameTypeReqDescription
selectorstringyesCSS or testid selector

No output schema declared.

No examples provided.

browser_navigate ~27

Navigate the browser to a URL.

NameTypeReqDescription
urlstringyesAbsolute URL to open

No output schema declared.

No examples provided.

browser_snapshot ~21

Return a trimmed HTML/a11y snapshot of the current page.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

browser_type ~39

Type text into the element matching a selector.

NameTypeReqDescription
selectorstringyesCSS or testid selector
textstringyesText to type

No output schema declared.

No examples provided.

dom_query ~30

Query the current page for elements matching a selector.

NameTypeReqDescription
selectorstringyesCSS or testid selector

No output schema declared.

No examples provided.

dom_testids ~20

List all data-testid values present on the current page.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

fs_list ~36

List entries in a workspace directory (directories end with "/").

NameTypeReqDescription
dirstring–Directory relative to the workspace root (default ".")

No output schema declared.

No examples provided.

fs_read ~32

Read a UTF-8 text file within the workspace.

NameTypeReqDescription
pathstringyesPath relative to the workspace root

No output schema declared.

No examples provided.

fs_write ~45

Write a UTF-8 text file within the workspace, creating parent directories.

NameTypeReqDescription
contentstringyesFile contents
pathstringyesPath relative to the workspace root

No output schema declared.

No examples provided.

playwright_run ~48

Run the project test suite (any supported framework) and report pass/fail counts and the artifacts directory.

NameTypeReqDescription
specPathstring–A specific spec to run; omit to run all specs

No output schema declared.

No examples provided.

test_run ~48

Run the project test suite (any supported framework) and report pass/fail counts and the artifacts directory.

NameTypeReqDescription
specPathstring–A specific spec to run; omit to run all specs

No output schema declared.

No examples provided.

Common questions

What is the Vigilis MCP server?

Vigilis is an MCP server listed in the public MCP registry as io.github.piyushpathakqa/vigilis-mcp. Gate AI-written tests: heal safe drift, refuse to hide real bugs, sign a verifiable receipt. This page covers its npm package (vigilis-mcp).

Is the Vigilis MCP server safe to use?

Vigilis scores 80 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 20 September 2026. It declares no install or post-install scripts. 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 Vigilis MCP server expose?

Vigilis exposes 11 tools: fs_read, fs_write, fs_list, browser_navigate, browser_click, and 6 more. Their descriptions and schemas cost roughly 374 tokens of context every time the server is loaded.

Is the Vigilis MCP server still maintained?

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

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