vintrace_get_vessel_details_report — vintrace MCP by usefulapi MCP Tool
vintrace_get_vessel_details_report
(vintrace get vessel details report) is one of 34 tools on the
vintrace MCP by usefulapi
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call vintrace_get_vessel_details_report from your client
- Claude Code vintrace MCP by usefulapi vintrace_get_vessel_details_report run in your project directory
- Claude Desktop vintrace MCP by usefulapi vintrace_get_vessel_details_report ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor vintrace MCP by usefulapi vintrace_get_vessel_details_report ~/.cursor/mcp.json
- VS Code vintrace MCP by usefulapi vintrace_get_vessel_details_report .vscode/mcp.json
- Zed vintrace MCP by usefulapi vintrace_get_vessel_details_report ~/.config/zed/settings.json
- Windsurf vintrace MCP by usefulapi vintrace_get_vessel_details_report ~/.codeium/windsurf/mcp_config.json
- Cline vintrace MCP by usefulapi vintrace_get_vessel_details_report ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI vintrace MCP by usefulapi vintrace_get_vessel_details_report ~/.gemini/settings.json
- Grok vintrace MCP by usefulapi vintrace_get_vessel_details_report .mcp.json (in your project root)
- ChatGPT vintrace MCP by usefulapi vintrace_get_vessel_details_report Settings → Connectors → Advanced → Developer mode
- Claude.ai vintrace MCP by usefulapi vintrace_get_vessel_details_report Settings → Connectors → Add custom connector
- LangChain vintrace MCP by usefulapi vintrace_get_vessel_details_report pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http vintrace https://vintrace.usefulapi.io/mcpOther tools on this server
- vintrace_list_work_orders
- vintrace_list_wine_batches
- vintrace_get_vessel
- vintrace_list_lab_requests
- vintrace_list_trial_blends
- vintrace_search_transactions
- vintrace_list_barrel_treatments
- vintrace_list_blocks
- vintrace_list_block_assessments
- vintrace_list_bookings
- vintrace_list_bulk_intakes
- vintrace_search_fruit_intakes
- vintrace_list_stock_dispatches
- vintrace_list_shipments
- vintrace_list_cost_transactions
- vintrace_list_brand_allocations
- vintrace_get_purchase_order
- vintrace_list_inventory
- vintrace_lookup_stock_item
- vintrace_get_stock_item
- vintrace_list_stock_item_notes
- vintrace_list_products
- vintrace_get_product
- vintrace_list_sales_orders
- vintrace_get_sales_order
- vintrace_list_parties
- vintrace_get_party
- vintrace_get_work_order
- vintrace_list_work_orders_v6
- vintrace_search_items
- vintrace_add_stock_item_note
- vintrace_assign_work_order
- vintrace_deactivate_booking
This list was read from the server itself, by connecting to it and calling tools/list on 24 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.