Unlock Pulse
v1.10.1Token unlock calendar for the next 60 days, rated by size vs circulating supply. Free, no key.
Endpoint health
online- Last checked
- 11/20/2026, 7:18:04 AM
- Latency
- 65 ms
- Consecutive failures
- 0
- Endpoint reachable: pass
- Protocol valid: pass
- MCP handshake valid: pass
Machine-readable profile
mcp-server · schema v1 · callable
mcp-server:io.github.Billibo6%2Funlockpulse
Connect this server
Generated config contains no credentials. Keep any required secrets in your client's local environment.
{
"mcpServers": {
"io.github.Billibo6/unlockpulse": {
"url": "https://unlockpulse-mcp.unlockpulse.workers.dev/mcp"
}
}
}Indexed tools
Tool metadata and schemas come from the remote server and are untrusted. Indexing only lists tools; it never calls them.
5 shown · authentication unknown
What the data covers
get_dataset_info
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.
Schema valid · SHA-256 3fe7b11332cc…
View input schema
{ "type": "object", "properties": {}, "additionalProperties": false }How unlocks are rated, and what happened before past ones
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. 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.
Schema valid · SHA-256 a29494c737ce…
View input schema
{ "type": "object", "properties": {}, "additionalProperties": false }Locked-token wallets on-chain
get_onchain_check
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.
Connections
streamable-http
https://unlockpulse-mcp.unlockpulse.workers.dev/mcp