Unlock Pulse
REMOTE · UNLOCKPULSE-MCP.UNLOCKPULSE.WORKERS.DEV
Token unlock calendar for the next 60 days, rated by size vs circulating supply. Free, no key.
Available components
Last scanned (11 hours ago)
Scores higher than 53% of remote servers
Reachable. Last reached 5 Nov 2026.
Category Crypto and Web3
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security63
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement. View diagnostics → Unverified
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability66
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 1116 tokens (~223/item across 5 items; 5 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management30
- Stability observed for 9 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage95
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 82% of tool parameters carry a description.Partial
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 4 Nov 26 +1
- The server rewrote its instructions, which are the text every model session reads security
- Tool “get_upcoming_unlocks” rewrote its description, which is the text the model reads security
- Tool “get_dataset_info” now declares an output schema ▲ functional
- Tool “get_method_and_track_record” now declares an output schema ▲ functional
- Tool “get_onchain_check” now declares an output schema ▲ functional
- Tool “get_token_unlocks” now declares an output schema ▲ functional
- Tool “get_upcoming_unlocks” now declares an output schema ▲ functional
- First check of Tool coverage: 100 functional
- Server version: 1.10.0 → 1.10.1 functional
- Server version: 1.9.5 → 1.10.0 functional
- 3 Nov 26 0
- Tool “get_token_unlocks” rewrote its description, which is the text the model reads security
- Server version: 1.9.4 → 1.9.5 functional
- 2 Nov 26 0
- Server version: 1.9.3 → 1.9.4 functional
- Server version: 1.9.1 → 1.9.3 functional
- 1 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.
- 30 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.
- 29 Oct 26 +1
- The server rewrote its instructions, which are the text every model session reads security
- Tool “get_method_and_track_record” rewrote its description, which is the text the model reads security
- Tool “get_onchain_check” rewrote its description, which is the text the model reads security
- Tool “get_token_unlocks” rewrote its description, which is the text the model reads security
- Tool “get_upcoming_unlocks” rewrote its description, which is the text the model reads security
- Schema quality: 189 → 222 ▼ functional
- Schema quality: good → excellent functional
- Server version: 1.9.0 → 1.9.1 functional
- Server version: 1.8.2 → 1.9.0 functional
- Server version: 1.8.1 → 1.8.2 functional
- New tool “get_dataset_info” functional
- 28 Oct 26 0
- The server rewrote its instructions, which are the text every model session reads security
- Schema quality: 166 → 189 ▼ functional
- Tool coverage: 75% → 82% ▲ functional
- Stability: unverified → 0.03 ▲ functional
- Server version: 1.8.0 → 1.8.1 functional
- Server version: 1.7.0 → 1.8.0 functional
- Server version: 1.4.0 → 1.7.0 functional
- Server version: 1.1.0 → 1.4.0 functional
- New tool “get_onchain_check” functional
- 27 Oct 26 63
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 5 Nov 2026 · Probed https://unlockpulse-mcp.unlockpulse.workers.dev/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=unlockpulse.workers.dev | CN=YE1,O=Let's Encrypt,C=US | 27 Oct 2026 | 25 Jan 2027 | ECDSA 256 | ECDSA-SHA384 | 60d17b355c2573339ed44c54d94241850ca |
| SANs: *.unlockpulse.workers.dev, unlockpulse.workers.dev | ||||||
| CN=YE1,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 5ddd70dd31f801c85c186a7a04b80afe |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of unlockpulse-mcp.unlockpulse.workers.dev. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| dev. | present | 60074 | 8 | Verified |
| workers.dev. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://unlockpulse-mcp.unlockpulse.workers.dev/mcp | Verified | 200 | |
| http (plaintext) | http://unlockpulse-mcp.unlockpulse.workers.dev/mcp | Inconclusive | 405 |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
get_dataset_info What the data covers ~98
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.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| calendar | object | – | – |
| cite_as | string | – | – |
| data_updated_utc | string|null | – | – |
| license | string|null | – | – |
| limitations | array | – | – |
| method_page | string | – | – |
| on_chain_check | object | – | – |
| open_dataset | object | – | – |
| server_version | string | yes | – |
| source | string | yes | – |
| sources | object | yes | – |
| strength_formula | string | – | – |
| thresholds | object | – | – |
| track_record | object | – | – |
No examples provided.
get_method_and_track_record How unlocks are rated, and what happened before past ones ~84
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.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| data_updated_utc | string|null | – | – |
| license | string|null | – | – |
| live_journal_page | string | – | – |
| measure | string | – | – |
| method_page | string | – | – |
| reading | string | – | – |
| source | string | yes | – |
| thresholds | object | yes | – |
| track_record | object | yes | – |
| track_record_window | string | – | – |
No examples provided.
get_onchain_check Locked-token wallets on-chain ~250
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.
| Name | Type | Req | Description |
|---|---|---|---|
| days | number | – | Look-back window for the list of recent movements (no token). |
| lang | string | – | Language of the page links. |
| token | string | – | Ticker, name or slug. Leave empty for recent movements across all covered tokens. |
| Name | Type | Req | Description |
|---|---|---|---|
| attribution_note | string | – | – |
| covered_tokens | array | – | – |
| data_updated_utc | string|null | – | – |
| events | array | – | – |
| finding | – | – | – |
| found | boolean | – | – |
| license | string|null | – | – |
| message | string | – | – |
| method | string|null | – | – |
| movements | array | – | – |
| movements_found | number | – | – |
| name | string|null | – | – |
| note | string | – | – |
| reading | string | – | – |
| source | string | yes | – |
| symbol | string | – | – |
| token | string | – | – |
| tokens_with_findings | array | – | – |
| tracked_wallets | array | – | – |
| upcoming_unlocks_in_calendar | array | – | – |
| window_days | number | – | – |
No examples provided.
get_token_unlocks Unlocks for one token ~183
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.
| Name | Type | Req | Description |
|---|---|---|---|
| lang | string | – | – |
| token | string | yes | Ticker, name or slug. |
| Name | Type | Req | Description |
|---|---|---|---|
| calendar_page | string | – | – |
| data_updated_utc | string|null | – | – |
| found | number | yes | – |
| license | string|null | – | – |
| message | string | – | – |
| onchain_check | string | – | – |
| source | string | yes | – |
| token | string | – | – |
| unlocks | array | – | – |
No examples provided.
get_upcoming_unlocks Upcoming token unlocks ~254
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.
| Name | Type | Req | Description |
|---|---|---|---|
| days | number | – | Look-ahead window in days. |
| futures | string | – | Filter by perpetual futures availability. |
| lang | string | – | Language of the page links. |
| limit | number | – | – |
| min_strength | string | – | Lowest strength to include. |
| sort | string | – | date = soonest first; size = largest share of circulating supply first. |
| Name | Type | Req | Description |
|---|---|---|---|
| by_strength | object | – | – |
| calendar_page | string | – | – |
| data_updated_utc | string|null | – | – |
| license | string|null | – | – |
| matched | number | yes | – |
| note | string | – | – |
| shown | number | yes | – |
| source | string | yes | – |
| track_record_strong | string|null | – | – |
| unlocks | array | yes | – |
| window_days | number | yes | – |
No examples provided.
How do I install the Unlock Pulse MCP server?
Unlock Pulse is a hosted endpoint at https://unlockpulse-mcp.unlockpulse.workers.dev/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · unlockpulse-mcp.unlockpulse.workers.dev
claude mcp add --transport http billibo6-unlockpulse 'https://unlockpulse-mcp.unlockpulse.workers.dev/mcp'
What is the Unlock Pulse MCP server?
Unlock Pulse is an MCP server listed in the public MCP registry as io.github.Billibo6/unlockpulse. Token unlock calendar for the next 60 days, rated by size vs circulating supply. Free, no key. This page covers its hosted endpoint (https://unlockpulse-mcp.unlockpulse.workers.dev/mcp).
Is the Unlock Pulse MCP server safe to use?
Unlock Pulse scores 67 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the Unlock Pulse MCP server expose?
Unlock Pulse exposes 5 tools: get_upcoming_unlocks, get_token_unlocks, get_onchain_check, get_method_and_track_record, get_dataset_info. Their descriptions and schemas cost roughly 869 tokens of context every time the server is loaded.
Does the Unlock Pulse MCP server require authentication?
No. We connected to Unlock Pulse without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Unlock Pulse MCP server still maintained?
Unlock Pulse is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.