Unlock Pulse

io.github.Billibo6Published by GitHub account Billibo6v1.10.1Updated Nov 4, 2026

Token unlock calendar for the next 60 days, rated by size vs circulating supply. Free, no key.

VerifiedStreamable HTTPWeb executableFinanceData & Analytics

Overview

AI-generated overview

Read-only crypto token unlock calendar MCP server that lets an assistant list upcoming vesting unlocks, rate their size, and check on-chain wallet activity.

What you can do
  • List upcoming token unlocks for the next 1–60 days, rated strong, medium or small by size versus circulating supply, filterable by size and futures availability
  • Look up all scheduled unlocks for one token by ticker, name or slug, with dates, USD value, recipients and futures availability
  • Inspect on-chain activity of wallets holding locked team, investor and treasury tokens: balances, outflows, mints, burns and contract upgrades
  • Explain the rating method and historical price record around past unlocks of each strength
  • Describe the dataset itself: version, refresh time, coverage, sources, formula, limitations and citation terms
When to use it
Useful when someone asks which token unlocks are coming soon, how large an unlock is relative to circulating supply, who receives the tokens, or whether locked wallets have actually moved funds. It is a research aid for crypto market questions, not a trading or advisory tool.
Requirements
Remote Streamable HTTP endpoint, no key or sign-up. Optionally run locally with Node 18+ from a single file with no dependencies. Internet access is needed for live data.
Before you install
Read-only and free, with no credentials requested. Data is compiled from third-party sources (CoinMarketCap, DefiLlama) and may disagree on circulating supply; the server states it is market data, not investment advice. Attribution terms (CC BY 4.0) apply to reuse of the data.

Installation

In SourceWeft

  1. Open Unlock Pulse in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/io.github.Billibo6%2Funlockpulse/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "unlock-pulse": {
      "type": "http",
      "url": "https://unlockpulse-mcp.unlockpulse.workers.dev/mcp"
    }
  }
}

README

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):
    json
    {"mcpServers": {"unlockpulse": {"url": "https://unlockpulse-mcp.unlockpulse.workers.dev/mcp"}}}

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

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

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

Tools

ToolWhat it returns
get_upcoming_unlocksUnlocks in the next 1–60 days, rated strong / medium / small, filters by size and futures availability
get_token_unlocksEvery 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_checkWhat the wallets holding locked team, investor and treasury tokens do on-chain: balances, outflows, findings
get_method_and_track_recordHow the rating works and how prices moved before past unlocks of each strength
get_dataset_infoData 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.

Source: README.md at commit 5703be8

Tools

5

get_upcoming_unlocks

Upcoming token unlocks

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. Schedules are compiled from CoinMarketCap and DefiLlama. 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.

Parametersdayslangsortlimitfuturesmin_strength

get_token_unlocks

Unlocks for one token

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. recipient_selling_habit (when present) says how often recipients of this coin's past unlocks sold within 7 days; it is reference only and did not predict price. lang=ru returns Russian page links.

Parameterslangtokenrequired

get_onchain_check

Locked-token wallets on-chain

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.

Parametersdayslangtoken

get_method_and_track_record

How unlocks are rated, and what happened before past ones

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.

Takes no parameters.

get_dataset_info

What the data covers

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.

Takes no parameters.

Version history

5
  1. v1.10.1LatestNov 4, 2026
  2. v1.10.0Nov 4, 2026
  3. v1.9.5Nov 3, 2026
  4. v1.9.4Nov 3, 2026
  5. v1.9.1Oct 29, 2026

Score

90% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listedRequired15 pts
  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts

    Declare a license in the repository or the registry entry.