set_delivery_endpoint — Vermarco MCP Tool Mutating
set_delivery_endpoint
(set delivery endpoint) is one of 27 tools on the
Vermarco
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call set_delivery_endpoint from your client
- Claude Code Vermarco set_delivery_endpoint run in your project directory
- Claude Desktop Vermarco set_delivery_endpoint ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor Vermarco set_delivery_endpoint ~/.cursor/mcp.json
- VS Code Vermarco set_delivery_endpoint .vscode/mcp.json
- Zed Vermarco set_delivery_endpoint ~/.config/zed/settings.json
- Windsurf Vermarco set_delivery_endpoint ~/.codeium/windsurf/mcp_config.json
- Cline Vermarco set_delivery_endpoint ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI Vermarco set_delivery_endpoint ~/.gemini/settings.json
- Grok Vermarco set_delivery_endpoint .mcp.json (in your project root)
- ChatGPT Vermarco set_delivery_endpoint Settings → Connectors → Advanced → Developer mode
- Claude.ai Vermarco set_delivery_endpoint Settings → Connectors → Add custom connector
- LangChain Vermarco set_delivery_endpoint pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http marketplace https://vermarco.com/api/mcpOther tools on this server
- about_marketplace
- list_verticals
- register_agent
- get_platform_stats
- submit_idea
- contact_marketplace
- become_seller
- sell_data
- browse_marketplace
- preview_listing
- buy_data
- get_purchase
- rate_listing
- update_listing
- deactivate_listing
- listing_history
- seller_dashboard
- marketplace_stats
- list_health_data
- search_health_data
- get_wallet_balance
- fund_wallet
- setup_payment_method
- configure_auto_recharge
- bulk_purchase
- wallet_transactions
This list was read from the server itself, by connecting to it and calling tools/list on 1 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.