Config is the same across clients — only the file and path differ.
{
"mcpServers": {
"vigile": {
"args": [
"-y",
"vigile-mcp"
],
"command": "npx"
}
}
}Are you the author?
Add this badge to your README to show your security score and help users find safe servers.
MCP server for Vigile AI Security — query trust scores for MCP servers and agent skills directly from your AI coding assistant.
Run this in your terminal to verify the server starts. Then let us know if it worked — your result helps other developers.
npx -y 'vigile-mcp' 2>&1 | head -1 && echo "✓ Server started successfully"
After testing, let us know if it worked:
Five weighted categories — click any category to see the underlying evidence.
No known CVEs.
Checked vigile-mcp against OSV.dev.
Be the first to review
Have you used this server?
Share your experience — it helps other developers decide.
Sign in to write a review.
Others in security
An evil MCP server used for redteam testing
AI-powered reverse engineering assistant that bridges IDA Pro with language models through MCP.
Proof primitive for AI agents on MultiversX. Anchor file hashes on-chain as verifiable proofs.
mcpki-server is the backend infrastructure for https://www.mcpki.org, enabling secure public key management and autonomous certificate handling for large language models (LLMs).
MCP Security Weekly
Get CVE alerts and security updates for io.github.Vigile-ai/vigile-mcp and similar servers.
Start a conversation
Ask a question, share a tip, or report an issue.
Sign in to join the discussion.
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.json{
"mcpServers": {
"vigile": {
"command": "npx",
"args": ["-y", "vigile-mcp"]
}
}
}
claude mcp add --transport stdio vigile --scope user -- npx -y vigile-mcp
Or add to your project's .mcp.json:
{
"vigile": {
"command": "npx",
"args": ["-y", "vigile-mcp"]
}
}
Add to ~/.cursor/mcp.json:
{
"mcpServers": {
"vigile": {
"command": "npx",
"args": ["-y", "vigile-mcp"]
}
}
}
Add to .vscode/mcp.json in your project:
{
"servers": {
"vigile": {
"command": "npx",
"args": ["-y", "vigile-mcp"]
}
}
}
Add to ~/.codeium/windsurf/mcp_config.json:
{
"mcpServers": {
"vigile": {
"command": "npx",
"args": ["-y", "vigile-mcp"]
}
}
}
npm install -g vigile-mcp
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:
{
"mcpServers": {
"vigile": {
"command": "npx",
"args": ["-y", "vigile-mcp"],
"env": {
"VIGILE_API_KEY": "vgl_your_key_here"
}
}
}
}
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_s