v4.11.3

What's Changed

• chore: add MIT LICENSE file by @kingassune in #50
• docs(mcp-server): show the server is implemented here; add source Dockerfile by @kingassune in #51
• chore: add glama.json so the Glama listing can be claimed by @kingassune in #52
• feat: ship GDEX as a Claude Code plugin marketplace and Gemini CLI extension by @kingassune in #53
• docs: point npm badge at the published package; exact EVM chain count by @kingassune in #54
• feat: publish the SDK to npm as @gemachdao/gdex-skill by @kingassune in #55

Full Changelog: v4.11.2...v4.11.3

v4.11.2

What's Changed

• ci(mcp-registry): wait for npm before registry publish; separate OIDC workflow by @kingassune in #48
• fix(mcp-server): report the installed package version in serverInfo by @kingassune in #49

Full Changelog: v4.11.1...v4.11.2

v4.11.1

What's Changed

• feat(mcp-server): list GDEX MCP server in the official MCP Registry by @kingassune in #47

Full Changelog: v4.11.0...v4.11.1

v4.11.0 — anomaly events in the contract column shape

Changed

• gdex-hl-anomaly events now carry the 15-column anomaly contract shape. The model, thresholds and
  backtest results are unchanged (model_version stays gemach-hl-anomaly/robust-baseline-v2).
  • Added: anomaly_id (stable), entity_type (market), chain (hyperliquid),
    detection_method (statistical), baseline_window (7d), observed_metric, observed_value,
    expected_value, summary and detected_at_utc.
  • Breaking: detected_at is now epoch seconds (was an ISO string; the ISO form moves to
    detected_at_utc). score (0–1) is replaced by anomaly_score (0–100), the same mapping ×100.
  • confidence is deliberately not emitted. The score is a ranking, not a calibrated probability.
  • Vendored script affected: skills/gdex-hl-anomaly/scripts/hl_anomaly.py. The other vendored
    scripts are unchanged.

---

What's Changed

• gdex-hl-anomaly: anomaly contract columns; release 4.11.0 by @kingassune in #46

Full Changelog: v4.10.0...v4.11.0

v4.10.0 — risk & market data skills, anomaly events, harness

Released from main. 4.8.0 and 4.9.0 were cut from a side branch that never merged into
main, so their changes (wallet-forensics reverseEngineerWinners, the close_perp_position
short fix, bounded trade history, the coins filter on get_hl_meta_and_asset_ctxs) are not in
this release. Package versions were also out of step (4.5.0 / 4.6.0 / 4.7.0 across the SDK, MCP
server and lockfiles); all are 4.10.0 now.

Added

• Risk & market data skills (#42). Each is a standard-library Python script that prints NDJSON: no API
  key, and every figure is read by the script, never produced by a model.
  • gdex-hl-market-risk: funding, open interest, oracle premium and leverage caps for ~234
    HyperLiquid core perps.
  • gdex-token-risk: a token screen on 12 chains; missing security data is emitted as null,
    never as "safe".
  • gvault: GVault NAV, share price, holdings and returns, from Enzyme's accounting.
• gdex-hl-anomaly (#44). Scored, time-stamped HyperLiquid anomaly events: oracle_divergence,
  funding_extremity (always emitted with the premium) and liquidity_shock, each measured against
  per-market learned baselines. Every run ends with a coverage record (detector_window_start /
  _end, the markets scored and not scored). It ships with APPROACH.md, a backtest over three real
  events, a calibration script, offline tests and a sample payload.
• harness/ (#42): runs the skills with Claude on the caller's own Anthropic API key. export runs
  with no model and fails closed; ask can only quote script output. Every script run is audited
  with a sha256 of its output.
• Robinhood Chain (4663) across the SDK and skills (#41).
• gdex-xstocks skill. Documents getXstocks(), the tokenised-equities listing. The method
  shipped with no skill, no tests and no typed response.
• gdex-content-coins skill. Documents getZoraTokens(), the Zora content-coin and
  creator-coin listing on Base. Same gap as above.
• Chain warning in the README. The ChainId enum defines Avalanche, Polygon, zkSync Era,
  Linea, Blast and Scroll, none of which are in the backend's supportedChainIds. Calls against
  those ids do not route.

Changed

• MCP tool count corrected from 116 to 117 (109 execution + 8 documentation) in the README,
  ARTICLE, and gdex-onboarding. Counted from mcp-server/src/tools/*.ts plus the eight
  documentation tools registered in mcp-server/src/index.ts.
• skill.json chain claim corrected from "12+ EVM chains" to "9 EVM chains" — the count that
  the backend actually supports and that the README table has always listed.

Fixed

• MCP server bundle rebuilt (#43). The committed mcp-server/dist/index.js was plain tsc output
  that failed at start with ERR_MODULE_NOT_FOUND; it is the esbuild bundle again (117 tools).
• README: lists every skill and all 109 MCP execution tools; drops the removed root router
  skill; core HyperLiquid leverage is 40x (50x is only on builder-DEX FX pairs).

---

What's Changed

• docs: brand README as GDEX Pro + agent growth blurb by @kingassune in #33
• docs: refresh ARTICLE.md stats and GDEX Pro branding by @kingassune in #34
• docs: clarify ARTICLE MCP 108+8 (+ README 103 test count) by @kingassune in #35
• docs: fix leftover 91 to 103 test count in README by @kingassune in #38
• Add xStocks and content-coin skills, correct tool and chain counts by @kingassune in #39
• Add Robinhood Chain (4663) to SDK + skills by @kingassune in #41
• Restore the bundled MCP server; the committed one has crashed since June by @kingassune in #43
• Add risk-data skills with deterministic scripts, and a bring-your-own-key harness by @kingassune in #42
• feat(skills): gdex-hl-anomaly — HyperLiquid anomaly events with learned baselines by @kingassune in #44
• Release 4.10.0 by @kingassune in #45

Full Changelog: v4.7.0...v4.10.0

v4.9.0 — MCP agent-ergonomics

An agent-ergonomics pass on the MCP read/management surface, from a red-team of how an agent perceives and acts through these tools.

Fixed

• close_perp_position could not close short positions. It hardcoded isLong: false (with a false "reduce-only determines direction" comment), so closing a short submitted a sell that could not reduce it — the primary risk-management tool silently failed for half of all positions. Direction and size are now resolved from the live position (a short closes with a buy).

Added

• get_hl_trade_history limit (default 20, most recent first) — the tool returned the entire lifetime fill history (~90KB in practice) and overflowed an agent's context.
• get_hl_meta_and_asset_ctxs coins filter — return only the requested assets instead of all ~231.

Changed

• Tool results serialize compact (no 2-space indent tax).
• Failures set isError: true with a structured { error } payload so a caller can branch on success/failure; the stack is logged server-side, not shipped into the agent's context.

Impact

trade_history on a real account: ~19k tokens unbounded → ~1.9k at limit=20 (~17k tokens/call saved).

Tests

107 mcp-server tests passing.

Full changelog: CHANGELOG.md.

v4.7.0 — Managed-custody EVM swaps

Agents can now swap on EVM chains through managed custody.

What's new

• buyToken + MCP buy_token execute managed-custody EVM swaps. Previously the plain-param path was rejected by the backend (missing params, code 101) on Ethereum/Base/Arbitrum. buyToken now routes EVM trades carrying a sessionPrivateKey + apiKey through the session-signed purchase_v2 flow — the proven managed path.
• The MCP buy_token tool forwards sessionPrivateKey + apiKey so agents can swap over MCP.

Notes

• Additive change — Solana / non-managed callers are unchanged.
• amount is the decimal native token to spend (e.g. "0.05" ETH); the spend is the chain's native asset.
• Verified live on Arbitrum: returns {requestId, status:"pending"} where the old path returned missing params.

v4.6.0 — Builder-dex position reads

Builder/HIP-3 dex-scoped clearinghouse reads

Builder/HIP-3 perps (xyz:NVDA, xyz:SPCX, stocks, commodities) fill and trade through the standard hlCreateOrder flow and honor the leverage passed (3× isolated, live-confirmed). But their positions live under their own dex's isolated account, not the default clearinghouse — so reads that only hit the default dex showed them empty, which read as "the order never filled."

Changed

• SDK getHlClearinghouseState now accepts { userAddress, dex } to read a builder dex (e.g. dex: "xyz"), not just a plain address.
• MCP get_hl_clearinghouse_state tool gains an optional dex param so the MCP path can see builder positions.
• Docs (gdex-perp-trading skill): builder stock/commodity perps on xyz are USDC-collateralized and 24h (no collateral swap); reads are dex-scoped; getHlClearinghouseStateAll is stale and omits xyz.

Verified: MCP connects with 117 tools, get_hl_clearinghouse_state advertises dex, open_perp_position advertises leverage.

v4.5.0

What's Changed

• feat: 24h volume for outcome markets via HL WS (v4.5.0) by @kingassune in #24

Full Changelog: v4.4.0...v4.5.0

v4.4.0

What's Changed

• docs(sdk-debugging): note backend-limited deposit 400 + outcome-market listings by @kingassune in #21
• feat: official Gemach branding (theming tokens, lion logo, agent demo) by @kingassune in #22
• chore: release 4.4.0 (Gemach branding) by @kingassune in #23

Full Changelog: v4.3.1...v4.4.0