Nymra Privacy Scan

Ask your AI assistant how traceable a wallet is. Give it any EVM wallet or ENS name and the Nymra Privacy Score comes back: a number from 0 (exposed) to 100 (private), every finding that costs points with the evidence behind it, the wallets it is likely linked to, and a fix plan with what you can change today. The scan runs on your own computer with the open privacy-scan engine, the same engine behind nymra.si.

The scan runs on your computer and Nymra receives nothing. What you type in the chat, the wallet included, reaches your AI provider like any other message.

It is a local MCP server, so it works in any app that runs one on your computer: as a plugin in Claude Code, and as an MCP server in Cursor, VS Code and OpenAI's Codex CLI.

What it adds

In every app:

• scan_wallet: the Privacy Score of a wallet, every finding with its evidence (transactions and addresses, with explorer links), the linked wallets with their confidence, and which chains were read.

• fix_plan: what the owner can undo today and how many points that wins back, what to do differently from now on, and what is on chain for good, with who can see each leak and the steps to take. In Claude Code, the plugin also brings:

• The wallet-privacy skill: tells Claude when to use the two tools and how to word a result, so a link between wallets always stays a likelihood with a confidence.

• The /nymra-privacy-scan:scan command: /nymra-privacy-scan:scan vitalik.eth scans a wallet and gives its fix plan in one go.

Both tools only read. They never ask for a seed phrase, a private key, a signature or a login, and they refuse one that is pasted in.

Related MCP server: ton-jetton-risk-mcp

Use it

Ask in your own words:

• "How private is vitalik.eth?"

• "What links 0x... to an exchange?"

• "Give me the fix plan for my wallet 0x..."

A scan takes about 20 seconds to 2 minutes, depending on how many chains the wallet used.

Where it works

The scan is a local MCP server, a small program your app starts on your computer over stdio. It runs in:

• Claude Code (the terminal, the IDE extensions and the Code tab of the desktop app) and Cowork when the session runs on your computer, as a plugin;

• Cursor, VS Code and OpenAI's Codex CLI, as an MCP server.

A chat in a browser or a mobile app (claude.ai, ChatGPT, Grok) starts no program on your computer, so the scan does not run there.

It needs Node.js 22.18 or newer on your computer (node --version). There is nothing else to install: it ships its own code and has no dependencies.

Install

Claude Code

/plugin marketplace add nymrasi/plugin
/plugin install nymra-privacy-scan@nymra

Claude Code then asks for the optional keys below; leave them empty to start.

Other apps

Get the code once, anywhere on your computer:

git clone https://github.com/nymrasi/plugin ~/nymra-plugin

The server is then node ~/nymra-plugin/server/main.ts (write out the full path where an app does not expand ~). Add it to your app:

• Cursor: in ~/.cursor/mcp.json (Cursor's MCP docs):

  {
    "mcpServers": {
      "nymra-privacy-scan": {
        "command": "node",
        "args": ["/Users/you/nymra-plugin/server/main.ts"]
      }
    }
  }

• VS Code: run MCP: Add Server from the Command Palette, choose Command (stdio) and enter node /Users/you/nymra-plugin/server/main.ts (VS Code's MCP docs).

• Codex CLI (Codex's MCP docs):

  codex mcp add nymra-privacy-scan -- node ~/nymra-plugin/server/main.ts

To update, run git pull in that folder and restart the app.

Your own keys (optional)

Most chains are read without a key. A few explorers answer a browser only, and one chain has no source without a key, so a wallet active there gets no score until those chains are read. A key of your own reads them, and the scan tells you which one it needs:

Each provider gives a key on its starter plan when you sign up. Put the key in one of two places, both on your own computer:

• The plugin's settings (Claude Code, recommended): run /plugin configure nymra-privacy-scan@nymra, or answer the questions Claude Code asks when you install the plugin. Claude Code keeps the keys in your system's secure credential store. Then run /reload-plugins.

• Your own environment (every app): set NYMRA_ALCHEMY_API_KEY, NYMRA_BLOCKSCOUT_API_KEY, NYMRA_NODEREAL_API_KEY or NYMRA_ETHERSCAN_API_KEY in your shell profile, or in the server's env in your app's MCP config (Codex: codex mcp add nymra-privacy-scan --env NYMRA_ALCHEMY_API_KEY=... -- node ...), and restart the app. In Claude Code a key in the plugin's settings wins.

Then scan again. Never paste a key into the chat: everything typed there reaches your AI provider. If one is pasted in, the plugin refuses it and does not repeat it; make a new key at the provider and delete that one.

A key never appears in an answer, a log or an error, the scan sends it only to its own provider, and no key ships with the plugin.

Privacy and data

• What runs: node server/main.ts from this repository, started by your app over stdio. Everything it runs is in this repository as readable source: server/ is the plugin, vendor/ the engine and the parts of Nymra's bot that run it outside a browser (see vendor/SOURCE.json for the exact commits).

• What it sends, and where: the wallet address, to public block explorers and nodes, the same requests your browser makes when you open the wallet on an explorer. These are the hosts it can reach:

  • Explorers: eth.blockscout.com, base.blockscout.com, arbitrum.blockscout.com, explorer.optimism.io, polygon.blockscout.com, robinhoodchain.blockscout.com, zksync.blockscout.com, scrollscan.com, unichain.blockscout.com, gnosisscan.io, explorer.inkonchain.com, soneium.blockscout.com, celo.blockscout.com, api.routescan.io

  • Nodes: ethereum-rpc.publicnode.com, eth.drpc.org, base-rpc.publicnode.com, arbitrum-one-rpc.publicnode.com, optimism-rpc.publicnode.com, polygon-bor-rpc.publicnode.com, rpc.mainnet.chain.robinhood.com, avalanche-c-chain-rpc.publicnode.com, mainnet.era.zksync.io, scroll-rpc.publicnode.com, unichain-rpc.publicnode.com, gnosis-rpc.publicnode.com, rpc-gel.inkonchain.com, soneium-rpc.publicnode.com, bsc-rpc.publicnode.com, celo-rpc.publicnode.com

  • ENS names: bens.services.blockscout.com

  • Only with a key of your own: base-mainnet.g.alchemy.com, polygon-mainnet.g.alchemy.com, api.blockscout.com, bsc-mainnet.nodereal.io, api.etherscan.io

• What Nymra receives: nothing. The plugin never contacts a Nymra server, sends no telemetry and writes no log line and no file. The exchange and service label lists ship with the engine, so a label lookup stays on your computer.

• What stays in memory: the last results, for ten minutes, so a fix plan right after a scan needs no second scan. They are gone when your app stops the scan.

• What your AI provider sees: what you type and what the tools answer is part of your conversation with the assistant, and reaches its provider (Anthropic, OpenAI or another) like any other message. Your app may also keep your conversations on your computer, as it does with every chat.

How the score works

Every wallet starts at 100. Each finding costs points by its severity and the engine's confidence, each kind of finding has a cap, and a wallet with a public label scores 34 or less. The rules, their thresholds and the formula are open: see RULES.md and nymra.si/docs.

A link between wallets is always a likelihood with a confidence (Likely, Possible or Weak). The scan never says who owns a wallet.

Limits

• EVM chains only: an address that is not 0x with 40 hex characters is refused.

• A chain that could not be read counts as not read, never as a chain without activity. A wallet with such a gap gets no score until it is read, and the answer says which chains are missing.

• On a long history the newest transactions and the oldest ones are read, and what lies between is not.

• Public data only. Whoever holds private records, such as an exchange that knows its customers, can link more than this scan shows.

Develop

npm test                      # node --test, no network
node scripts/mutate.mjs       # breaks one rule at a time; every mutant must be caught
node scripts/ask.mjs scan_wallet vitalik.eth   # ask the server the way an MCP app does
node scripts/sync.mjs         # take the bot repo's latest scanner and engine

License

MIT, see LICENSE. The engine is MIT too, and vendor/noble-hashes/ is @noble/hashes 2.4.0, MIT.