Check the trust/security score of MCP servers, agents, skills & CLIs before you install them.
The trust layer for MCP — as an MCP tool. Let Claude (or any MCP client/agent) check whether an MCP tool is safe before installing it, look up the most trusted tools, or score an entire MCP stack — all backed by the Veragent trust registry.
⭐ Star this repo ·
uvx veragent-mcp— check any tool's trust before you install · Get your tool SGC Certified → · How we audit (open methodology) →
| Tool | What it does |
|---|---|
check_tool_trust(name) | Veragent trust score + audit state for a tool/server/agent. Use before installing. |
list_trusted_tools(query, limit) | The most trusted MCP tools, optionally filtered. |
scan_mcp_stack(mcp_config) | Score a whole mcp_settings.json — per-server risk + summary. |
Add to your claude_desktop_config.json:
{
"mcpServers": {
"veragent": {
"command": "uvx",
"args": ["veragent-mcp"]
}
}
}
Then ask Claude: "Is the playwright-mcp server safe? Check Veragent."
uvx veragent-mcp
# or
pip install veragent-mcp && veragent-mcp
VERAGENT_API_BASE — override the API base (default https://veragent.store/api/v1).Veragent labels static-analysis results as Heuristic and reserves SGC Certified for behavioral-sandbox passes. Scores are reported with this distinction.
Source-derived launch command. Check the maintainer’s required arguments and credentials before running:
uvx veragent-mcpMerge this template into ~/Library/Application Support/Claude/claude_desktop_config.json. Keep existing servers. Add any arguments, credentials, and permissions required by the maintainer; this template has not been install-tested.
{
"mcpServers": {
"io-github-lixiaowww-veragent": {
"command": "uvx",
"args": [
"veragent-mcp"
]
}
}
}Restart Claude Desktop completely for changes to take effect. Confirm the server appears connected in the client’s tool list, then try a read-only example from its documentation.
Claude Desktop setup referenceveragent-mcppypiVeragent works with any MCP-compatible client. Copy the config snippet from the Configuration section above and add it to the file shown for your client, then restart the application.
~/Library/Application Support/Claude/claude_desktop_config.jsonRestart Claude Desktop completely for changes to take effect.~/.cursor/mcp.jsonRestart Cursor for changes to take effect..vscode/mcp.jsonReload VS Code window for changes to take effect.~/.codeium/windsurf/mcp_config.jsonRestart Windsurf for changes to take effect..mcp.jsonSave at the project root, then start Claude Code in that project and review the MCP server approval prompt. Keep real credentials out of shared files.