@aetherwealth/mcp 0.1.34 → 0.1.35

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (3) hide show
  1. package/README.md +26 -3
  2. package/dist/index.js +60 -59
  3. package/package.json +1 -1
package/README.md CHANGED
@@ -48,9 +48,12 @@ Aether Wealth MCP gives AI assistants a safe tool layer over Aether Wealth:
48
48
  - Render chart images and drive an open browser chart
49
49
  - Compute technical indicators such as RSI, MACD, EMA, Bollinger Bands, ATR,
50
50
  ADX, Supertrend, and more
51
+ - Propose broker trade intents and execute only user-confirmed email/app/auto
52
+ intents; push-mode intents execute only after the user taps Approve in the app
51
53
 
52
- Aether Wealth is trading analysis and journaling software. This MCP server does
53
- not place broker orders or execute trades.
54
+ Aether Wealth broker execution is intent-based: the assistant can propose, but
55
+ the backend enforces the selected user confirmation channel before any order is
56
+ placed.
54
57
 
55
58
  ## Authentication
56
59
 
@@ -68,6 +71,8 @@ Operators can deploy this server as a shared remote MCP endpoint instead of a
68
71
  local process. Set `MCP_TRANSPORT=http`, `MCP_HTTP_AUTH=oauth`, and
69
72
  `MCP_PUBLIC_ORIGIN=https://<your-host>`. In this mode:
70
73
 
74
+ - The Aether-hosted endpoint is `https://mcp.aetherwealth.ai`; `/mcp` remains
75
+ available as a legacy connector alias.
71
76
  - Each request must carry the caller's own OAuth access token
72
77
  (`Authorization: Bearer ...`); MCP clients obtain it via the standard MCP
73
78
  auth flow, discovered from `/.well-known/oauth-protected-resource`.
@@ -151,6 +156,22 @@ local process. Set `MCP_TRANSPORT=http`, `MCP_HTTP_AUTH=oauth`, and
151
156
  | --- | --- |
152
157
  | `get_indicators` | Compute up to 8 technical indicators for a pair and interval. |
153
158
 
159
+ ### Broker Execution
160
+
161
+ | Tool | Purpose |
162
+ | --- | --- |
163
+ | `get_broker_account` | Read live broker account balance, equity, currency, and connection status. |
164
+ | `list_broker_positions` | List open broker positions with P&L. |
165
+ | `connect_broker` | Attach the user's already-deployed MetaApi account to a journal account. |
166
+ | `broker_connection_status` | Read the current live broker connection status. |
167
+ | `set_broker_approval_mode` | Switch confirmation between `app_otp`, `email_otp`, and `push`; `push` requires an active app push subscription. |
168
+ | `propose_trade` | Size and propose a trade intent. Push-mode proposals notify the user's device. |
169
+ | `execute_trade` | Execute email_otp/app_otp/auto intents after the required confirmation; push intents are blocked here. |
170
+ | `trade_intent_status` | Check whether a proposed intent was approved, executed, expired, cancelled, or failed. |
171
+ | `cancel_trade_intent` | Cancel a pending proposed broker trade. |
172
+ | `close_position` | Close an open broker position fully or partially. |
173
+ | `modify_position` | Adjust stop-loss or take-profit without increasing risk. |
174
+
154
175
  ### Charts
155
176
 
156
177
  | Tool | Purpose |
@@ -183,7 +204,9 @@ local process. Set `MCP_TRANSPORT=http`, `MCP_HTTP_AUTH=oauth`, and
183
204
  gates.
184
205
  - Trade deletion is limited to demo accounts. Live-account trades cannot be
185
206
  deleted through this MCP.
186
- - The MCP does not execute trades or route broker orders.
207
+ - Broker orders require backend-enforced confirmation. Push-mode intents cannot
208
+ be executed by the assistant; use `trade_intent_status` to observe the user's
209
+ app approval outcome.
187
210
 
188
211
  ## Updating
189
212