get_vendor_fact_sheet — StackSwap MCP Tool Read-only
get_vendor_fact_sheet
(get vendor fact sheet) is one of 23 tools on the
StackSwap
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call get_vendor_fact_sheet from your client
- Claude Code StackSwap get_vendor_fact_sheet run in your project directory
- Claude Desktop StackSwap get_vendor_fact_sheet ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor StackSwap get_vendor_fact_sheet ~/.cursor/mcp.json
- VS Code StackSwap get_vendor_fact_sheet .vscode/mcp.json
- Zed StackSwap get_vendor_fact_sheet ~/.config/zed/settings.json
- Windsurf StackSwap get_vendor_fact_sheet ~/.codeium/windsurf/mcp_config.json
- Cline StackSwap get_vendor_fact_sheet ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI StackSwap get_vendor_fact_sheet ~/.gemini/settings.json
- Grok StackSwap get_vendor_fact_sheet .mcp.json (in your project root)
- ChatGPT StackSwap get_vendor_fact_sheet Settings → Connectors → Advanced → Developer mode
- Claude.ai StackSwap get_vendor_fact_sheet Settings → Connectors → Add custom connector
- LangChain StackSwap get_vendor_fact_sheet pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http stackswap https://stackswap.ai/api/mcpOther tools on this server
- inspect_available_connections
- request_system_connection
- start_stack_audit
- complete_stack_audit
- generate_data_layer_blueprint
- generate_build_prompt
- search_tools
- get_tool_details
- find_overlaps
- suggest_swaps
- scan_stack
- recommend_partner
- recommend_stack
- compare_tools
- compare_tools_n_way
- search_content
- get_kb_article
- get_category_landscape
- detect_stack_from_text
- get_buyer_questions
- get_renewal_strategy
- submit_correction
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.