ChronoDrawer
REMOTE · CHRONODRAWER.ORG
What happened and was released in a given month or day, across countries (1960-2026), with sources.
Available components
Last scanned (10 hours ago)
Scores higher than 43% of remote servers
Reachable. Last reached 5 Nov 2026.
Category Education and Research
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 6 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 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 Usability62
- AI-judged instruction clarity (fair).Partial
- Tool/resource definitions use about 569 tokens (~94/item across 6 items; 6 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management13
- Stability observed for 4 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage68
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 5% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 6 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 7 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 (11)
- TLS certificate
- HSTS header
- DNSSEC
- Transport
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Checks we could not complete (2)
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 6 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 in Endpoint SecurityHTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement.
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 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.
- 3 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.
- 2 Nov 26 0
- Stability: unverified → 0.03 ▲ functional
- 1 Nov 26 55
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://chronodrawer.org/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=chronodrawer.org | CN=WE1,O=Google Trust Services,C=US | 2 Oct 2026 | 31 Dec 2026 | ECDSA 256 | ECDSA-SHA256 | 5b1ef4db9d15f3e90e6a8f820f055f9c |
| SANs: chronodrawer.org, www.chronodrawer.org, *.www.chronodrawer.org | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of chronodrawer.org. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| org. | DS published | 725, 26974 | 8, 8 | Verified |
| chronodrawer.org. | 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://chronodrawer.org/mcp | Verified | 200 | |
| http (plaintext) | http://chronodrawer.org/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_entity Dates by country for a work or event ~60
Given a Wikidata ID (e.g. Q332368), return the release/occurrence dates in each country known to ChronoDrawer, with links. Answers questions like 'when was this film released in Japan?'.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | – |
No output schema declared.
No examples provided.
get_month What happened in a month ~93
List the most notable items for a given year and month (optionally one genre), across countries, e.g. year=1985, month=8. Use this to answer 'what happened / what came out in <month> <year>'.
| Name | Type | Req | Description |
|---|---|---|---|
| genre | string | – | – |
| limit | integer | – | – |
| month | integer | yes | – |
| offset | integer | – | – |
| year | integer | yes | – |
No output schema declared.
No examples provided.
on_this_day On this day ~65
List notable things that happened or were released on a given calendar day (month and day) in different years, from 1970 onward.
| Name | Type | Req | Description |
|---|---|---|---|
| day | integer | yes | – |
| genre | string | – | – |
| limit | integer | – | – |
| month | integer | yes | – |
No output schema declared.
No examples provided.
person_timeline Timeline of a person ~51
Chronological list of works and events linked to a person (singer, director, actor, author, developer...). Japanese or English names.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | – |
| name | string | yes | – |
No output schema declared.
No examples provided.
report_correction Report a correction ~79
Report a factual error or missing information in ChronoDrawer (e.g. a wrong date). A human reviews it before anything changes. Include the item title, what is wrong, and a source.
| Name | Type | Req | Description |
|---|---|---|---|
| item_id | string | – | – |
| item_title | string | yes | – |
| message | string | yes | – |
| source | string | – | – |
No output schema declared.
No examples provided.
search_chronodrawer Search ChronoDrawer ~175
Search ChronoDrawer, a month-by-month database (1960-2026) of what happened and what was released around the world: events, Japanese laws, openings, sports, music, films, TV, anime, games, manga, books, magazines, prizes, cars, mobile phones. Matches titles, English titles and people (artists, directors, authors). Japanese and English queries both work; person_match is true when one of the item's people is exactly the query. Returns dates (YYYY-MM-DD, or YYYY-MM when only the month is known), countries, date type and a source URL.
| Name | Type | Req | Description |
|---|---|---|---|
| genre | string | – | – |
| limit | integer | – | – |
| q | string | yes | Title, person or keyword |
| year_from | integer | – | – |
| year_to | integer | – | – |
No output schema declared.
No examples provided.
How do I install the ChronoDrawer MCP server?
ChronoDrawer is a hosted endpoint at https://chronodrawer.org/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 · chronodrawer.org
claude mcp add --transport http org-chronodrawer-chronodrawer 'https://chronodrawer.org/mcp'
What is the ChronoDrawer MCP server?
ChronoDrawer is an MCP server listed in the public MCP registry as org.chronodrawer/chronodrawer. What happened and was released in a given month or day, across countries (1960-2026), with sources. This page covers its hosted endpoint (https://chronodrawer.org/mcp).
Is the ChronoDrawer MCP server safe to use?
ChronoDrawer scores 57 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 ChronoDrawer MCP server expose?
ChronoDrawer exposes 6 tools: search_chronodrawer, get_month, on_this_day, person_timeline, get_entity, report_correction. Their descriptions and schemas cost roughly 523 tokens of context every time the server is loaded.
Does the ChronoDrawer MCP server require authentication?
No. We connected to ChronoDrawer without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the ChronoDrawer MCP server still maintained?
ChronoDrawer 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 ChronoDrawer MCP server?
VerifyMCP ran 11 checks on ChronoDrawer, covering TLS certificate, HSTS header, DNSSEC, Transport and 7 more. 2 items could not be completed, a gap on our side rather than a finding about ChronoDrawer: Authorization and HTTPS. 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.