Unlock Pulse

io.github.Billibo6由 GitHub 账号 Billibo6 发布v1.10.1更新于 Nov 4, 2026

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

已验证Streamable HTTP可网页运行金融数据与分析

概览

AI 生成的概览

只读的加密代币解锁日历 MCP 服务器,让助手查询未来解锁安排、按规模评级,并查看锁仓钱包的链上动向。

可以做什么
  • 列出未来 1–60 天的代币解锁,按解锁量占流通量的比例评为强、中、小,并可按规模和是否有永续合约筛选
  • 按代码、名称或 slug 查询单个代币的全部解锁安排,含日期、美元价值、接收方和期货可用性
  • 查看持有团队、投资人和金库锁仓代币的钱包链上活动:余额、流出、增发、销毁和合约升级
  • 解释评级方法,以及过去各强度解锁前后的历史价格表现
  • 说明数据集本身:版本、刷新时间、覆盖范围、来源、公式、局限和引用条款
适用场景
适合回答近期有哪些代币解锁、解锁规模相对流通量有多大、代币发给谁,以及锁仓钱包是否真的动过资金等问题。它是加密市场研究的辅助工具,不构成交易或投资建议。
运行要求
远程 Streamable HTTP 端点,无需密钥或注册。也可用 Node 18+ 以单文件本地运行,无依赖。获取实时数据需要联网。
安装前请注意
只读且免费,不索取任何凭据。数据来自第三方来源(CoinMarketCap、DefiLlama),流通量数据可能不一致;服务器声明这是市场数据而非投资建议。复用数据需遵守 CC BY 4.0 署名条款。

安装

在 SourceWeft 中

  1. 打开 控制台中的 Unlock Pulse,将其添加到工作区。
  2. 为需要使用其工具的对话启用该服务。

Web executable,通过 Streamable HTTP。 远程服务在工作区中配置后即可从网页运行时运行。

交给智能体安装

把这段提示词粘贴到 Claude Code、Codex、Cursor 等智能体,或 SourceWeft 对话中。智能体会读取该服务器的安装指南,先向你展示发布者、端点和登录方式,经你同意后再把它添加到你的客户端。密钥不会写进任何命令。

阅读 https://sourceweft.com/mcp/io.github.Billibo6%2Funlockpulse/install.md,并按其中说明把这个 MCP 服务器接入我的客户端。修改任何配置之前,先告诉我它的发布者、端点和登录方式,等我确认。不要把 API 密钥写进命令或我会提交的文件;问我密钥应从哪里获取。

查看智能体所依据的安装指南

其他 MCP 客户端

把它添加到你客户端的 mcpServers 配置中。

{
  "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.

来源:README.md,提交 5703be8

工具

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.

输入参数dayslangsortlimitfuturesmin_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.

输入参数langtoken必填

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.

输入参数dayslangtoken

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.

无需输入参数。

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.

无需输入参数。

版本历史

5
  1. v1.10.1最新Nov 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

评分

已满足适用检查项的 90%

该评分衡量此收录条目的完整程度,依据注册中心条目、端点与公开来源计算得出。它不是对服务器本身的评价,也不表示服务器安全或当前可用:可连通性是带日期的检查结果,评分也不包含安装量或用户评价。

  • 近 30 天内可连通必需25 分
  • 已声明认证方式必需10 分
  • 已列出工具必需15 分
  • 描述必需15 分
  • 图标10 分
  • 文档15 分
  • 许可证10 分

    请在仓库或注册中心条目中声明许可证。