mcp-vigil@0.3.0
VERIFIED· not startedPublisher claims: "Security audit CLI for MCP (Model Context Protocol) configurations. Find leaked API keys, excessive permissions, and vulnerable servers before attackers do." Observed in sandbox: no network, touches nothing outside the project, writes no memory.
Coverage
Not started: dependency install failed; the server itself was not observed.- Tested
- the dependency install step · every file read, file written and host contacted by what ran
- Not tested
- server startup · the tool list · tool behavior
What this means for the label: Verified here covers what ran. The server's tools were not exercised with a real credential, so nothing about their behavior is asserted; the credential summary below says what to do with that.
Before you give it your token
- It will ask for
- no credential variables read in the code
- Where it talks to
- no vendor host named in the code
- What the honeypot saw
- no credential files read · no network
- What we could not test
- server startup · the tool list · tool behavior
Connect it under the guard. Not started: dependency install failed; the server itself was not observed. The code names no credential variable; the guard pins the network to what the honeypot saw and logs every call.
Never paste a credential into a chat, a ticket or a report, including ours. How the guard holds it.
Is [email protected] safe to install?
KillerSkills ran it in the KillerSkills honeypot sandbox (2 scenarios; not started: dependency install failed; the server itself was not observed) on 2026-11-10 and scored it 86/100 (Verified). In what ran, nothing we could detect went wrong: no undeclared network egress, no credential reads, no persistent instruction writes. What it does with a real credential was not observed; the static findings and the publisher carry the rest of the score. Summary: no network, touches nothing outside the project, writes no memory.
Behavior trace
Honeypot run · 0 s · 2 scenarios · 0 deviationsStatic findings
if cmd.startswith("npx ") and "@" not in cmd.split()[-1]:Fix: Pin versions and sources; vendor anything fetched at install time.description=f"Server '{server.get('name', 'unknown')}' uses npx without a pinned version. Running latest can introduce breaking changes or compromised updates.",Fix: Pin versions and sources; vendor anything fetched at install time.remediation=f"Move the secret to a separate .env file and reference it: {key}=${{EXTERNAL_SECRET}}",Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.if re.search(r'\$\{?\w+\}?|process\.env|import\.meta\.env', line, re.IGNORECASE):Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.title="MCP server using unpinned version (npx without @version)",Fix: Pin versions and sources; vendor anything fetched at install time.("UNPINNED-VERSION", "medium", "Warn about npx packages without pinned versions"),Fix: Pin versions and sources; vendor anything fetched at install time."""Pin unpinned npx versions with a placeholder."""Fix: Pin versions and sources; vendor anything fetched at install time.print(f" {Colors.YELLOW}💡 Add to your .env: {change['env_var_added']}=your_real_value{Colors.RESET}")Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.# Check if npx package uses a specific version or always latestFix: Pin versions and sources; vendor anything fetched at install time.remediation=f"Pin a specific version: npx @scope/[email protected] instead of npx @scope/package",Fix: Pin versions and sources; vendor anything fetched at install time.Cost to the agent
Tokens estimated at four characters each. The tool list is re-read by the agent on every turn, so it is the number to compare between servers that do the same job: ranked across the index.
Known vulnerabilities
No advisories in OSV for mcp-vigil@0.3.0 as of 4d ago. This is the package itself, not its dependencies.