dependency_check — QuassLabs API MCP Tool
dependency_check
(dependency check) is one of 30 tools on the
QuassLabs API
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call dependency_check from your client
- Claude Code QuassLabs API dependency_check run in your project directory
- Claude Desktop QuassLabs API dependency_check ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor QuassLabs API dependency_check ~/.cursor/mcp.json
- VS Code QuassLabs API dependency_check .vscode/mcp.json
- Zed QuassLabs API dependency_check ~/.config/zed/settings.json
- Windsurf QuassLabs API dependency_check ~/.codeium/windsurf/mcp_config.json
- Cline QuassLabs API dependency_check ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI QuassLabs API dependency_check ~/.gemini/settings.json
- Grok QuassLabs API dependency_check .mcp.json (in your project root)
- ChatGPT QuassLabs API dependency_check Settings → Connectors → Advanced → Developer mode
- Claude.ai QuassLabs API dependency_check Settings → Connectors → Add custom connector
- LangChain QuassLabs API dependency_check pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http api https://api.quasslabs.com/mcp
Other tools on this server
- alignment_gate
- blm_land_lookup
- diagram_contrast
- humanizer_score
- saas_metrics
- acceptance_criteria_validator
- coverage_check
- defect_triage
- model_advisor
- tool_advisor
- humanize
- log_audit_creator
- log_analyzer
- ticket_lint
- story_lint
- estimate_sanity
- pr_description_lint
- commit_hygiene
- readability_grade
- regex_lint
- sprint_health
- worklog_guardrail
- uploads
- feedback
- buy_credits
- rate_call
- supply_chain_scan
- describe_diagram
- convert_diagram
This list was read from the server itself, by connecting to it and calling tools/list on 29 October 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.