Headlesstracker MCP Server

Read-only MCP server: let your AI read your whole crypto portfolio across exchanges, on-chain wallets, and prediction markets -- never your API keys, and it can't trade or withdraw. Not financial advice. Exposed over MCP by the headlesstracker mcp server, that capability becomes something an assistant can invoke while it works, not something you go and do afterwards.

What it actually does

↑ What your AI host renders from HeadlessTracker's data — one question, six venues, one view. The server returns the numbers; the host draws the picture. (Sample data; the visual is what a host renders on top of the tool output.)

• "What do I own?"
• "How is my portfolio split between crypto and prediction markets?"
• "Show my Polymarket positions grouped by event."
• "Refresh Bybit and tell me my BTC P&L."

Adding it to your client

headless-tracker on npm is all you need. Most clients run it directly, so configuration is a few lines and a restart.

Configuration

You will need 3 environment variables: HT_SETUP_ETHERSCAN_KEY, HT_SETUP_API_KEY, HT_SETUP_API_SECRET. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.

When to reach for it

Plenty of developer tooling servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. It is maintained by tamaspetki; worth a glance at recent repository activity before you build anything load-bearing on it.

SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.

Caveats

• It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
• Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
• MCP clients confirm each tool call by default. Leave that on until you have watched what the headlesstracker mcp server does with a few real requests.