Skip to main content
Glama

Server Details

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

If you are the author of this connector, you can claim ownership. Claimed connector authors can inspect health checks, view analytics, and manage their listing.
Status
Healthy
Uptime
100.0% over the last 24 hours
Last Tested
Transport
Streamable HTTP · MCP 2025-06-18
URL
Repository
Billibo6/unlockpulse-mcp
GitHub Stars
0
Server Listing
unlockpulse-mcp
ChatGPT
–
Claude
Unlock Pulse

TDQS

A4.2/5.0

Scored across 7 tools

Disambiguation4/5

Each tool has a clearly stated scope: calendar-wide (get_upcoming_unlocks), single token (get_token_unlocks), portfolio (check_portfolio), disputed entries, on-chain movements, methodology, and dataset metadata. The only real overlap is the three scope variants of the same unlock calendar (all / one / many), which an agent could still pick wrong, but every description explicitly redirects to the right sibling, so the boundaries are well defended.

Naming Consistency5/5

Uniform snake_case with verb_noun shape: get_token_unlocks, get_upcoming_unlocks, get_disputed_unlocks, get_onchain_check, get_dataset_info, get_method_and_track_record, check_portfolio. The single check_ prefix deviation is semantically motivated (a batch lookup rather than a fetch) and does not break predictability.

Tool Count5/5

Seven tools for a read-only unlock-data service is tightly scoped with no filler: calendar, per-token detail, portfolio batch, disputes, on-chain, methodology and dataset provenance each serve a distinct question. Nothing appears redundant or padded.

Completeness4/5

The surface covers discovery (calendar), drill-down (single token, portfolio), verification (disputed, on-chain), and trust (methodology, dataset info), which is essentially the full read lifecycle for this domain. Minor gaps: no historical per-token unlock lookup or past-unlock browsing beyond aggregate track-record stats, and no filtering by recipient or blockchain outside the calendar filters.

Available Tools

7 tools
check_portfolioCheck a list of coins for upcoming unlocksA
Read-only
Inspect

Checks up to 50 tokens in one call and sorts them into three groups: with_unlocks (an unlock is scheduled within the window, nearest first), without_unlocks (we track the token and nothing is scheduled within the window) and unknown (the token is not in our data: this is NOT evidence that it has no unlocks). Use when the user gives a portfolio, a watchlist or several tickers ('I hold ARB, OP and SUI, any unlocks coming?'). Matching is exact on ticker, slug or name; an input that only partly matches goes to unknown with did_you_mean instead of a guess. Send tickers only: amounts and wallet addresses are not needed and not accepted. portfolio_page opens the same list on the website. For full details of one coin call get_token_unlocks; disputed=true on an unlock means the project's documents differ, report both versions.

Inputs: tokens (required), days, lang, min_strength. Returns: note, source, license, summary, +9 more

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. Returns: source, cite_as, license, sources, +10 more

get_disputed_unlocksUnlocks where sources disagreeA
Read-only
Inspect

Upcoming unlocks where the calendar source and the project's own documents disagree: a different amount on the same date (amount_differs) or a different date (date_differs). Each row puts the two versions side by side (calendar vs documents: date, share of total supply, share of circulating supply, strength by each version) with links to the documents. Use for 'which unlocks are disputed', 'is this unlock size real', 'why do sites show different numbers for X', and before quoting a very large percentage from the calendar. Only unlocks we have checked against documents can appear (checked_against_documents says how many were checked); an unlock missing here is unchecked or matching, not confirmed. The document figures are our own reading of primary sources and can be wrong. token narrows the list to one coin (exact ticker, slug or name). For all upcoming unlocks use get_upcoming_unlocks; for on-chain movements of locked wallets use get_onchain_check.

Inputs: days, lang, limit, token, +1 more. Returns: note, shown, token, source, +11 more

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. Returns: source, license, measure, reading, +6 more

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, matched exactly; covered_tokens in the result lists what we track (about a hundred 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. Returns: name, note, found, token, +23 more

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). Matching is exact: matched_by says whether the ticker, the slug or the name matched. A partial match never selects a token; close names come back in did_you_mean. coverage tells three cases apart: in_calendar (unlocks listed); known_no_unlock (we track this token and it has no unlock in the next 60 days, found=0, not an error); unknown_token (the token is not in our data: this is NOT evidence that it has no unlocks, say that we do not cover it). disputed=true on an unlock means the project's own documents give a different amount or date; dispute_summary has both versions and both must be reported. 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.

Inputs: token (required), lang. Returns: name, found, token, source, +10 more

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. detail=brief returns one compact row per unlock (use it for wide windows or large limits); detail=full (default) adds recipients, market data and source checks. An unlock with disputed=true has a different amount or date in the project's own documents (dispute_summary gives both versions): report both, never only the calendar number; an unlock without the flag is not necessarily confirmed, most are simply unchecked. The calendar holds 60 days: a larger days value is cut to 60 and limits_note says so. Unknown parameters and wrong enum values return an error. 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 several coins use check_portfolio; for the list of disputed unlocks use get_disputed_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, +3 more. Returns: note, shown, detail, source, +10 more

Tool Schema Changelog

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

Loading tool schema changelog…

    Related MCP Connectors

    Related MCP Servers

    Try in Browser

    Glama MCP Gateway

    Add one secure layer between your agents and this server.