set_listing_status — TraydStar MCP Tool Mutating
set_listing_status
(set listing status) is one of 29 tools on the
TraydStar
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call set_listing_status from your client
- Claude Code TraydStar set_listing_status run in your project directory
- Claude Desktop TraydStar set_listing_status ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor TraydStar set_listing_status ~/.cursor/mcp.json
- VS Code TraydStar set_listing_status .vscode/mcp.json
- Zed TraydStar set_listing_status ~/.config/zed/settings.json
- Windsurf TraydStar set_listing_status ~/.codeium/windsurf/mcp_config.json
- Cline TraydStar set_listing_status ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI TraydStar set_listing_status ~/.gemini/settings.json
- Grok TraydStar set_listing_status .mcp.json (in your project root)
- ChatGPT TraydStar set_listing_status Settings → Connectors → Advanced → Developer mode
- Claude.ai TraydStar set_listing_status Settings → Connectors → Add custom connector
- LangChain TraydStar set_listing_status pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http marketplace https://traydstar.com/mcp
Other tools on this server
- search_listings
- get_listing
- get_profile
- create_listing
- save_listing
- list_saved_listings
- list_my_listings
- update_listing
- remove_listing
- list_proposals
- create_proposal
- counter_proposal
- accept_proposal
- decline_proposal
- withdraw_proposal
- send_message
- list_conversations
- read_conversation
- mark_conversation_read
- list_handshakes
- get_handshake
- confirm_handshake
- complete_handshake
- withdraw_handshake
- nudge_handshake
- get_wallet_link_message
- link_wallet
- verify_handshake_payment
This list was read from the server itself, by connecting to it and calling tools/list on 16 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.