Skip to content

Unlock Pulse MCP server

io.github.Billibo6/unlockpulseBillibo6streamable-httpv1.11.0Scanned

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

7 tools: 1 change things and 6 only read.

Tools: 0 delete, 0 irreversible, 1 write, 6 read.
  • Reads private data · 3
  • Reads text others write · 7
  • Can send data out · 0
  • No findings

Tools listed without sign-in. Remote posture

With Anlyon

1 tool here changes things. Govern it.

  • Anlyon lists the tools and adopts none.
  • Each tool you adopt gets approvals and receipts.
  • Your agent never holds the key.
Govern this server →

A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.

What the Unlock Pulse MCP server can do

The Unlock Pulse MCP server is published by the GitHub account Billibo6. It has 7 tools. It can create or change data (1 tool: check_portfolio), but cannot delete data. 6 tools only read.

3 tools read private data (get_upcoming_unlocks, get_onchain_check and get_disputed_unlocks); 7 tools bring in text other people can write (get_upcoming_unlocks, get_token_unlocks, get_onchain_check and 4 more).

None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.

Its remote endpoint lists its tools without sign-in, and its tools changed 5 times since Anlyon Radar first saw them.

Last scanned Nov 17, 2026, version 1.11.0.

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

7 tools

Changes things 1Claude Code: ask
  • check_portfolioChecks 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…Reads text others writeNo findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: true
    • openWorldHint: true
    • title: Check a list of coins
Only reads 6Show 6 read-only tools
  • get_dataset_infoDescribes 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 …Reads text others writeNo findings

    Why it is in this group

    • The name "get_dataset_info" says "get": a word for reading.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: true
    • openWorldHint: true
    • title: What the data covers
  • get_disputed_unlocksUpcoming 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).Reads private dataReads text others writeNo findings

    Why it is in this group

    • The name "get_disputed_unlocks" says "get": a word for reading.

    What it can reach

    • private-dataThe description's first sentence says "calendar": it reads calendars.
    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: true
    • openWorldHint: true
    • title: Unlocks where sources disagree
  • get_method_and_track_recordExplains 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 unlo…Reads text others writeNo findings

    Why it is in this group

    • The name "get_method_and_track_record" says "get": a word for reading.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: true
    • openWorldHint: true
    • title: Method and track record
  • get_onchain_checkWhat 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, outflow…Reads private dataReads text others writeNo findings

    Why it is in this group

    • The name "get_onchain_check" says "get": a word for reading.

    What it can reach

    • private-dataThe description's first sentence says "document": it reads documents.
    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: true
    • openWorldHint: true
    • title: Locked-token wallets on-chain
  • get_token_unlocksAll 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…Reads text others writeNo findings

    Why it is in this group

    • The name "get_token_unlocks" says "get": a word for reading.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: true
    • openWorldHint: true
    • title: Unlocks for one token
  • get_upcoming_unlocksCalendar of scheduled crypto token unlocks in the next N days (up to 60), each rated strong / medium / small by size relative to circulating supply.Reads private dataReads text others writeNo findings

    Why it is in this group

    • The name "get_upcoming_unlocks" says "get": a word for reading.

    What it can reach

    • private-dataThe description's first sentence says "calendar": it reads calendars.
    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: true
    • openWorldHint: true
    • title: Upcoming token unlocks

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

No private-data, untrusted-input, outbound path in this server alone: no tool is tagged outbound.

Reads private data3
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write7
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out0
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

Tools listed without sign-in

Looked at Nov 18, 2026, 16:24 UTC, unchanged since Nov 18, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
yes
HTTP status of an anonymous initialize
200
tools/list served without credentials
yes
Tools that change things, listed without credentials
1
Protocol version
2025-06-18
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
not observed
Authorization servers
not observed
Legacy HTTP+SSE transport
no
Dynamic client registration
not observed
Client ID metadata documents
not observed
  • WarnThe whole server

    The endpoint served tools/list without credentials, and the list has 1 tool that changes things (1 write). Whether a call also works without credentials was not tested: tools are never called.

    Matched text

    https://unlockpulse-mcp.unlockpulse.workers.dev/mcp: tools/list returned 7 tools to an anonymous client, including check_portfolio (write)

    What this check looks for

Posture changes

  1. Nov 18, 2026
    • Tools that change things, listed without credentials: 0 to 1

Findings

Matches of fixed checks, with the text they matched.

No check matched anything in these tool definitions. That is not a safety guarantee.

History

Changes to its tool definitions and to its remote endpoint, newest first.

  1. PostureRemote posture changed. Tools that change things, listed without credentials: 0 -> 1.View diff
    • Tools that change things, listed without credentials: 0 to 1
  2. Tools2 added, 3 changed.+2 added~3 changedView diff
  3. Tools1 changed.~1 changedView diff
  4. Tools1 changed.~1 changedView diff
  5. Tools1 added, 4 changed.+1 added~4 changedView diff
  6. Tools1 added.+1 addedView diff

Install

Pinned to version 1.11.0. Values in angle brackets are yours to fill in.

claude mcp add --transport http unlockpulse https://unlockpulse-mcp.unlockpulse.workers.dev/mcp
claude mcp add --transport http unlockpulse https://unlockpulse-mcp.unlockpulse.workers.dev/mcp

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__unlockpulse__get_upcoming_unlocks",
      "mcp__unlockpulse__get_token_unlocks",
      "mcp__unlockpulse__get_onchain_check",
      "mcp__unlockpulse__get_disputed_unlocks",
      "mcp__unlockpulse__get_method_and_track_record",
      "mcp__unlockpulse__get_dataset_info"
    ],
    "ask": [
      "mcp__unlockpulse__check_portfolio"
    ],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as unlockpulse. Review it before you use it.

Capability tags behind 7 rules
  • mcp__unlockpulse__get_upcoming_unlocks private-data, untrusted-input
  • mcp__unlockpulse__get_token_unlocks untrusted-input
  • mcp__unlockpulse__get_onchain_check private-data, untrusted-input
  • mcp__unlockpulse__get_disputed_unlocks private-data, untrusted-input
  • mcp__unlockpulse__check_portfolio untrusted-input
  • mcp__unlockpulse__get_method_and_track_record untrusted-input
  • mcp__unlockpulse__get_dataset_info untrusted-input

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://radar.anlyon.com/api/v1/servers/io.github.Billibo6/unlockpulse/verify?hash=63bff8e7260638b70974cb3f5e551f49ae0db82b54acc7e149a93fa35b496c77" | jq -e '.changed == false'

Pinned hash 63bff8e72606, from Nov 17, 2026, 04:18 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/io.github.Billibo6/unlockpulse/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for io.github.Billibo6/unlockpulse
[![Anlyon Radar](https://radar.anlyon.com/badge/io.github.Billibo6/unlockpulse.svg)](https://radar.anlyon.com/servers/io.github.Billibo6/unlockpulse)

Source: MCP Registry · repository. Synced Nov 17, 2026, 05:17 UTC.

Unlock Pulse MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the Unlock Pulse MCP server safe?

No scan can promise that. What its definitions show: 7 tools, 1 of which can change, send or delete something, and 0 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.

Can the Unlock Pulse MCP server delete data?

No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.

Can the Unlock Pulse MCP server do things that cannot be undone?

No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.

What tools does the Unlock Pulse MCP server have?

7 tools: 1 write, 6 read. check_portfolio, get_upcoming_unlocks, get_token_unlocks, get_onchain_check, get_disputed_unlocks, get_method_and_track_record and get_dataset_info.

Does the Unlock Pulse MCP server need sign-in or OAuth?

Its remote endpoint listed its tools to an anonymous client, without sign-in.

Does the Unlock Pulse MCP server send data to outside services?

None of its tools sends, posts or publishes, or takes a recipient, channel or URL.

Has the Unlock Pulse MCP server changed its tools?

Yes, 5 times since Anlyon Radar started tracking it, most recently on Nov 17, 2026. Every change is on this page and in its Atom feed.