Unlock Pulse
Token unlock calendar for the next 60 days, rated by size vs circulating supply. Free, no key.
Should I use this
Quality & Safety
Based on automated analysis of tool definitions and protocol compliance.
Context Cost
This is the approximate number of tokens consumed each time the server's tools are loaded into a model's context. Higher counts reduce the attention available for other tasks.
Install
One-Click Install
Add this to your `claude_desktop_config.json` file:
{
"mcpServers": {
"unlockpulse": {
"url": "https://unlockpulse-mcp.unlockpulse.workers.dev/mcp"
}
}
}Remote endpoints
https://unlockpulse-mcp.unlockpulse.workers.dev/mcpstreamable-httpWhat it can do
Tool inventory
Tools (4)
🟢get_upcoming_unlocks(days, min_strength, futures, sort, limit, ...)
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'.
Input Schema
{
"type": "object",
"properties": {
"days": {
"type": "number",
"minimum": 1,
"maximum": 60,
"default": 14,
"description": "Look-ahead window in days."
},
"min_strength": {
"type": "string",
"enum": [
"strong",
"medium",
"small"
],
"default": "small",
"description": "Lowest strength to include."
},
"futures": {
"type": "string",
"enum": [
"any",
"with_futures",
"kucoin",
"binance"
],
"default": "any",
"description": "Filter by perpetual futures availability."
},
"sort": {
"type": "string",
"enum": [
"date",
"size"
],
"default": "date",
"description": "date = soonest first; size = largest share of circulating supply first."
},
"limit": {
"type": "number",
"minimum": 1,
"maximum": 100,
"default": 30
},
"lang": {
"type": "string",
"enum": [
"en",
"ru"
],
"default": "en",
"description": "Language of the page links."
}
},
"additionalProperties": false
}🟢get_token_unlocks(token, lang)
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).
Input Schema
{
"type": "object",
"properties": {
"token": {
"type": "string",
"minLength": 1,
"maxLength": 60,
"description": "Ticker, name or slug."
},
"lang": {
"type": "string",
"enum": [
"en",
"ru"
],
"default": "en"
}
},
"required": [
"token"
],
"additionalProperties": false
}🟢get_onchain_check(token, days, lang)
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.
Input Schema
{
"type": "object",
"properties": {
"token": {
"type": "string",
"maxLength": 60,
"description": "Ticker, name or slug. Leave empty for recent movements across all covered tokens."
},
"days": {
"type": "number",
"minimum": 1,
"maximum": 30,
"default": 30,
"description": "Look-back window for the list of recent movements (no token)."
},
"lang": {
"type": "string",
"enum": [
"en",
"ru"
],
"default": "en",
"description": "Language of the page links."
}
},
"additionalProperties": false
}🟢get_method_and_track_record
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.
Input Schema
{
"type": "object",
"properties": {},
"additionalProperties": false
}Community
Evidence