Skip to main content
Glama
unlockpulse-mcp

unlockpulse-mcp

Unlock Pulse MCP

Token unlock calendar for AI assistants. Ask Claude, ChatGPT or Cursor which crypto token unlocks are coming, how big they are against the coins already trading, who receives the tokens, and what prices did before similar unlocks in the past.

Free, read-only, no key, no sign-up. Website: https://billibo6.github.io/unlockpulse/ Telegram alerts about 24h before each unlock of 2%+ of supply: https://t.me/+22nzXAYLCGsyMzJi

Connect

Remote server (recommended): https://unlockpulse-mcp.unlockpulse.workers.dev/mcp (Streamable HTTP).

  • Claude Code: claude mcp add --transport http unlockpulse https://unlockpulse-mcp.unlockpulse.workers.dev/mcp

  • Claude (web, desktop, mobile): Settings → Connectors → Add custom connector → paste the address.

  • ChatGPT: Settings → Apps & Connectors → Advanced → Developer mode → Create → paste the address.

  • Cursor, VS Code, Windsurf (mcp.json):

    {"mcpServers": {"unlockpulse": {"url": "https://unlockpulse-mcp.unlockpulse.workers.dev/mcp"}}}

Run it locally instead (one file, Node 18+, no dependencies):

{"mcpServers": {"unlockpulse": {"command": "node", "args": ["/path/to/unlockpulse-mcp.mjs"]}}}

Also listed in the official MCP Registry as io.github.Billibo6/unlockpulse.

Related MCP server: Swiss Whale Intelligence

Tools

Tool

What it returns

get_upcoming_unlocks

Unlocks in the next 1–60 days, rated strong / medium / small, filters by size and futures availability

get_token_unlocks

Every scheduled unlock of one token: date, size, USD value, recipients, futures, and for some coins how often recipients of past unlocks sold (reference only, not a signal)

get_onchain_check

What the wallets holding locked team, investor and treasury tokens do on-chain: balances, outflows, findings

get_method_and_track_record

How the rating works and how prices moved before past unlocks of each strength

get_dataset_info

Data freshness, coverage, sources, formula, limitations and how to cite

Strength: B = tokens unlocked / circulating supply. Strong: B ≥ 10.4%, medium: B ≥ 5%.

Skill

skills/unlock-pulse/SKILL.md tells Claude which tool to call for which question and how to present the answer.

npx skills add Billibo6/unlockpulse-mcp

Data

Monthly unlock lists as CSV (snapshots; live versions update hourly) are in data/. Open data: CC BY 4.0.

Research dataset (unlock ratings, 7-day event study against Bitcoin around 304 past unlocks, date checks, schedule changes, on-chain checks): doi.org/10.5281/zenodo.23949644 on Zenodo, CC BY 4.0.

Example questions

  • "Which strong token unlocks are coming in the next two weeks?"

  • "Biggest unlocks with perpetual futures on Binance this month."

  • "When is the next ARB unlock, and who gets the tokens?"

  • "Have the team and investor wallets of this token moved anything? Did the unlock really happen?"

Data and license

Code: MIT. Data served by the tools (our ratings, track record, on-chain measurements, texts): CC BY 4.0, keep the link to Unlock Pulse. Unlock schedules are compiled from CoinMarketCap and DefiLlama and remain subject to their terms. Market data, not investment advice.

Test

node test.mjs

The tests call the live data file, so they need internet access.

Available Tools

5 tools
get_dataset_infoWhat the data coversA
Read-only
Inspect

Describes the Unlock Pulse dataset itself: server version, when it was last refreshed, how many upcoming unlocks it holds and how far ahead, how many past unlocks the track record is built on, which blockchains the on-chain check covers, sources, the strength formula and thresholds, known limitations and how to cite. Use when the user asks where the numbers come from, how fresh or complete they are, or how to cite them.

Inputs: no named parameters.

get_method_and_track_recordHow unlocks are rated, and what happened before past onesA
Read-only
Inspect

Explains the strong / medium / small rating and gives the historical record: for past unlocks of each strength, how often the token fell against Bitcoin in the week before the unlock and the average move. Use when the user asks what 'strong' means, whether unlocks move prices, or how reliable the rating is. Not a forecast for any single token.

Inputs: no named parameters.

get_onchain_checkLocked-token wallets on-chainA
Read-only
Inspect

What is actually happening on-chain with a token's locked allocations: the vesting contracts and wallets holding team, investor and treasury tokens, how much they hold now, outflows (tokens leaving locked wallets), mints, burns and contract upgrades, the next unlock by the project's own documents, and our short finding (for example: unlocked but never withdrawn, tranches sent to an exchange, vesting contract has not paid out). Use for 'are team tokens moving', 'did the unlock really happen', 'who is selling'. Without a token: recent movements across all covered tokens. token accepts a ticker (preferred), a name or a slug; covered_tokens in the result lists what we track (a few dozen tokens, not the whole calendar). Movements look back at most 30 days; wallet roles marked 'our attribution' are our analysis, not the project's statement. For the unlock calendar use get_token_unlocks.

Inputs: days, lang, token.

get_token_unlocksUnlocks for one tokenA
Read-only
Inspect

All scheduled unlocks in the next 60 days for one token, with recipients (team, investors, treasury ...), USD value, share of circulating supply, futures availability and a link to the token page. Accepts a ticker (ARB), a name (Arbitrum) or a slug (arbitrum). Returns found=0 if the token has no unlock in the next 60 days (that is not an error). If the result mentions onchain_check, call get_onchain_check to see what the locked wallets are doing. lang=ru returns Russian page links.

Inputs: token (required), lang.

get_upcoming_unlocksUpcoming token unlocksA
Read-only
Inspect

Calendar of scheduled crypto token unlocks in the next N days (up to 60), each rated strong / medium / small by size relative to circulating supply. Use for questions like 'which token unlocks are coming this week', 'biggest unlocks in November', 'strong unlocks with perpetual futures'. Data refreshes hourly (data_updated_utc in the result). Results are cut to 'limit' (default 30): 'matched' says how many fit the filters. The futures filter covers KuCoin and Binance USDT perpetuals only. For one coin use get_token_unlocks; for what the rating means and past results use get_method_and_track_record; for coverage and sources use get_dataset_info. lang=ru returns Russian page links.

Inputs: days, lang, sort, limit, +2 more.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    A4.4/5.0

    Scored across 5 tools

    Disambiguation4/5

    The calendar tool and the per-token tool clearly differ (many unlocks vs one token, up to 60 days), and their descriptions explicitly cross-reference each other. The only real overlap is between get_method_and_track_record (rating explanation + track record) and get_dataset_info (sources, formula, thresholds, limitations) — both partly explain the rating methodology, so an agent may pause over which to call.

    Naming Consistency5/5

    All five tools follow a uniform snake_case get_<noun> pattern with descriptive noun phrases. No mixing of conventions, no vague verbs like process or run.

    Tool Count5/5

    Five tools is well-scoped for a narrow, single-domain data server (unlock calendar, per-token unlocks, on-chain check, methodology, dataset info). Each tool covers a distinct access path and none looks redundant.

    Completeness4/5

    The surface covers discovery (calendar with filters), drill-down (per token), verification (on-chain), and trust/provenance (method, dataset info) — a coherent lifecycle for this domain. Minor gaps: no tool to enumerate covered tokens/blockchains directly, and past unlocks are only exposed in aggregate via the track record rather than as queryable history for a specific token.

    Maintenance

    ActivityMaintained
    ResponsivenessOutdated data

    Related MCP Connectors

    Related MCP Servers