ChronoKey
REMOTE · BOT.CHRONOKEY.WORKERS.DEV
MCP tools: timestamps, UUID v4, gas prices, domain WHOIS, text extraction, and persistent memory.
Available components
Last scanned (20 hours ago)
Scores higher than 12% of remote servers
Reachable. Last reached 22 Oct 2026.
Category Memory and Knowledge
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 connect, but we couldn't read the whole tool list to see what that exposes. View diagnostics → Unverified
- HTTPS enforcement could not be verified: the plaintext port answered with HTTP 402, 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 Usability0
- Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.Unverified
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
- Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Tool Safety0
- Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Capabilities0
- Capabilities not yet verified: we couldn't read the endpoint's capabilities.Unverified
Unverified: 5 categories
Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.
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.
- 1 Oct 26 −37
- Endpoint reachability: reachable → not serving MCP ▼ security
- Stability: fail → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- Authorization: partial → unverified ▼ security
- Capabilities: fail → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- First check of Schema quality: unverified functional
- 29 Sept 26 +4
- Stability: 0.03 → fail ▼ security
- Tool “domain.intel” was removed ▼ security
- Tool “extract.and.fetch” was removed ▼ security
- Tool “extract.and.summarize” was removed ▼ security
- Tool “extract.confirm” was removed ▼ security
- Tool “extract.verified” was removed ▼ security
- Tool “gas.price” was removed ▼ security
- Tool “health” was removed ▼ security
- Tool “memory.recall” was removed ▼ security
- Tool “memory.search” was removed ▼ security
- Tool “memory.store” was removed ▼ security
- Tool “subscribe” was removed ▼ security
- Tool “subscription.status” was removed ▼ security
- Tool “text.structure” was removed ▼ security
- Tool “text.structure.deep” was removed ▼ security
- Tool “timestamp” was removed ▼ security
- Tool “uuid” was removed ▼ security
- Authorization: unverified → partial ▲ security
- The server rewrote its instructions, which are the text every model session reads security
- The server changed its declared name: ChronoKey → chronokey security
- MCP protocol: pass → fail ▼ functional
- Schema quality: 63 → 31 ▲ functional
- MCP protocol version: 2025-11-25 → 2025-06-18 functional
- Server version: 2.1.0 → 2.3.0 functional
- New tool “extractTextFromUrl” functional
- New tool “generateUUID” functional
- New tool “getDomainIntel” functional
- New tool “getGasPrice” functional
- New tool “getTimestamp” functional
- New tool “memoryRetrieve” functional
- New tool “memoryStore” functional
- 28 Sept 26 +1
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 27 Sept 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 22 Oct 2026 · Probed https://bot.chronokey.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=chronokey.workers.dev | CN=YE1,O=Let's Encrypt,C=US | 27 Sept 2026 | 26 Dec 2026 | ECDSA 256 | ECDSA-SHA384 | 5cf64a7745568d2d2711fb26759018b89dc |
| SANs: *.chronokey.workers.dev, chronokey.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 bot.chronokey.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 |
| Header | Value |
|---|---|
| x-content-type-options | nosniff |
| x-frame-options | DENY |
| referrer-policy | strict-origin-when-cross-origin |
| permissions-policy | geolocation=(), microphone=() |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://bot.chronokey.workers.dev/mcp | Verified | 200 | |
| http (plaintext) | http://bot.chronokey.workers.dev/mcp | Inconclusive | 402 |
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 →
extractTextFromUrl ~35
Fetches a URL and returns clean readable text.
| Name | Type | Req | Description |
|---|---|---|---|
| url | string | yes | Absolute URL to fetch and extract text from |
No output schema declared.
No examples provided.
generateUUID ~15
Generates a UUID v4 identifier.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
getDomainIntel ~38
Returns domain intelligence and WHOIS data for a domain.
| Name | Type | Req | Description |
|---|---|---|---|
| domain | string | yes | Domain name to look up, e.g. example.com |
No output schema declared.
No examples provided.
getGasPrice ~19
Returns the current ethereum gas price in gwei.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
getTimestamp ~24
Returns the current unix timestamp in milliseconds and seconds, plus ISO 8601.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
memoryRetrieve ~28
Retrieves a previously stored memory value by key.
| Name | Type | Req | Description |
|---|---|---|---|
| key | string | yes | Memory key to retrieve |
No output schema declared.
No examples provided.
memoryStore ~36
Stores a key-value fact in persistent memory.
| Name | Type | Req | Description |
|---|---|---|---|
| key | string | yes | Memory key |
| value | string | yes | Value to store |
No output schema declared.
No examples provided.
How do I install the ChronoKey MCP server?
ChronoKey is a hosted endpoint at https://bot.chronokey.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 · bot.chronokey.workers.dev
claude mcp add --transport http dyln01-chronokey 'https://bot.chronokey.workers.dev/mcp'
What is the ChronoKey MCP server?
ChronoKey is an MCP server listed in the public MCP registry as io.github.Dyln01/chronokey. MCP tools: timestamps, UUID v4, gas prices, domain WHOIS, text extraction, and persistent memory. This page covers its hosted endpoint (https://bot.chronokey.workers.dev/mcp).
Is the ChronoKey MCP server safe to use?
ChronoKey scores 28 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 ChronoKey MCP server expose?
ChronoKey exposes 7 tools: getTimestamp, generateUUID, getGasPrice, getDomainIntel, extractTextFromUrl, and 2 more. Their descriptions and schemas cost roughly 195 tokens of context every time the server is loaded.
Does the ChronoKey MCP server require authentication?
No. We connected to ChronoKey without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the ChronoKey MCP server still maintained?
ChronoKey is still listed as active in the MCP registry. We last reached this channel on 22 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.