nansen-cli 1.41.0 → 1.42.0

package/CHANGELOG.md

@@ -1,5 +1,52 @@
 # Changelog
 
+## 1.42.0
+
+### Minor Changes
+
+- [#508](https://github.com/nansen-ai/nansen-cli/pull/508) [`3fc6e6b`](https://github.com/nansen-ai/nansen-cli/commit/3fc6e6b3083d3a8e0ab738c800bbcaf24dc00bef) Thanks [@gulshngill](https://github.com/gulshngill)! - Add `nansen mcp verify` to verify the hosted Nansen MCP setup with an authenticated data-path check.
+
+- [#487](https://github.com/nansen-ai/nansen-cli/pull/487) [`bb3f33e`](https://github.com/nansen-ai/nansen-cli/commit/bb3f33ea28642effbda911012dec8810adc8d40c) Thanks [@gulshngill](https://github.com/gulshngill)! - Add `nansen mcp install <client>` / `nansen mcp uninstall <client>` for one-step setup of the hosted Nansen MCP server (https://mcp.nansen.ai/ra/mcp) in Claude Code, Claude Desktop, and Cursor. Writes are merge-only and atomic (existing servers preserved, `.bak` backup on install and uninstall, refuses unparseable configs), use the API key from `nansen login` / `NANSEN_API_KEY`, never print the key, and support `--dry-run`.
+
+### Patch Changes
+
+- [#536](https://github.com/nansen-ai/nansen-cli/pull/536) [`f5e48df`](https://github.com/nansen-ai/nansen-cli/commit/f5e48dfddc9f063225847f54ed4b20334cadc6ae) Thanks [@kome12](https://github.com/kome12)! - `bridge quote` now prints a notice when a Hyperliquid USDC amount is floored to the 6-decimal precision the bridge signs, instead of adjusting the amount silently. The adjustment is unchanged (it's what keeps the persisted amount matching what gets signed); it's just no longer hidden.
+
+- [#533](https://github.com/nansen-ai/nansen-cli/pull/533) [`a96418d`](https://github.com/nansen-ai/nansen-cli/commit/a96418d4c7af5d8f8874f7ccb27d1d59ce797098) Thanks [@kome12](https://github.com/kome12)! - Bridge withdrawals now verify the Hyperliquid action's type, amount, network, and source token/routing fields against your request before signing, so a tampered quote cannot inflate a withdrawal, swap in a different token, or authorize on another account. The deposit action's EIP-712 primary type and exact ordered field list are now pinned too — not just the shared signing domain — so a quote can no longer pass every value check yet have the wallet sign a differently shaped Hyperliquid action (e.g. an agent approval) that the amount cap doesn't bound. The relayer authorization step is likewise pinned exactly to its real EIP-712 domain, field shape, and signing wallet, and its signature can only ever be submitted to the relayer's own fixed authorize endpoint — closing a gap where a malicious quote could have requested a signature over unrelated typed data and relayed it elsewhere. All of a withdrawal's steps are verified against this before any of them are signed or posted, so a bad step later in a multi-step quote (e.g. the real [authorize, sendAsset] order) can no longer let an earlier, valid-looking step reach the relayer or Hyperliquid first.
+
+  Also fixes a false rejection: Hyperliquid withdrawals whose `--amount` was given in base units (the default, no `--amount-unit`) and whose last two digits weren't zero were rejected at execute time as an amount mismatch, because the amount wasn't floored to the 6-decimal precision the bridge actually sends. Base-unit amounts are now floored the same way `--amount-unit` amounts already were, so these withdrawals execute.
+
+- [#530](https://github.com/nansen-ai/nansen-cli/pull/530) [`4312b50`](https://github.com/nansen-ai/nansen-cli/commit/4312b5004e0644f0bfcdac2e5e3eda7128958d92) Thanks [@kome12](https://github.com/kome12)! - Trade safety: tolerate a bounded native-token fee on cross-chain bridge swaps. The pre-signing swap-outcome check rejected any non-input token leaving the wallet, which could reject a legitimate bridge that pays its network fee in the native token on a token-input route. The tolerance is capped and applies only to the native token on bridges; every other token, and all same-chain swaps, stay strict.
+
+- [#537](https://github.com/nansen-ai/nansen-cli/pull/537) [`2d630d5`](https://github.com/nansen-ai/nansen-cli/commit/2d630d545161d656b41867d7b439e02c0786a01f) Thanks [@kome12](https://github.com/kome12)! - Fix `nansen mcp verify` routing after merging MCP install commands.
+
+- [#538](https://github.com/nansen-ai/nansen-cli/pull/538) [`853c48a`](https://github.com/nansen-ai/nansen-cli/commit/853c48ac1779e42507513c7c47a8f57bbffd540d) Thanks [@kome12](https://github.com/kome12)! - Harden the Hyperliquid bridge deposit leg: EVM approvals are now re-scoped to the requested amount (never unlimited) and the deposit target contract/method is pinned, so a tampered quote can't drain the wallet.
+
+- [#534](https://github.com/nansen-ai/nansen-cli/pull/534) [`e23af5c`](https://github.com/nansen-ai/nansen-cli/commit/e23af5cd111eb596dda9f3b6c88b32ffa3e5e756) Thanks [@gulshngill](https://github.com/gulshngill)! - Credential hygiene: `nansen login` verification failures cannot relay the API
+  key, invalid-key remediation points at key management, and login guidance leads
+  with paths that avoid shell history. Every request that carries a credential —
+  API key, agent, limit-order JWT/X-API-Key, MCP verify, and Privy auth — now
+  refuses to follow HTTP redirects, so a credential can't be relayed to a redirect
+  target. Interactive password and API-key prompts stay masked (no cleartext echo)
+  even when stdout is redirected.
+
+- [#529](https://github.com/nansen-ai/nansen-cli/pull/529) [`45b8584`](https://github.com/nansen-ai/nansen-cli/commit/45b8584ba8e2a3859612d8702dd78f117911cf87) Thanks [@gulshngill](https://github.com/gulshngill)! - Docs: stop pointing at the retired Cursor install deep link, pin the
+  `mcp-remote` bridge to the version `mcp install` writes, and correct the
+  header-formatting note (whitespace after the colon is trimmed; the key belongs
+  in `env`, not in the argument list).
+
+- [#531](https://github.com/nansen-ai/nansen-cli/pull/531) [`9bb44a7`](https://github.com/nansen-ai/nansen-cli/commit/9bb44a7339e80bba30d9ec2e499b5d3e306ceb66) Thanks [@crazywriter1](https://github.com/crazywriter1)! - Honor the original HTTP method on x402 paid retries so GET/DELETE/PATCH requests are not resent as POST after payment.
+
+## 1.41.1
+
+### Patch Changes
+
+- [#527](https://github.com/nansen-ai/nansen-cli/pull/527) [`02efb6d`](https://github.com/nansen-ai/nansen-cli/commit/02efb6d1f40453c03135eb68cf493486a5b6133a) Thanks [@kome12](https://github.com/kome12)! - Cross-chain (bridge) swaps now run swap-outcome verification instead of skipping it entirely. The output-arrival check is still skipped (the output settles on the destination chain), but the input-outflow cap and no-sibling-drain checks now run on the source-chain leg, closing a gap where a compromised quote's bridge instructions could move more than the declared input. Bridges also now enforce an intent-relative lower bound on the source-chain input outflow (an exactIn bridge must spend ~the requested input, so a large fee-only or partial no-op no longer verifies) and still validate the quote's output-amount integrity, and the native-SOL bridge log no longer contradicts itself about whether the output check ran. Note the lower bound relaxes by a native-SOL fee/rent allowance (~0.013 SOL), so on a small native-SOL leg at or below that allowance the floor effectively collapses to a bare "outflow > 0" — the tightest bound possible for a native leg whose fees are indistinguishable from the transfer. `--swap-mode` is now validated against `exactIn`/`exactOut` at the CLI, and both the swap-outcome verifier and the pre-signing request-intent completeness checks fail closed on an unrecognized mode in a persisted quote so a garbage value cannot bypass the exactIn input floor — even when outcome verification is skipped or degraded.
+
+  Because bridges now go through the simulation, a bridge quote that **reverts in simulation** returns `proceed: false` and is dropped (the signing loop falls through to the next quote); only a simulation that cannot run at all (`NO_SIM_RPC` / `SIM_RPC_ERROR` / `NOT_SIM_CAPABLE`) degrades to proceed-without-verification, matching same-chain swaps. This is a new, fail-closed outcome for bridges specifically.
+
+- [#513](https://github.com/nansen-ai/nansen-cli/pull/513) [`55eb953`](https://github.com/nansen-ai/nansen-cli/commit/55eb953cc15fe21aa441d1700e05ef053c643a58) Thanks [@kome12](https://github.com/kome12)! - Fix `trade execute` crashing on Solana-source bridge quotes from the Relay aggregator, which return raw uncompiled instructions instead of a ready-to-sign transaction. These are now compiled client-side before signing.
+
 ## 1.41.0
 
 ### Minor Changes

package/README.md

@@ -20,17 +20,27 @@ Three options — pick whichever fits your setup:
 
 1. **API key** (subscription):
    ```bash
-   nansen login --api-key <key>   # save key to ~/.nansen/config.json
-   nansen login --human           # interactive prompt
-   export NANSEN_API_KEY=...      # env var (highest priority)
-   nansen logout                  # remove saved key
+   nansen login --human   # interactive prompt; saves to ~/.nansen/config.json
+   nansen login           # uses NANSEN_API_KEY when already set
+   nansen logout          # remove saved key
    ```
+   For automation, inject `NANSEN_API_KEY` through your environment or secret manager.
    Get your API key at [app.nansen.ai/auth/agent-setup](https://app.nansen.ai/auth/agent-setup).
 
 2. **x402 micropayment** (no key needed): `nansen wallet create`, fund with USDC on Base or Solana, or USDT0 on X Layer, then call any endpoint — the CLI signs `Payment-Signature` headers automatically on 402 responses. See [Wallet](#wallet).
 
 3. **MPP via tempo** (no key needed): install the [tempo CLI](https://docs.tempo.xyz) separately, run `tempo wallet login` to set up, then call the Nansen API through `tempo request`. The Nansen API selects the MPP rail when it sees `Authorization: Payment ...`. See [MPP / Tempo](#mpp--tempo) below.
 
+## Verify your MCP setup
+
+For the hosted Nansen MCP server, verify server reachability and the supplied API key on the paid data path with:
+
+```bash
+npx -y nansen-cli mcp verify  # uses the saved key or NANSEN_API_KEY
+```
+
+The check calls `tools/list` for reachability, then calls the paid `nansen_score_top_tokens` canary tool. A successful canary costs about 1 credit; tool listings and free tools alone do not prove that a key works. The CLI cannot inspect the key inside your MCP client, so make sure this same key is in the client's `NANSEN-API-KEY` header. For the final client-config check, ask your client: “Use the `nansen_score_top_tokens` tool.”
+
 ## Commands
 
 ```
@@ -40,6 +50,7 @@ nansen agent "<question>" --expert    # deeper analysis (750 credits, Pro)
 nansen trade quote --chain solana --from SOL --to USDC --amount 1000000000
 nansen trade execute --quote <quoteId>
 nansen wallet <subcommand> [options]
+nansen mcp install <client>           # add the Nansen MCP server to Claude Code/Desktop or Cursor
 nansen schema [command] [--pretty]    # full command reference (no API key needed)
 ```
 
@@ -59,7 +70,19 @@ Connect any MCP client to Nansen's streamable HTTP server:
 - **Authentication:** `NANSEN-API-KEY` header
 - **API key:** [app.nansen.ai/auth/agent-setup](https://app.nansen.ai/auth/agent-setup)
 
-**Claude Desktop and Cursor:** setup instructions for both — the Claude Desktop `.dxt` bundle and the Cursor install deep link — are in the connection docs: [docs.nansen.ai/mcp/connecting](https://docs.nansen.ai/mcp/connecting).
+One-step install of the hosted [Nansen MCP server](https://docs.nansen.ai/mcp/overview) (`https://mcp.nansen.ai/ra/mcp`) into a local MCP client:
+
+```bash
+nansen mcp install claude-code       # ~/.claude.json (user scope)
+nansen mcp install claude-desktop    # macOS/Windows only; bridges via pinned mcp-remote
+nansen mcp install cursor            # ~/.cursor/mcp.json
+nansen mcp install cursor --dry-run  # print what would be written (key redacted)
+nansen mcp uninstall <client>        # remove the entry (add --dry-run to preview)
+```
+
+Uses the API key from `nansen login` / `NANSEN_API_KEY`; re-run `install` after rotating your key. Writes are merge-only and atomic: existing servers and settings are preserved, a `.bak` copy is written before every install or uninstall, and the CLI refuses to touch a config it can't parse. Note the client config stores the API key in plaintext — new files are created with `0600` permissions. Restart the client after installing.
+
+**Manual setup**, for other clients or if you would rather not use the CLI — the paths below, and the connection docs at [docs.nansen.ai/mcp/connecting](https://docs.nansen.ai/mcp/connecting).
 
 **One-command (Claude Code):**
 
@@ -82,7 +105,7 @@ claude mcp add --transport http nansen https://mcp.nansen.ai/ra/mcp --header "NA
 }
 ```
 
-**Manual (stdio-only clients):** use `mcp-remote` as a bridge. Keep the header as one argument with no space after the colon:
+**Manual (stdio-only clients):** use `mcp-remote` as a bridge. Keep the header name and value in a single `args` entry, and keep the key in `env` rather than in the argument list — `mcp-remote` substitutes `${NANSEN_API_KEY}` from the environment:
 
 ```json
 {
@@ -91,7 +114,7 @@ claude mcp add --transport http nansen https://mcp.nansen.ai/ra/mcp --header "NA
       "command": "npx",
       "args": [
         "-y",
-        "mcp-remote@latest",
+        "mcp-remote@0.2.1",
         "https://mcp.nansen.ai/ra/mcp",
         "--header",
         "NANSEN-API-KEY:${NANSEN_API_KEY}"
@@ -104,6 +127,8 @@ claude mcp add --transport http nansen https://mcp.nansen.ai/ra/mcp --header "NA
 }
 ```
 
+`mcp-remote` is pinned to an exact version rather than `@latest` because the bridge handles your API key on every request, and `npx` would otherwise pull a new release automatically. `0.2.1` is the current release and the version this config is tested against; bumping it is safe — review the release and update the pin.
+
 **Claude Tag (Claude in Slack):** an admin must attach a plugin whose `.mcp.json` points at `https://mcp.nansen.ai/ra/mcp` and add a custom credential allowing the host `mcp.nansen.ai`. See the [Claude Tag custom-connections documentation](https://claude.com/docs/claude-tag/admins/connections/custom). Per-user fallback: use Claude Code or Claude Desktop.
 
 ## Trading
@@ -294,6 +319,7 @@ Any field may be absent or `null`, meaning unknown — never assume zero. A low-
 | `command not found` | `npm install -g nansen-cli` |
 | Global install reports an older version | `npm i -g nansen-cli@latest --registry=https://registry.npmjs.org/ --prefer-online`, then check `which -a nansen` for stale binaries |
 | `UNAUTHORIZED` after login | `nansen auth status` shows which key is active and where it comes from; re-run `nansen login` or set `NANSEN_API_KEY` |
+| MCP client lists tools but paid calls fail | Run `npx -y nansen-cli mcp verify` with the saved key or `NANSEN_API_KEY`, and ensure that same key is in the client's `NANSEN-API-KEY` header |
 | Anything else misbehaving | `nansen doctor` checks your whole setup (auth, wallets, caches, connectivity) with a fix per finding |
 | Empty perp _research_ results | Use `--symbol BTC`, not `--token`. Perps are Hyperliquid-only. |
 | `perp` _trading_ prints the usage banner | Trading needs `--coin BTC` (`--symbol` also works); see the Perpetuals section. |

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "nansen-cli",
-  "version": "1.41.0",
+  "version": "1.42.0",
   "description": "AI-agent CLI for Nansen API analytics, DEX swaps, and cross-chain trading",
   "main": "src/index.js",
   "type": "module",

package/scripts/postinstall.js

@@ -132,7 +132,7 @@ async function installSkill() {
 async function testQuery() {
   if (!isLoggedIn()) {
     log();
-    log(`Not logged in yet. Run ${CYAN}nansen login --api-key <key>${RESET} to authenticate.`);
+    log(`Not logged in yet. Run ${CYAN}nansen login --human${RESET} to authenticate.`);
     log(`Get your API key at: ${CYAN}https://app.nansen.ai/auth/agent-setup${RESET}`);
     return;
   }
@@ -156,7 +156,7 @@ async function testQuery() {
     log(`${GREEN}✓${RESET} All set! Run ${CYAN}nansen help${RESET} to see all available commands.`);
   } else {
     log();
-    log(`${YELLOW}Query failed. Check your API key with: nansen login --api-key <key>${RESET}`);
+    log(`${YELLOW}Query failed. Check your API key with: nansen auth status${RESET}`);
   }
 }
 
@@ -172,7 +172,7 @@ async function main() {
     log(`${BOLD}Nansen CLI installed!${RESET}`);
     log();
     log(`Tip: Run '${CYAN}npx skills add ${SKILL_REPO}${RESET}' to install the Nansen AI coding skill.`);
-    log(`Tip: Run '${CYAN}nansen login --api-key <key>${RESET}' to authenticate.`);
+    log(`Tip: Run '${CYAN}nansen login --human${RESET}' to authenticate.`);
     log(`Tip: To trade, first create a wallet with '${CYAN}nansen wallet create${RESET}', then quote with '${CYAN}nansen trade quote --chain solana --from SOL --to USDC --amount 1000000000${RESET}' and execute with '${CYAN}nansen trade execute --quote <id>${RESET}'.`);
     return;
   }

package/skills/nansen-wallet-manager/SKILL.md

@@ -21,10 +21,10 @@ allowed-tools: Bash(nansen:*)
 ## Auth Setup
 
 ```bash
-# Save API key (non-interactive)
-nansen login --api-key <key>
-# Or via env var:
-NANSEN_API_KEY=<key> nansen login
+# Save API key interactively
+nansen login --human
+# Or use NANSEN_API_KEY after provisioning it through your environment/secret manager
+nansen login
 
 # Verify
 nansen research profiler labels --address 0xd8dA6BF26964aF9D7eEd9e03E53415D37aA96045 --chain ethereum
@@ -190,7 +190,7 @@ For detailed migration steps (from `~/.nansen/.env`, `.credentials`, or env-var-
 | Var | Purpose |
 |-----|---------|
 | `NANSEN_WALLET_PASSWORD` | Wallet encryption password — only needed for initial `wallet create`. After that, the OS keychain handles it. |
-| `NANSEN_API_KEY` | API key (also set via `nansen login --api-key <key>`) |
+| `NANSEN_API_KEY` | API key (can also be saved via `nansen login --human`) |
 | `PRIVY_APP_ID` | Privy application ID (required for `--provider privy`) |
 | `PRIVY_APP_SECRET` | Privy application secret (required for `--provider privy`) |
 | `NANSEN_WALLET_PROVIDER` | Default provider for wallet create — `local` or `privy` |

package/src/api.js

@@ -538,7 +538,7 @@ export class NansenAPI {
    * @param {string|null} network - x402 network string for balance check, e.g. "eip155:8453"
    * @param {string} url - Request URL
    * @param {object} body - Request body (will be cleaned)
-   * @param {object} [options={}] - Request options (may include .headers)
+   * @param {object} [options={}] - Request options (may include .method, .headers)
    * @returns {Promise<object|null>} Parsed JSON on success, null if rejected
    *
    * TODO: full fix — extract the entire x402 provider dispatch from request() into
@@ -546,10 +546,15 @@ export class NansenAPI {
    * touching that one method, not hunting inside the retry loop.
    */
   async _x402Retry(signature, walletLabel, network, url, body, options = {}, asset = null) {
+    // Mirror request(): paid retries must use the original method. Hardcoding
+    // POST burned a payment signature then hit the wrong route for GET/DELETE/PATCH.
+    const method = options.method || 'POST';
+    const isGet = method === 'GET';
     const paidResponse = await fetch(url, {
-      method: 'POST',
+      method,
+      redirect: 'error',
       headers: {
-        'Content-Type': 'application/json',
+        ...(!isGet && { 'Content-Type': 'application/json' }),
         'X-Client-Type': 'nansen-cli',
         'X-Client-Version': packageVersion,
         ...telemetryHeaders(),
@@ -557,7 +562,7 @@ export class NansenAPI {
         ...this.defaultHeaders,
         ...options.headers,
       },
-      body: JSON.stringify(NansenAPI.cleanBody(body)),
+      ...(!isGet && method !== 'DELETE' && { body: JSON.stringify(NansenAPI.cleanBody(body)) }),
     });
     if (!paidResponse.ok) return null;
     if (walletLabel) {
@@ -605,6 +610,7 @@ export class NansenAPI {
         const isGet = method === 'GET';
         response = await fetch(url, {
           method,
+          redirect: 'error',
           headers: {
             ...(!isGet && { 'Content-Type': 'application/json' }),
             'X-Client-Type': 'nansen-cli',
@@ -747,7 +753,7 @@ export class NansenAPI {
                   } catch (x402Err) {
                     if (!this.apiKey) {
                       message = 'No API key configured. Three ways to authenticate:\n' +
-                        '  1. API key: nansen login --api-key <key> (get key at https://app.nansen.ai/auth/agent-setup)\n' +
+                        '  1. API key: run `nansen login --human` or set NANSEN_API_KEY (get key at https://app.nansen.ai/auth/agent-setup)\n' +
                         '  2. x402 micropayment: nansen wallet create + fund with USDC on Base/Solana or USDT0 on X Layer (no API key needed)\n' +
                         '  3. MPP via tempo: install tempo CLI, run `tempo wallet login`, then call the API with `tempo request` (see skills/nansen-mpp-payment)';
                     } else {