LABSCO SUMMARY

The credential handling is written into the tool descriptions, and it is more careful than most — read-only keys, the OS keychain, and a rule for what the model may repeat back.

setup_connector writes read-only credentials to the OS keychain and instructs the model to confirm only the account label and id afterwards rather than echoing what it was given. remove_account is described as one-way, deleting both the account and its keychain entry, with the settings UI requiring explicit confirmation before it is called. The read side separates cache from source on purpose: the holdings and transaction tools serve cached data, and refresh_data is the explicit invalidation for when balances look stale.

What it is

A portfolio tracker with 15 tools that read holdings, transactions, P&L and allocation across connected exchange accounts and on-chain wallets, manage those connections and their credentials, and render two live UI panels.

What you get

get_holdings returns current positions across all connected accounts, filterable by account, asset class and reporting currency.
get_pnl returns profit and loss per account and in total, reporting currentValue and costBasis where the connector tracks it, with a method, timeframe and optional history.
get_allocations groups current value by asset class, connector or another dimension, where cash covers stablecoins such as USDC and USDT plus fiat.
get_transactions returns trades, buys, sells, deposits, withdrawals, fees and ERC-20 transfers across accounts since a date you set.
get_polymarket_positions returns prediction-market positions grouped by event, with a resolved-only filter.
Connection management: list_accounts without exposing credentials, setup_connector, which writes read-only credentials into the OS keychain, add_wallet_address for an extra address on an existing MetaMask or Solana account, and remove_account, a one-way delete of both the account and its keychain entry.
Custom ERC-20 tracking on top of the bundled USDC, USDT, WETH, WBTC, LINK and DAI: add_custom_token by chain id and contract, remove_custom_token and list_custom_tokens, all of it public on-chain data.
refresh_data invalidates the cache and forces a fresh fetch from the upstream APIs on the next call.
render_dashboard and render_settings open live UI panels — a dashboard across Portfolio, Weekly and Risk tabs with a currency switch, and a settings panel as the GUI alternative to the CLI setup flow.

Requirements

Read-only credentials for whichever venues you connect, written into the OS keychain by setup_connector. Wallet addresses and custom token contracts are public on-chain identifiers and add no secrets.

Setup effort

One command — npm install -g headless-tracker

See installation options

USE CASES

01

Answering "what do I actually own" across venues in one call

Holdings come back across every connected account, and the allocation read regroups the same value by asset class or connector.

get_holdingsget_allocationslist_accounts

02

Working out whether you are up or down, and by which measure

P&L reports current value against cost basis where the connector tracks it, and the transaction history is where a number that looks wrong gets checked.

get_pnlget_transactionsget_holdings

03

Connecting a new exchange or wallet without leaking a key

Setup writes read-only credentials into the OS keychain and confirms only the account label back; removing an account clears the keychain entry with it.

setup_connectorlist_accountsadd_wallet_addressremove_account

04

Tracking a project token the defaults do not cover

The bundled list covers the common tokens; anything beyond it is added by chain id and contract, all of it public on-chain data.

add_custom_tokenlist_custom_tokensremove_custom_token

05

Checking prediction-market bets apart from everything else

Positions can be grouped by event and filtered to resolved ones, which is the view the general holdings read cannot give.

get_polymarket_positionsget_holdings

06

Getting a live panel instead of a wall of numbers

The dashboard has Portfolio, Weekly and Risk tabs with a currency switch, and the settings panel is the GUI route to the same connections the CLI flow sets up.

render_dashboardrender_settingsrefresh_data

15 tools

Counted once with only startup setup. Other versions, modes or optional credentials may expose a different list.

`add_custom_token`

Adds a project-specific ERC-20 token to a MetaMask account's tracked-tokens list. The bundled common tokens (USDC, USDT, WETH, WBTC, LINK, DAI) are tracked by default; this is for additional tokens like project / governance tokens. Use when the user asks: 'track ARB token', 'add UNI to my wallet', 'monitor a custom ERC-20'. Token data is PUBLIC on-chain (contract + symbol + decimals) — NO secrets, NO keychain involved. Inputs: - account_id: target MetaMask account (e.g. 'metamask:0xabc...') - chain_id: numeric (1=Ethereum, 137=Polygon, 56=BSC, 8453=Base, 42161=Arbitrum, 10=Optimism) - contract: 0x-prefixed contract address (40 hex) - symbol: 1-20 chars - decimals: 0-36 integer

`get_pnl`

Returns aggregate profit/loss across all configured accounts. Use this when the user asks: 'how am I doing', 'what's my P&L', 'am I up or down', 'show profit', 'show losses', or wants any portfolio performance summary. Returned fields per account and across the total: - currentValue (USD) — current portfolio value - costBasis (USD) — sum of avgCost * quantity (where the connector tracks it) - unrealizedPnl (USD) — currentValue - costBasis (for positions still held) - realizedPnl (USD) — already-closed P&L from connector metadata - notes — caveats per connector (e.g. MetaMask doesn't track cost basis) Inputs (optional): - account_id: scope to one account. - timeframe: '24h' | '7d' | '30d' | 'ytd' | 'all'. When set to anything other than 'all', the result includes a windowDelta block computed from CoinGecko historical prices. APPROXIMATION CAVEAT: it values your CURRENT basket at historical prices vs current prices — it does NOT account for trades within the window. Communicate this honestly to the user. Polymarket positions and tokens without a CoinGecko mapping are skipped (counted in skippedSymbols). CoinGecko free-tier historical is daily granularity, so '24h' = 'yesterday's close'. - include_history (boolean, default false): also pulls transactions and runs a cost-basis ledger over them, returning realizedFromHistory per account + total. Costs an extra round-trip per account but unlocks honest realized PnL on tokens born on-chain (LP rewards, swaps, native airdrops). Tokens that arrived via wallet transfer-in (no price) get unknownSalesCount not inflated knownRealized — explicit honesty about what cost basis we know. POLYMARKET-SPECIFIC: when include_history=true, the Polymarket account's realizedPnl is replaced by the cost-basis-from-/trades number. Default mode leaves Polymarket realizedPnl null because the connector's cashPnl mixes realized + unrealized — set include_history=true to get the real realized number. - method ('fifo' | 'average', default 'fifo'): cost basis method used when include_history=true. FIFO consumes oldest lot first per sell; Average Cost pools all priced acquisitions and sells out at the running average. If the user mentions 'average cost' / 'avg cost' / 'weighted', use 'average'. Both methods preserve the 'honest unknown' rule: any sell drawing from an unpriced deposit/transfer returns realizedPnl=null, NOT a fabricated number. Has NO effect when include_history=false. - currency ('USD' | 'EUR' | 'GBP' | 'HUF', default 'USD'): when set to anything other than USD, ALL numeric fields (currentValue, costBasis, realizedPnl, unrealizedPnl, windowDelta numbers, realizedFromHistory.knownRealized) are converted via live FX rates. The fx.source + fetchedAt are surfaced in meta.fx. Use this for currency-consistent rendering when the user asked their dashboard to be in HUF/EUR/GBP — otherwise per-tab currencies will mismatch. Returns position data only. Not financial advice.

`setup_connector`

Creates a new account by writing READ-ONLY credentials to the OS keychain. Use when the user asks: 'add a Bybit account', 'connect Binance', 'connect my MetaMask wallet', 'set up Polymarket', 'connect my Solana wallet', 'track my Hyperliquid', 'add my Hyperliquid wallet', 'add new exchange'. BEHAVIOR CONTRACT FOR YOU (the LLM): - After this tool succeeds, confirm ONLY the account label and account_id back to the user. - NEVER echo, log, paraphrase, or repeat the credential values (apiKey, apiSecret, etherscanApiKey) in your response. - If the user pastes credentials inline in chat, suggest they use the Settings UI (render_settings tool) form instead — the form keeps secrets out of the conversation transcript. Credentials are validated against the upstream API before they're persisted; if validation fails, nothing is written. Storage: OS keychain (macOS Keychain / Linux Secret Service / Windows Credential Vault) via @napi-rs/keyring. Same path as the CLI setup flow. All six connectors use READ-ONLY credentials by design (Bybit 'Read' only, Binance 'Enable Reading' only, Etherscan is a public-data rate-limit token, Polymarket proxy wallet is already public, Solana/Hyperliquid addresses are public on-chain identifiers — Hyperliquid needs no key or signature at all). Inputs (one of bybit / binance / metamask / polymarket / solana / hyperliquid required): - connector: 'bybit' | 'binance' | 'metamask' | 'polymarket' | 'solana' | 'hyperliquid' - bybit: { apiKey, apiSecret, accountType: 'UNIFIED'|'CONTRACT'|'SPOT'|'FUND' (primary, also the account ID), accountTypes?: array of additional types to fan out across (e.g. ['FUND'] alongside UNIFIED so funding-wallet balances are tracked too) } - binance: { apiKey, apiSecret, includeFutures (optional bool, default false), recvWindow (optional ms) } - metamask: { address, etherscanApiKey, chainIds (number[]), trackCommonTokens (bool), hasEtherscanPro (bool) } - polymarket: { proxyWallet (0x...), sizeThreshold (default 0.01) } - solana: { address (base58), rpcUrl (optional premium RPC), dustThresholdUsd (optional, default 0.5) } - hyperliquid: { address (0x... EVM address you trade from), dustThresholdUsd (optional, default 0.5). No API key — public address only. Tracks perp account equity + open positions + spot balances. }

BEFORE YOU INSTALL

What to know first

Tools you get

15 tools when we connected. Data tools return only venues you have configured, so a fresh install returns just the demo. render_dashboard and render_settings draw interactive panels, and setup_connector stores credentials in your OS keychain.

Requires

npx on PATH

Where it runs

Both documented setups run the server on your machine.

CONTEXT COST

Moderate Standing cost

Rated by the size of the 15 tool definitions that ride along on every turn, not by how many there are

INSTALLATION

Connect your client

Server setup

TERMINAL

npm install -g headless-tracker

MCP Clients

Claude Desktop — npx

CLAUDE DESKTOP — NPX · JSON

{
  "mcpServers": {
    "headless-tracker": {
      "command": "npx",
      "args": [
        "-y",
        "headless-tracker"
      ]
    }
  }
}

Claude Desktop — global install

CLAUDE DESKTOP — GLOBAL INSTALL · JSON

{
  "mcpServers": {
    "headless-tracker": {
      "command": "headless-tracker"
    }
  }
}

Headless Tracker

The credential handling is written into the tool descriptions, and it is more careful than most — read-only keys, the OS keychain, and a rule for what the model may repeat back.

What it is

What you get

Requirements

Setup effort

Answering "what do I actually own" across venues in one call

Working out whether you are up or down, and by which measure

Connecting a new exchange or wallet without leaking a key

Tracking a project token the defaults do not cover

Checking prediction-market bets apart from everything else

Getting a live panel instead of a wall of numbers

15 tools

`add_custom_token`

`add_wallet_address`

`get_allocations`

`get_holdings`

`get_pnl`

`get_polymarket_positions`

`get_transactions`

`list_accounts`

`list_custom_tokens`

`refresh_data`

`remove_account`

`remove_custom_token`

`render_dashboard`

`render_settings`

`setup_connector`

What to know first

Tools you get

Requires

Where it runs

Moderate Standing cost

Connect your client

Server setup

MCP Clients

Claude Desktop — npx

Claude Desktop — global install

Headless Tracker

The credential handling is written into the tool descriptions, and it is more careful than most — read-only keys, the OS keychain, and a rule for what the model may repeat back.

What it is

What you get

Requirements

Setup effort

Answering "what do I actually own" across venues in one call

Working out whether you are up or down, and by which measure

Connecting a new exchange or wallet without leaking a key

Tracking a project token the defaults do not cover

Checking prediction-market bets apart from everything else

Getting a live panel instead of a wall of numbers

15 tools

add_custom_token

add_wallet_address

get_allocations

get_holdings

get_pnl

get_polymarket_positions

get_transactions

list_accounts

list_custom_tokens

refresh_data

remove_account

remove_custom_token

render_dashboard

render_settings

setup_connector

What to know first

Tools you get

Requires

Where it runs

Moderate Standing cost

Connect your client

Server setup

MCP Clients

Claude Desktop — npx

Claude Desktop — global install

Same category

Banco MCP

BankBridge

Monzo

Actual Budget MCP

`add_custom_token`

`add_wallet_address`

`get_allocations`

`get_holdings`

`get_pnl`

`get_polymarket_positions`

`get_transactions`

`list_accounts`

`list_custom_tokens`

`refresh_data`

`remove_account`

`remove_custom_token`

`render_dashboard`

`render_settings`

`setup_connector`