fetch — Velox TriFit: Virtual Try-On API MCP Tool Read-only
fetch
(fetch) is one of 18 tools on the
Velox TriFit: Virtual Try-On API
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call fetch from your client
- Claude Code Velox TriFit: Virtual Try-On API fetch run in your project directory
- Claude Desktop Velox TriFit: Virtual Try-On API fetch ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor Velox TriFit: Virtual Try-On API fetch ~/.cursor/mcp.json
- VS Code Velox TriFit: Virtual Try-On API fetch .vscode/mcp.json
- Zed Velox TriFit: Virtual Try-On API fetch ~/.config/zed/settings.json
- Windsurf Velox TriFit: Virtual Try-On API fetch ~/.codeium/windsurf/mcp_config.json
- Cline Velox TriFit: Virtual Try-On API fetch ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI Velox TriFit: Virtual Try-On API fetch ~/.gemini/settings.json
- Grok Velox TriFit: Virtual Try-On API fetch .mcp.json (in your project root)
- ChatGPT Velox TriFit: Virtual Try-On API fetch Settings → Connectors → Advanced → Developer mode
- Claude.ai Velox TriFit: Virtual Try-On API fetch Settings → Connectors → Add custom connector
- LangChain Velox TriFit: Virtual Try-On API fetch pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http velox-trifit-developer https://studio.v3lox.com/partner/trifit/mcpOther tools on this server
- get_trifit_account
- get_trifit_profile
- get_trifit_allowance
- list_trifit_library
- prepare_trifit_upload
- upload_trifit_image
- create_trifit_try_on
- get_trifit_try_on
- show_trifit_try_on
- get_guest_demo_status
- prepare_guest_upload
- create_try_on
- get_try_on
- search
- get_integration_example
- get_partner_access_requirements
- get_partner_application_guide
This list was read from the server itself, by connecting to it and calling tools/list on 5 November 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.