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
Available components
Last scanned (5 hours ago)
Scores higher than 45% 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 Security46
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- 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. See how to fix → View diagnostics → Unverified
- HTTPS check failed: the endpoint is reachable over plaintext HTTP. See how to fix → View diagnostics → Fail
- 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 Usability78
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 394 tokens (~98/item across 4 items; 4 tools + 0 resources), lean.Pass
- 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 Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Checks we ran (12)
- TLS certificate
- HTTPS
- HSTS header
- DNSSEC
- Transport
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Checks we could not complete (1)
These are gaps on our side, not findings about this hosted endpoint. We only credit what we can confirm, so a category made up entirely of them scores 0.
- Authorization in Endpoint SecurityAuthorisation 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.
Does not apply to this hosted endpoint (2)
- Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
- Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
The score does not measure everything. What the score does not measure →
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.
- 5 Nov 26 +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.
- 3 Nov 26 +1
- 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 security
- Schema quality: 73 → 98 ▼ functional
- Schema quality: good → excellent functional
- 2 Nov 26 +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.
- 31 Oct 26 +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.
- 28 Oct 26 +1
- Stability: unverified → 0.03 ▲ functional
- 27 Oct 26 60
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://tokenomics-unlock-mcp.gtcclothing1.workers.dev/
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=gtcclothing1.workers.dev | CN=YE2,O=Let's Encrypt,C=US | 4 Oct 2026 | 2 Jan 2027 | ECDSA 256 | ECDSA-SHA384 | 68df5dc675fb733368c8271a3b35aca8d5f |
| SANs: *.gtcclothing1.workers.dev, gtcclothing1.workers.dev | ||||||
| CN=YE2,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 4df3b15dd6c0784c507cd37b58e6f115 |
| 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 tokenomics-unlock-mcp.gtcclothing1.workers.dev. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| dev. | DS published | 60074 | 8 | Verified |
| workers.dev. | No DS | 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://tokenomics-unlock-mcp.gtcclothing1.workers.dev/ | Verified | 200 | |
| http (plaintext) | http://tokenomics-unlock-mcp.gtcclothing1.workers.dev/ | Served over HTTP | 200 |
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 →
dataset_info About this dataset ~71
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).
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_token_unlocks Get unlocks for one token ~70
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).
| Name | Type | Req | Description |
|---|---|---|---|
| token | string | yes | Token symbol or project name to look up. |
No output schema declared.
No examples provided.
get_unlock_calendar Get unlocks in a date range ~69
Return all unlock events whose date falls inside an inclusive ISO date range (YYYY-MM-DD). Omit a bound to leave that side open.
| Name | Type | Req | Description |
|---|---|---|---|
| end_date | string | – | Last date to include, YYYY-MM-DD. |
| start_date | string | – | First date to include, YYYY-MM-DD. |
No output schema declared.
No examples provided.
list_upcoming_unlocks List upcoming token unlocks ~82
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.
| Name | Type | Req | Description |
|---|---|---|---|
| days_ahead | integer | – | How many days ahead of today to look (1-90). |
| limit | integer | – | Maximum number of events to return. |
No output schema declared.
No examples provided.
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.
remote · tokenomics-unlock-mcp.gtcclothing1.workers.dev
claude mcp add --transport http yungsuper16-eng-tokenomics-unlock-calendar 'https://tokenomics-unlock-mcp.gtcclothing1.workers.dev/'
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.