get_trust_signals — DepScope MCP Tool Read-only
get_trust_signals
(get trust signals) is one of 22 tools on the
DepScope
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call get_trust_signals from your client
- Claude Code DepScope get_trust_signals run in your project directory
- Claude Desktop DepScope get_trust_signals ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor DepScope get_trust_signals ~/.cursor/mcp.json
- VS Code DepScope get_trust_signals .vscode/mcp.json
- Zed DepScope get_trust_signals ~/.config/zed/settings.json
- Windsurf DepScope get_trust_signals ~/.codeium/windsurf/mcp_config.json
- Cline DepScope get_trust_signals ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI DepScope get_trust_signals ~/.gemini/settings.json
- Grok DepScope get_trust_signals .mcp.json (in your project root)
- ChatGPT DepScope get_trust_signals Settings → Connectors → Advanced → Developer mode
- Claude.ai DepScope get_trust_signals Settings → Connectors → Add custom connector
- LangChain DepScope get_trust_signals pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http mcp https://mcp.depscope.dev/mcpOther tools on this server
- check_malicious
- check_typosquat
- check_bulk
- package_exists
- get_latest_version
- get_health_score
- install_command
- get_package_prompt
- check_package
- get_vulnerabilities
- find_alternatives
- get_migration_path
- get_breaking_changes
- pin_safe
- scan_project
- compare_packages
- check_compatibility
- resolve_error
- get_known_bugs
- get_trending
- contact_depscope
This list was read from the server itself, by connecting to it and calling tools/list on 24 September 2026. It is what
the server actually exposes, not what its listing claims.
Mutating and Read-only are read off each tool's name, not its schema — a hint, not a guarantee. The registry stores tool names only; connect the server for its live schemas.