The full upstream README, mirrored here for reference. Install config, tool schemas, adoption signals, and an original overview live on the Vigile MCP listing page.
MCP server for Vigile AI Security — query trust scores for MCP servers and agent skills directly from your AI coding assistant.
Works with Claude Desktop, Claude Code, Cursor, VS Code, Windsurf, and any MCP-compatible client.
Add to your Claude Desktop config file:
~/Library/Application Support/Claude/claude_desktop_config.json%APPDATA%\Claude\claude_desktop_config.jsonOr add to your project's .mcp.json:
Add to ~/.cursor/mcp.json:
Add to .vscode/mcp.json in your project:
Add to ~/.codeium/windsurf/mcp_config.json:
Then replace "command": "npx", "args": ["-y", "vigile-mcp"] with "command": "vigile-mcp" in any config above.
Vigile scans and scores MCP servers and agent skills for security issues like tool poisoning, data exfiltration, prompt injection, and supply chain attacks. This MCP server brings those trust scores into your AI workflow — so your coding assistant can check whether a tool is safe before using it.
Covers servers from npm, Smithery, PyPI, and other registries, plus agent skills from Claude Code, Cursor, OpenClaw/ClawHub, and more.
| Tool | Description |
|---|---|
vigile_check_server | Look up trust score for an MCP server by name or package |
vigile_check_skill | Look up trust score for an agent skill (claude.md, .cursorrules, OpenClaw skills, etc.) |
vigile_scan_content | Scan raw content from a claude.md, .cursorrules, skill.md, or similar file for security issues |
vigile_search | Search the Vigile trust registry by keyword |
vigile_verify_location | Verify whether a skill uses location data safely and check for location-based attack patterns |
Once installed, your AI assistant can use these tools naturally:
"Check if @anthropic/mcp-server-filesystem is safe" "Scan this claude.md file for security issues" "Search for database MCP servers and show me their trust scores"
Vigile rates every server and skill on a 0-100 scale:
| Score | Level | Meaning |
|---|---|---|
| 80-100 | Trusted | No significant issues found |
| 60-79 | Caution | Minor issues, review recommended |
| 40-59 | Risky | Notable security concerns |
| 0-39 | Dangerous | Critical issues, do not use |
By default, vigile-mcp uses the public Vigile registry (rate-limited). For higher limits, set your API key:
Get an API key at vigile.dev.
| Tier | Scans/min | Monthly Quota |
|---|---|---|
| Free (no key) | 10 | 50 |
| Pro ($30/mo) | 60 | 1,000 |
| Pro+ ($100/mo) | 300 | 5,000 |
Registry lookups (vigile_check_server, vigile_check_skill, vigile_search) do not count against your scan quota. Only vigile_scan_content consumes scans.
THIS SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED. Vigile AI Security provides security scanning and trust scoring as informational tools only. Trust scores, scan results, and security assessments are based on automated analysis and should not be considered definitive security guarantees.
Vigile does not guarantee the detection of all security threats, vulnerabilities, or malicious behavior. Users are solely responsible for their own security decisions and should use Vigile as one component of a comprehensive security strategy.
By using this software, you agree to the Vigile Terms of Service.
MIT