@panoptic-eng/mcp 0.1.0 → 0.1.2

package/README.md

@@ -22,8 +22,8 @@ its MCP settings, etc.).
       "command": "npx",
       "args": ["-y", "@panoptic-eng/mcp"],
       "env": {
-        "PANOPTIC_RPC_URL": "https://mainnet.base.org",
-        "PANOPTIC_CHAIN_ID": "8453",
+        "PANOPTIC_RPC_URL": "https://eth-mainnet.g.alchemy.com/v2/<key>",
+        "PANOPTIC_CHAIN_ID": "1",
         // optional — enables enhanced analytics tools
         "PANOPTIC_SUBGRAPH_URL": ""
       }
@@ -35,15 +35,20 @@ its MCP settings, etc.).
 Configuration may also be passed as CLI flags, which override the env vars:
 
 ```bash
-npx @panoptic-eng/mcp --rpc-url https://mainnet.base.org --chain-id 8453
+npx @panoptic-eng/mcp --rpc-url https://eth-mainnet.g.alchemy.com/v2/<key> --chain-id 1
 ```
 
-Supported chains: Ethereum mainnet (`1`), Base (`8453`), Sepolia (`11155111`).
+Supported chains: Ethereum mainnet (`1`), Sepolia (`11155111`).
 
-## v0 tools (read-only, pure RPC)
+## v0 tools (read-only)
+
+All tools are read-only (they never build or send transactions). The one
+exception to statelessness is `configure_session`, which mutates in-process
+session preferences rather than reading the chain.
 
 | Tool | What it does |
 | --- | --- |
+| `configure_session` | **Local session state — not an RPC read.** Set/read this session's preferences — notably the preferred delta reporting frame (`assetIndex`) — so delta tools don't re-ask which token to denominate net delta in. State lives in the server process for the session only. |
 | `list_pools` | Known pool deployment + live pool state (tokens, tick, trackers, health). |
 | `explain_position` | Decode a TokenId into readable legs + a strategy label (no RPC). |
 | `identify_address` | Map an address to its role in a Panoptic deployment. |
@@ -57,6 +62,10 @@ Supported chains: Ethereum mainnet (`1`), Base (`8453`), Sepolia (`11155111`).
 | `position_scenario` | Payoff / NLV curve — net liquidation value across a band of hypothetical prices. |
 | `hedge_params` | SDK-native delta-hedge parameters (`getDeltaHedgeParams`) to reach a target delta; whole-portfolio or single-position. |
 | `trade_history` | Chronological mints/burns from on-chain events (event-level only — no realized P&L). |
+| `list_vaults` | Known HypoVault deployments: vaults, managers, accountant, underlying token, pool, trackers, and strategy labels. |
+| `vault_summary` | Live HypoVault state: supply, manager/accountant, fees, epochs, reserved withdrawal assets, and current epoch totals. |
+| `vault_account` | A user's HypoVault share balance, basis, queued deposit/withdrawal, redeposit flag, and executable epoch hints. |
+| `vault_exposure` | Treat a HypoVault as the Panoptic account and return positions, collateral, greeks, and margin health. |
 
 `get_portfolio`, `account_health`, `suggest_delta_hedge`, `advise_position`,
 `preview_position`, `position_scenario`, and `hedge_params` discover positions
@@ -65,6 +74,18 @@ Pass `fromBlock` to bound the scan on chains with a distant deployment block.
 These account tools need an RPC that permits `eth_getLogs`; many free public
 endpoints throttle or block large log scans, so a private RPC is recommended.
 
+An account's aggregate net delta is a single figure and must be denominated in
+one token's units (its "reporting frame"). There is no canonical pool asset —
+each position leg carries its own — so `suggest_delta_hedge` and `hedge_params`
+(portfolio mode) resolve the frame as: explicit `assetIndex` argument → session
+preference → **ask the user**. When neither is set they return a
+`needs_asset_preference` prompt rather than silently guessing; call
+`configure_session` with `assetIndex` to record the choice for the session.
+
+HypoVault NAV/share-price reads are intentionally not exposed in v0 because
+`totalAssets(bytes)` and `convertToAssets(uint256,bytes)` require
+managerInput-aware accounting; use `vault_summary` for raw vault state.
+
 Build + simulate tools (`build_position`, `build_strategy`, `simulate_tx`, …)
 that return unsigned transaction envelopes are planned for a future release and
 are **not** shipped yet. All numeric on-chain quantities are serialized as
@@ -79,7 +100,7 @@ pnpm --filter @panoptic-eng/mcp typecheck   # tsc --noEmit
 pnpm --filter @panoptic-eng/mcp lint
 
 # Inspect locally against a real RPC:
-PANOPTIC_RPC_URL=https://mainnet.base.org PANOPTIC_CHAIN_ID=8453 \
+PANOPTIC_RPC_URL=https://eth-mainnet.g.alchemy.com/v2/<key> PANOPTIC_CHAIN_ID=1 \
   npx @modelcontextprotocol/inspector node dist/cli.js
 ```
 

package/dist/cli.js

@@ -1,5 +1,5 @@
 #!/usr/bin/env node
-import { SERVER_VERSION, createContext, createServer, resolveConfig } from "./server--YF2LHqv.js";
+import { SERVER_VERSION, createContext, createServer, resolveConfig } from "./server-CabyB7Fb.js";
 import { StdioServerTransport } from "@modelcontextprotocol/sdk/server/stdio.js";
 
 //#region src/cli.ts

package/dist/index.d.ts

@@ -4,14 +4,10 @@ import { Address, Hex, PublicClient } from "viem";
 import { McpServer } from "@modelcontextprotocol/sdk/server/mcp.js";
 
 //#region src/config.d.ts
-/** Chain ids Panoptic has deployments for (mainnet, Base, Sepolia). */
-/** Chain ids Panoptic has deployments for (mainnet, Base, Sepolia). */
-declare const KNOWN_CHAIN_IDS: readonly [1, 8453, 11155111];
+declare const KNOWN_CHAIN_IDS: readonly [1, 11155111];
 /**
- * Resolve an optional user-supplied chain-id string to a trusted known-chain
- * constant, falling back to `fallback` when omitted/blank. Matches on canonical
- * decimal form only (never Number(), so "1e0" is rejected) and throws on
- * unsupported ids.
+ * Resolve an optional user-supplied chain-id string to a trusted, deployed
+ * known-chain constant, falling back to `fallback` when omitted/blank.
  */
 
 interface ServerConfig {
@@ -20,10 +16,25 @@ interface ServerConfig {
   /** Optional indexer URL; enables enhanced analytics tools. */
   subgraphUrl?: string;
 }
+/**
+ * Mutable per-process session state. The stdio server runs for the lifetime of
+ * one agent session, so tools can record user preferences here (via
+ * `configure_session`) and later tools read them back. Nothing here is
+ * persisted across restarts.
+ */
+interface SessionState {
+  /**
+   * The user's preferred delta reporting frame for this session (0n = token0,
+   * 1n = token1). When set, delta tools report net delta in this frame instead
+   * of asking. There is no canonical pool asset — this is a user choice.
+   */
+  preferredAssetIndex?: 0n | 1n;
+}
 interface PanopticContext {
   config: ServerConfig;
   client: PublicClient;
   deployment: ChainDeployment;
+  session: SessionState;
 }
 /**
  * Resolve server config from CLI flags (`--rpc-url`, `--chain-id`,
@@ -33,9 +44,7 @@ interface PanopticContext {
  */
 declare function resolveConfig(argv: string[], env: NodeJS.ProcessEnv): ServerConfig;
 /** Create the shared context (viem client + resolved deployment) for tools. */
-declare function createContext(config: ServerConfig): Promise<PanopticContext>;
-
-//#endregion
+declare function createContext(config: ServerConfig): Promise<PanopticContext>; //#endregion
 //#region src/serialize.d.ts
 /**
  * Recursively convert a value into a JSON-safe form. The only Panoptic-specific

package/dist/index.js

@@ -1,3 +1,3 @@
-import { KNOWN_CHAIN_IDS, SERVER_NAME, SERVER_VERSION, buildEnvelope, createContext, createServer, jsonResult, resolveConfig, toJsonSafe } from "./server--YF2LHqv.js";
+import { KNOWN_CHAIN_IDS, SERVER_NAME, SERVER_VERSION, buildEnvelope, createContext, createServer, jsonResult, resolveConfig, toJsonSafe } from "./server-CabyB7Fb.js";
 
 export { KNOWN_CHAIN_IDS, SERVER_NAME, SERVER_VERSION, buildEnvelope, createContext, createServer, jsonResult, resolveConfig, toJsonSafe };