WICK FUNDED Trading

Overview

WICK FUNDED provides a first-party streamable HTTP MCP endpoint for simulated funded trading accounts at https://wickfunded.com/api/mcp. The upstream docs describe two connection paths: one-click OAuth for clients such as Claude Desktop, claude.ai, ChatGPT, and compatible connector clients, and a Bearer API-key header path for Claude Code CLI, Cursor, scripts, or raw HTTP clients.

Prerequisites

• A WICK FUNDED account with access to a simulated trading account/challenge.
• For OAuth: an MCP-compatible client that can add a custom connector and complete OAuth authorization. The docs say to leave OAuth Client ID and Secret blank because dynamic registration is automatic.
• For API-key/CLI use: a WICK API key generated from Dashboard -> Developer/API keys. Keys are shown once and use scopes read and/or execute.
• Users must comply with WICK trading rules, personal automation limits, jurisdiction restrictions, and KYC/payout requirements documented in the Terms and Rules pages.

Connection

OAuth connector flow:

1. Open the AI client's connector settings, for example Claude Settings -> Connectors -> Add custom connector.
2. Paste https://wickfunded.com/api/mcp and leave Client ID/Secret blank.
3. Connect, log in to WICK, and approve read or read + execute.

API-key CLI flow:

claude mcp add wick --transport http https://wickfunded.com/api/mcp \
  --header "Authorization: Bearer wk_live_xxxxxxxxxxxx"

MCP config file form:

{ "mcpServers": { "wick": {
  "url": "https://wickfunded.com/api/mcp",
  "headers": { "Authorization": "Bearer wk_live_xxxxxxxxxxxx" }
} } }

Configuration

Remote endpoint: https://wickfunded.com/api/mcp using streamable HTTP. No query parameters are documented or required.

OAuth configuration is discovered from /.well-known/oauth-protected-resource and /.well-known/oauth-authorization-server: issuer https://wickfunded.com, authorization endpoint https://wickfunded.com/oauth/authorize, token endpoint https://wickfunded.com/api/oauth/token, dynamic registration endpoint https://wickfunded.com/api/oauth/register, scopes read and execute, PKCE S256, and token endpoint auth method none.

Bearer API-key configuration uses an optional Authorization header with the documented form Bearer wk_live_xxxxxxxxxxxx. Secret token values are user-specific and are intentionally blank in this metadata. No package transport, local command, package arguments, or remote query parameters are documented for this server.

Authentication

Live OAuth protected-resource metadata advertises resource https://wickfunded.com/api/mcp, authorization server https://wickfunded.com, scopes read and execute, bearer method header, and documentation https://wickfunded.com/api. The OAuth authorization-server metadata advertises issuer https://wickfunded.com, authorization endpoint /oauth/authorize, token endpoint /api/oauth/token, dynamic registration endpoint /api/oauth/register, authorization-code and refresh-token grants, PKCE S256, and token endpoint auth method none.

The Bearer API-key path uses Authorization: Bearer <wk_live token> against the same MCP endpoint and REST API. Secret/user-specific token values are not included in this registry metadata.

Capabilities

Read tools documented by WICK: wick_account, wick_positions, wick_pending, wick_journal, wick_consistency, wick_symbols, and wick_candles. These map to account state, open positions, pending orders, journal/history, consistency-rule status, tradable symbols, and OHLC candles.

Execute tools documented by WICK: wick_trade_open, wick_trade_close, wick_trade_pending, wick_trade_cancel, and wick_trade_modify. The REST OpenAPI spec also documents read endpoints for account, positions, pending orders, journal, symbols, and candles, and execute endpoints for opening, closing, placing pending, canceling, and modifying trades. Execute calls require execute scope.

Limitations and Operational Requirements

WICK states all trading is simulated; it is not a brokerage or investment service and no real client funds are traded. Granting execute allows the connected AI/client to open, close, modify, place, and cancel trades on the user's simulated account. Execute calls are audit logged. Developer API rate limits are documented as default 100 requests/minute and 10,000 requests/hour, configurable per key.

The Terms and Rules permit personal automation for a user's own account but forbid sharing API keys, trading other users' accounts through one key, group signal mirroring/copy trading across accounts the user does not own, selling/renting/syndicating access, latency arbitrage, burst order/cancel cycles over 50/min, pure-HFT behavior, account sharing/sale, hedging across accounts, exploiting simulator bugs, and restricted-jurisdiction access. Trading rules include drawdown, consistency, news blackout, Friday close, hold-time, lot-size, payout/KYC, and breach policies that vary by account track.