Verify your API key and check your Segnals identity. Returns your username, account tier, and connection status. Use this as the FIRST call to confirm the API key is working. Requires: any valid API key. Example: segnals_whoami()

List all available Segnals MCP tools and their required scopes. Use this to understand what actions you can perform with the current API key. Requires: any valid API key. Example: segnals_get_capabilities()

Returns the Segnals risk and safety disclaimer. This explains that Segnals is a software tool (not financial advice), outlines trading risks, and clarifies what the MCP server can and cannot do. Present this to users before creating strategies or starting bots. Requires: any valid API key. Example: segnals_get_safety_disclaimer()

Get your Segnals account details: tier, subscription status, bot limits, and usage. Use this to check account standing or before creating bots. Requires scope: read:account. Example: segnals_get_account()

Get your current subscription plan, billing status, and payment history. Use this to check if the user's subscription is active, when it renews, or what plan they're on. Requires scope: read:account. Example: segnals_get_subscription()

Check which exchanges and services are connected to the user's account. Returns boolean flags only (true/false for each exchange) — never returns credentials or secrets. Use this to verify exchange connectivity before creating bots. Requires scope: read:account. Example: segnals_list_connections()

Get the trading dashboard overview: total PnL, win rate, active bots count, equity curve, and summary stats. Use this for a high-level view of trading performance. Requires scope: read:stats. Example: segnals_get_dashboard()

Get aggregated PnL (profit and loss) breakdown from the dashboard data. Use this to analyze profitability over time. Requires scope: read:stats. Example: segnals_get_pnl_summary()

Get detailed performance metrics for a specific bot: net PnL, win rate, total trades, drawdown, and more. Use this to analyze how well a particular bot is performing. Requires scope: read:stats. Example: segnals_get_bot_performance({ bot_id: 42 })

Get recent trade history across all bots, with optional filtering by bot ID, symbol, or date range. Use this to review individual trades. Requires scope: read:stats. Example: segnals_get_trades({ limit: 20 })

List all trading bots on the user's account with their ID, name, exchange, status, and symbol. Use this to get an overview of all configured bots. Requires scope: read:bots. Example: segnals_list_bots()

Get the full configuration and status of a specific bot by its ID. Returns the bot's name, exchange, symbol, status, and complete config object. Use this to inspect a bot's settings in detail. Requires scope: read:bots. Example: segnals_get_bot({ bot_id: 42 })

Get execution logs for a specific bot. Shows recent trading activity, errors, and system events including cold-start status. Use this to debug bot behavior or check recent activity. Requires scope: read:bots. Example: segnals_get_bot_logs({ bot_id: 42 })

Get the configuration schema for a bot, showing all available settings, their types, defaults, and valid ranges. Use this to understand what parameters can be configured before creating or updating a bot. Requires scope: read:bots. Example: segnals_get_strategy_schema({ bot_id: 42 })

Analyze and explain a bot's current configuration. Describes what each setting does, flags risky combinations (e.g., Martingale with high multiplier), and suggests improvements. Use this to understand or review a bot's strategy setup. Requires scope: read:bots. Example: segnals_explain_config({ bot_id: 42 })

Browse the Segnals strategy marketplace. Returns available strategy listings with performance data (clearly labeled as live or backtest). Results are neutrally sorted. Use this to discover strategies the user can copy. Requires scope: read:marketplace. Example: segnals_browse_marketplace({ page: 1 })

Get details for a specific marketplace listing, including the strategy configuration preview and performance report. Use this to evaluate a strategy before copying it. Requires scope: read:marketplace. Example: segnals_get_listing({ listing_id: "abc123" })

View your own marketplace listings and sales data (VIP sellers). Shows your published strategies, sale counts, and earnings. Use this to manage your marketplace presence. Requires scope: read:marketplace. Example: segnals_my_listings()

Get the latest market news and events from the Segnals newsfeed. Use this to stay informed about market-moving events that may affect trading strategies. Requires scope: read:news. Example: segnals_get_news()

Get market sentiment data for a specific coin or trading symbol. Shows bullish/bearish sentiment indicators. NOTE: This tool is coming soon — the endpoint is not yet available. Requires scope: read:news. Example: segnals_get_sentiment({ symbol: "BTCUSDT" })

Get the current live price for a trading symbol. NOTE: This tool is coming soon — the endpoint is not yet available. Requires scope: read:news. Example: segnals_get_market_price({ symbol: "BTCUSDT" })

Search the Segnals knowledge base for help articles, feature documentation, and trading guides. Uses semantic search to find relevant content. NOTE: This tool is coming soon — the endpoint is not yet available. Requires scope: read:knowledge. Example: segnals_search_knowledge({ query: "how to set up trailing stop" })

Get your copy trading configuration and status. Shows which exchanges have copy trading enabled, the current settings, and operational status. Copy trading is a VIP feature. Requires scope: read:account. Example: segnals_get_copy_trading()

Start or stop copy trading for an exchange. Requires scope: control:bots. VIP tier required.

TWO-STEP CONFIRMATION: Call without confirm to preview. Call with confirm: true to execute. Copy trading mirrors trades from source accounts to destination accounts on the same exchange.

Get your notification preferences: daily reports, performance alerts, weekly summaries, and system reminders. Use this to review current notification settings before updating them. Requires scope: manage:notifications. Example: segnals_get_notifications()

Update notification preferences. Requires scope: manage:notifications.

Non-destructive — no confirmation needed. Updates are deep-merged with existing preferences. Valid keys: system_reminders, daily_report, performance_alerts, weekly_summary, custom_alerts.

Create a new trading bot on Segnals. Requires scope: write:bots.

TWO-STEP CONFIRMATION: Call without confirm (or confirm: false) to preview. Call with confirm: true to execute. The new bot starts in 'stopped' state — it will NOT start trading automatically. IMPORTANT: Never ask for or accept exchange API keys/secrets — users enter those in the Segnals dashboard (Settings → Connections).

Update a bot's configuration. Requires scope: write:bots.

TWO-STEP CONFIRMATION: Call without confirm to preview changes and see risk warnings. Call with confirm: true to apply. IMPORTANT: Never include exchange API keys/secrets in the config — users enter those in the dashboard.

Start a trading bot. Requires scope: control:bots.

TWO-STEP CONFIRMATION: Call without confirm to preview. Call with confirm: true to start. COLD-START NOTE: Starting a bot takes a few minutes. The status will show 'starting' → 'warming_up' → 'running'. This is normal behavior. IMPORTANT: The bot must have exchange credentials configured in the dashboard before starting.

Stop a running trading bot. Requires scope: control:bots.

This is a safe action — no confirmation required. The bot will stop trading but its configuration is preserved.

Restart a trading bot. Requires scope: control:bots.

TWO-STEP CONFIRMATION: Call without confirm to preview. Call with confirm: true to restart. NOTE: Restarting resets the bot's loss streaks and goes through the cold-start cycle.

Permanently delete a trading bot. Requires scope: write:bots.

TWO-STEP CONFIRMATION: Call without confirm to preview. Call with confirm: true to delete. WARNING: This action is PERMANENT and cannot be undone. The bot must be stopped first.

Create a fully configured trading strategy (bot + config). Requires scope: write:strategies.

TWO-STEP CONFIRMATION: Call without confirm to preview and validate. Call with confirm: true to create. This orchestrates: create bot → apply full config. The bot starts in 'stopped' state. IMPORTANT: Never include exchange API keys/secrets in the config.

Configure an indicator-based regime filter (ADX, RSI, EMA, ATR) on a bot. Requires scope: write:bots.

This is a non-destructive config update — no confirmation required. The filter is applied to the bot's config and takes effect on next trade evaluation.

Copy a strategy from the marketplace to your bots. Requires scope: write:marketplace.

TWO-STEP CONFIRMATION: Call without confirm to preview the listing and cost. Call with confirm: true to copy. FREE strategies: copied immediately. PAID strategies: initiates a crypto payment flow. The buyer risk disclaimer is required — the agent must present the disclaimer to the user before confirming.

Publish a bot as a marketplace listing. Requires scope: write:marketplace. VIP tier required.

TWO-STEP CONFIRMATION: Call without confirm to preview. Call with confirm: true to publish. The listing goes to 'pending_review' — an admin must approve it before it becomes active. Seller terms acceptance is required.