unsubscribe — South Dakota Code MCP Tool
unsubscribe
(unsubscribe) is one of 38 tools on the
South Dakota Code
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call unsubscribe from your client
- Claude Code South Dakota Code unsubscribe run in your project directory
- Claude Desktop South Dakota Code unsubscribe ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor South Dakota Code unsubscribe ~/.cursor/mcp.json
- VS Code South Dakota Code unsubscribe .vscode/mcp.json
- Zed South Dakota Code unsubscribe ~/.config/zed/settings.json
- Windsurf South Dakota Code unsubscribe ~/.codeium/windsurf/mcp_config.json
- Cline South Dakota Code unsubscribe ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI South Dakota Code unsubscribe ~/.gemini/settings.json
- Grok South Dakota Code unsubscribe .mcp.json (in your project root)
- ChatGPT South Dakota Code unsubscribe Settings → Connectors → Advanced → Developer mode
- Claude.ai South Dakota Code unsubscribe Settings → Connectors → Add custom connector
- LangChain South Dakota Code unsubscribe pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http south-dakota-code https://gateway.pipeworx.io/south-dakota-code/mcpOther tools on this server
- ask_pipeworx
- ask_pipeworx_beta
- ask_pipeworx_grounded
- search_within
- deep_research
- discover_tools
- resolve_entity
- compare_entities
- subscribe
- list_subscriptions
- recent_alerts
- entity_profile
- recent_changes
- validate_claim
- company_facts
- scan_dependency
- bet_research
- polymarket_arbitrage
- polymarket_edges
- polymarket_kalshi_spread
- polymarket_fill_risk
- polymarket_edge_tracker
- kalshi_weather_edge
- resolution_audit
- resolution_diff
- release_calendar_markets
- pipeworx_trending
- suggest_questions
- generate_llms_txt
- ai_visibility_check
- scan_competitor_ai_presence
- pipeworx_feedback
- remember
- recall
- forget
- sd_statute
- sd_search
This list was read from the server itself, by connecting to it and calling tools/list on 8 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.