nansen-mcp-dxt

One-click install of the Nansen MCP server for Claude Desktop: download nansen.dxt and open it. Setup guide: docs.nansen.ai/mcp/connecting.

What is generated

The connection settings (endpoint, NANSEN-API-KEY header, API-key URL, exact mcp-remote version) are not maintained here. The one maintained source is src/mcp-client-config.json in nansen-cli (API-322).

File	Maintained by hand?	Source
config/mcp-client-config.json	No	Byte-identical copy of the nansen-cli file at the commit in config/upstream.json
config/upstream.json	No	Written by npm run sync (commit SHA + sha256)
manifest.base.json	Yes	Extension metadata: name, description, version, icon
bundle/manifest.json	No	manifest.base.json + the config (npm run generate)
bundle/package.json, bundle/package-lock.json	No	Exact mcp-remote pin from the config (npm run build)
nansen.dxt	No	Packed from bundle/ with @anthropic-ai/mcpb (npm run build)

Do not edit generated files by hand. CI (.github/workflows/check.yml) fails when:

• a generated file drifts from the config;
• the config copy does not match its checksum, or the upstream file at the pinned commit;
• the pinned commit is not on nansen-cli main (merge nansen-cli first);
• any file in nansen.dxt differs from what npm ci installs from bundle/package-lock.json.

The manifest sets compatibility.runtimes.node from the strictest Node engine in the lock (today >=20.18.1, from undici).

How to update

Node.js 20.18.1 or later and unzip are required (macOS or Linux; the scripts do not support Windows).

npm ci
npm run sync -- --ref <nansen-cli commit SHA>   # after the config changes in nansen-cli: re-vendor, regenerate, rebuild nansen.dxt
npm run build                                   # after you edit manifest.base.json (bump its "version")
npm run check                                   # offline drift check

When the bundle changes, bump "version" in manifest.base.json and run npm run build again. npm run build keeps the committed nansen.dxt when its contents are already current (zip timestamps would otherwise change it on every build), so commit nansen.dxt only when it changed. nansen-cli runs a weekly check that opens an issue when this repo pins an older config.

The mcp-remote pin is owned by nansen-cli; see its AGENTS.md > MCP client config for the review and bump process.