# Tokenomics Audit Desk — Unlock Calendar (remote · tokenomics-unlock-mcp.gtcclothing1.workers.dev)

Premium via x402: $1.00 full 20-token reconstruction - tokenomics-x402.gtcclothing1.workers.dev

- Trust score: 65/100 (medium)
- Change this week: +4
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- remote · `tokenomics-unlock-mcp.gtcclothing1.workers.dev`: 65/100 (this document), [markdown](https://verifymcp.io/servers/yungsuper16-eng-tokenomics-unlock-calendar/tokenomics-unlock-mcp.md), [page](https://verifymcp.io/servers/yungsuper16-eng-tokenomics-unlock-calendar/tokenomics-unlock-mcp)

## Channel facts

- Endpoint: `https://tokenomics-unlock-mcp.gtcclothing1.workers.dev/`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.3`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-05.

- **Endpoint Security**: 46/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation not fully verified: no authorisation is required to call this server, and 4 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.
  - HTTPS check failed: the endpoint is reachable over plaintext HTTP.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 78/100
  - AI-judged instruction clarity (excellent).
  - Tool/resource definitions use about 394 tokens (~98/item across 4 items; 4 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 30/100
  - Stability observed for 9 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### How do I install the Tokenomics Audit Desk — Unlock Calendar MCP server?

Tokenomics Audit Desk — Unlock Calendar is a hosted endpoint at https://tokenomics-unlock-mcp.gtcclothing1.workers.dev/, 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.

### Claude

```bash
claude mcp add --transport http yungsuper16-eng-tokenomics-unlock-calendar 'https://tokenomics-unlock-mcp.gtcclothing1.workers.dev/'
```

### Cursor

```json
{
  "mcpServers": {
    "yungsuper16-eng-tokenomics-unlock-calendar": {
      "url": "https://tokenomics-unlock-mcp.gtcclothing1.workers.dev/"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "yungsuper16-eng-tokenomics-unlock-calendar": {
      "type": "http",
      "url": "https://tokenomics-unlock-mcp.gtcclothing1.workers.dev/"
    }
  }
}
```

### Codex

```toml
[mcp_servers.yungsuper16-eng-tokenomics-unlock-calendar]
url = "https://tokenomics-unlock-mcp.gtcclothing1.workers.dev/"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "yungsuper16-eng-tokenomics-unlock-calendar": {
      "type": "remote",
      "url": "https://tokenomics-unlock-mcp.gtcclothing1.workers.dev/",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add yungsuper16-eng-tokenomics-unlock-calendar --url 'https://tokenomics-unlock-mcp.gtcclothing1.workers.dev/' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  yungsuper16-eng-tokenomics-unlock-calendar:
    url: "https://tokenomics-unlock-mcp.gtcclothing1.workers.dev/"
```

### Netclaw

```json
{
  "McpServers": {
    "yungsuper16-eng-tokenomics-unlock-calendar": {
      "Transport": "http",
      "Url": "https://tokenomics-unlock-mcp.gtcclothing1.workers.dev/"
    }
  }
}
```

### Vellum

```bash
assistant mcp add yungsuper16-eng-tokenomics-unlock-calendar -t streamable-http -u 'https://tokenomics-unlock-mcp.gtcclothing1.workers.dev/'
```

### Other

```json
{
  "mcpServers": {
    "yungsuper16-eng-tokenomics-unlock-calendar": {
      "type": "http",
      "url": "https://tokenomics-unlock-mcp.gtcclothing1.workers.dev/"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-05 (score 65, +1)

No change was recorded against any check on this day. Stability & Change Management went from 27 to 30. That category is still filling its 30-day observation window: 8 days of observed history at the previous scan, 9 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-03 (score 64, +1)

- [security] The server rewrote its instructions, which are the text every model session reads
- [security] Tool “dataset_info” rewrote its description, which is the text the model reads
- [functional regression] Schema quality: 73 → 98
- [functional] Schema quality: good → excellent

### 2026-11-02 (score 63, +1)

No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-31 (score 62, +1)

No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-28 (score 61, +1)

- [functional improvement] Stability: unverified → 0.03

### 2026-10-27 (score 60)

First indexed and scored.

## MCP tools (4)

### `list_upcoming_unlocks` (~82 tokens)

List upcoming token unlocks

List dated token unlock events from the Tokenomics Audit Desk 90-day unlock calendar, starting today (UTC), soonest first. Only events the desk holds verified figures for are included.

Input parameters:

- `days_ahead` (integer): How many days ahead of today to look (1-90).
- `limit` (integer): Maximum number of events to return.

### `get_token_unlocks` (~70 tokens)

Get unlocks for one token

Return every unlock event in the calendar for one token, matched case-insensitively against the token symbol (e.g. ENA, ZRO) or the project name (e.g. Ethena, LayerZero).

Input parameters:

- `token` (string, required): Token symbol or project name to look up.

### `get_unlock_calendar` (~69 tokens)

Get unlocks in a date range

Return all unlock events whose date falls inside an inclusive ISO date range (YYYY-MM-DD). Omit a bound to leave that side open.

Input parameters:

- `end_date` (string): Last date to include, YYYY-MM-DD.
- `start_date` (string): First date to include, YYYY-MM-DD.

### `dataset_info` (~71 tokens)

About this dataset

Provenance and coverage of the unlock dataset behind this server: version, coverage window, entry count, sources, license (MIT) and attribution. Also returns the premium x402 API for the full 20-token dataset ($1.00 via https://tokenomics-x402.gtcclothing1.workers.dev).

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/yungsuper16-eng-tokenomics-unlock-calendar/tokenomics-unlock-mcp#diagnostics

## Score history

- 2026-11-05: 65
- 2026-11-04: 64
- 2026-11-03: 64
- 2026-11-02: 63
- 2026-11-01: 62
- 2026-10-31: 62
- 2026-10-30: 61
- 2026-10-29: 61
- 2026-10-28: 61
- 2026-10-27: 60

## Common questions

### What is the Tokenomics Audit Desk — Unlock Calendar MCP server?

Tokenomics Audit Desk — Unlock Calendar is an MCP server listed in the public MCP registry as io.github.yungsuper16-eng/tokenomics-unlock-calendar. Premium via x402: $1.00 full 20-token reconstruction - tokenomics-x402.gtcclothing1.workers.dev. This page covers its hosted endpoint (https://tokenomics-unlock-mcp.gtcclothing1.workers.dev/).

### Is the Tokenomics Audit Desk — Unlock Calendar MCP server safe to use?

Tokenomics Audit Desk — Unlock Calendar scores 65 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 Tokenomics Audit Desk — Unlock Calendar MCP server expose?

Tokenomics Audit Desk — Unlock Calendar exposes 4 tools: list_upcoming_unlocks, get_token_unlocks, get_unlock_calendar, dataset_info. Their descriptions and schemas cost roughly 292 tokens of context every time the server is loaded.

### Does the Tokenomics Audit Desk — Unlock Calendar MCP server require authentication?

No. We connected to Tokenomics Audit Desk — Unlock Calendar without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the Tokenomics Audit Desk — Unlock Calendar MCP server still maintained?

Tokenomics Audit Desk — Unlock Calendar 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.

### What did VerifyMCP test on the Tokenomics Audit Desk — Unlock Calendar MCP server?

VerifyMCP ran 12 checks on Tokenomics Audit Desk — Unlock Calendar, covering TLS certificate, HTTPS, HSTS header, DNSSEC and 8 more. One item could not be completed, a gap on our side rather than a finding about Tokenomics Audit Desk — Unlock Calendar: Authorization. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.

## Links

- Remote endpoint: https://tokenomics-unlock-mcp.gtcclothing1.workers.dev/
- Repository: https://github.com/yungsuper16-eng/tokenomics-audit-desk
- Website: https://tokenomics-portfolio.pages.dev/
- Changelog RSS feed: https://verifymcp.io/servers/yungsuper16-eng-tokenomics-unlock-calendar/tokenomics-unlock-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/yungsuper16-eng-tokenomics-unlock-calendar/tokenomics-unlock-mcp/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/yungsuper16-eng-tokenomics-unlock-calendar/tokenomics-unlock-mcp.json
- HTML version of this page: https://verifymcp.io/servers/yungsuper16-eng-tokenomics-unlock-calendar/tokenomics-unlock-mcp