Vigilis
NPM · VIGILIS-MCP
Gate AI-written tests: heal safe drift, refuse to hide real bugs, sign a verifiable receipt.
Available components
Last scanned (21 hours ago)
Scores higher than 77% of npm servers
Category Testing and QA
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
- 33 of 104 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
- 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 120 days ago).Pass
- Security-disclosure policy not yet verified: we couldn't inspect the source repository.Unverified
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 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 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
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
- Known CVEs: partial → pass ▲ security
- Dependency health: partial → 0.86 functional
- 3 Nov 26 0
- Known CVEs: pass → partial ▼ security
- Dependency health: 0.86 → partial functional
- 30 Oct 26 +1
- Stability: 0.97 → pass security
- 29 Oct 26 −1
- Security disclosure: fail → unverified ▼ functional
- Stability: pass → 0.97 functional
- 25 Oct 26 0
- Security disclosure: unverified → fail ▼ functional
- 23 Oct 26 +1
- Stability: 0.97 → pass security
- 22 Oct 26 −1
- Stability: pass → 0.97 functional
- 20 Oct 26 0
- Security disclosure: fail → unverified ▼ 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/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 104 packages
| Packages resolved | 104 |
|---|---|
| Stale | 33 |
| 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 →
browser_click ~28
Click the first element matching a selector.
| Name | Type | Req | Description |
|---|---|---|---|
| selector | string | yes | CSS or testid selector |
No output schema declared.
No examples provided.
browser_navigate ~27
Navigate the browser to a URL.
| Name | Type | Req | Description |
|---|---|---|---|
| url | string | yes | Absolute 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.
| Name | Type | Req | Description |
|---|---|---|---|
| selector | string | yes | CSS or testid selector |
| text | string | yes | Text to type |
No output schema declared.
No examples provided.
dom_query ~30
Query the current page for elements matching a selector.
| Name | Type | Req | Description |
|---|---|---|---|
| selector | string | yes | CSS 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 "/").
| Name | Type | Req | Description |
|---|---|---|---|
| dir | string | – | 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.
| Name | Type | Req | Description |
|---|---|---|---|
| path | string | yes | Path 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.
| Name | Type | Req | Description |
|---|---|---|---|
| content | string | yes | File contents |
| path | string | yes | Path 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.
| Name | Type | Req | Description |
|---|---|---|---|
| specPath | string | – | 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.
| Name | Type | Req | Description |
|---|---|---|---|
| specPath | string | – | A specific spec to run; omit to run all specs |
No output schema declared.
No examples provided.
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
claude mcp add piyushpathakqa-vigilis-mcp -- npx -y vigilis-mcp
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 83 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 4 November 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 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 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.