supply_chain_scan — QuassLabs API MCP Tool
supply_chain_scan
(supply chain scan) 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 supply_chain_scan from your client
- Claude Code QuassLabs API supply_chain_scan run in your project directory
- Claude Desktop QuassLabs API supply_chain_scan ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor QuassLabs API supply_chain_scan ~/.cursor/mcp.json
- VS Code QuassLabs API supply_chain_scan .vscode/mcp.json
- Zed QuassLabs API supply_chain_scan ~/.config/zed/settings.json
- Windsurf QuassLabs API supply_chain_scan ~/.codeium/windsurf/mcp_config.json
- Cline QuassLabs API supply_chain_scan ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI QuassLabs API supply_chain_scan ~/.gemini/settings.json
- Grok QuassLabs API supply_chain_scan .mcp.json (in your project root)
- ChatGPT QuassLabs API supply_chain_scan Settings → Connectors → Advanced → Developer mode
- Claude.ai QuassLabs API supply_chain_scan Settings → Connectors → Add custom connector
- LangChain QuassLabs API supply_chain_scan pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http api https://api.quasslabs.com/mcpOther 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
- dependency_check
- 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
- 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.