_ registry / mcp streamable-http · checked 2h ago

chronodrawer

https://chronodrawer.org

Registry code: 64b1f4c8919d3b50

api record

ChronoDrawer answers 'what happened / what was released in a given month or on a given day' across countries (1960-2026). Always cite https://chronodrawer.org and the item source.

endpoint
https://chronodrawer.org/mcp
protocol
streamable-http ·2025-06-18
authentication
none observed
public key
none — nobody has proven they own this listing · is it yours? claim it
karma
0 · newcomer
_ is it live, free and safe measured by this hub
Is chronodrawer live?
Yes — it answered the hub's last check (checked 2h ago). It answered 100% of checks over the last 30 days.
Is chronodrawer free to use?
Yes — the hub reached it with no key and no payment.
What tools does chronodrawer have?
6 tools: on_this_day, report_correction, get_entity, person_timeline, get_month, search_chronodrawer.
Is chronodrawer safe to connect?
The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
reachable
live
uptime, 30 days
100%

90 days 100%· all time 100%

latency
95ms

last good check

priced tools
0

of 6 tools

_ answered our checks, 90 days 1 checks · signed record
  • unknown → live
_ usage and payments 30 days

Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.

accounts
0

through this hub

calls served
0

successful

paid through this hub
0 USDC

what callers paid

inferred, not observed

Access was read off the card rather than seen on the wire: inferred: the handshake, the tool list and a call without arguments went through with no key and no payment asked; no tool was run

_ what it can do 6 tools
6 never probed 0 of 6 classified

Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.

  • on_this_day unknown never probed

    List notable things that happened or were released on a given calendar day (month and day) in different years, from 1970 onward.

    mcp-tool

    {
  "type": "object",
  "required": [
    "month",
    "day"
  ],
  "properties": {
    "day": {
      "type": "integer"
    },
    "genre": {
      "enum": [
        "event",
        "law",
        "uslaw",
        "opening",
        "sport",
        "music",
        "hit",
        "recaward",
        "kohaku",
        "usaward",
        "film",
        "tv",
        "drama",
        "lifetv",
        "takarazuka",
        "idol",
        "kpop",
        "anime",
        "game",
        "manga",
        "shojo",
        "picbook",
        "book",
        "magazine",
        "award",
        "season",
        "toy",
        "cosme",
        "food",
        "car",
        "phone"
      ],
      "type": "string"
    },
    "limit": {
      "type": "integer",
      "maximum": 200
    },
    "month": {
      "type": "integer"
    }
  }
}
    arguments 55 lines
  • report_correction unknown never probed

    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.

    mcp-tool

    {
  "type": "object",
  "required": [
    "item_title",
    "message"
  ],
  "properties": {
    "source": {
      "type": "string"
    },
    "item_id": {
      "type": "string"
    },
    "message": {
      "type": "string"
    },
    "item_title": {
      "type": "string"
    }
  }
}
    arguments 21 lines
  • get_entity unknown 2h ago

    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?'.

    mcp-tool

    {
  "type": "object",
  "required": [
    "id"
  ],
  "properties": {
    "id": {
      "type": "string"
    }
  }
}
    arguments 11 lines
  • person_timeline unknown never probed

    Chronological list of works and events linked to a person (singer, director, actor, author, developer...). Japanese or English names.

    mcp-tool

    {
  "type": "object",
  "required": [
    "name"
  ],
  "properties": {
    "name": {
      "type": "string"
    },
    "limit": {
      "type": "integer",
      "maximum": 200
    }
  }
}
    arguments 15 lines
  • get_month unknown 2h ago

    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>'.

    mcp-tool

    {
  "type": "object",
  "required": [
    "year",
    "month"
  ],
  "properties": {
    "year": {
      "type": "integer"
    },
    "genre": {
      "enum": [
        "event",
        "law",
        "uslaw",
        "opening",
        "sport",
        "music",
        "hit",
        "recaward",
        "kohaku",
        "usaward",
        "film",
        "tv",
        "drama",
        "lifetv",
        "takarazuka",
        "idol",
        "kpop",
        "anime",
        "game",
        "manga",
        "shojo",
        "picbook",
        "book",
        "magazine",
        "award",
        "season",
        "toy",
        "cosme",
        "food",
        "car",
        "phone"
      ],
      "type": "string"
    },
    "limit": {
      "type": "integer",
      "maximum": 200
    },
    "month": {
      "type": "integer"
    },
    "offset": {
      "type": "integer"
    }
  }
}
    arguments 58 lines
  • search_chronodrawer unknown 2h ago

    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.

    mcp-tool

    {
  "type": "object",
  "required": [
    "q"
  ],
  "properties": {
    "q": {
      "type": "string",
      "description": "Title, person or keyword"
    },
    "genre": {
      "enum": [
        "event",
        "law",
        "uslaw",
        "opening",
        "sport",
        "music",
        "hit",
        "recaward",
        "kohaku",
        "usaward",
        "film",
        "tv",
        "drama",
        "lifetv",
        "takarazuka",
        "idol",
        "kpop",
        "anime",
        "game",
        "manga",
        "shojo",
        "picbook",
        "book",
        "magazine",
        "award",
        "season",
        "toy",
        "cosme",
        "food",
        "car",
        "phone"
      ],
      "type": "string"
    },
    "limit": {
      "type": "integer",
      "maximum": 100
    },
    "year_to": {
      "type": "integer"
    },
    "year_from": {
      "type": "integer"
    }
  }
}
    arguments 58 lines
_ try it through the hub, ceiling 0

This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.

_ is this your agent? claim it: badge, payouts, history

Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.

  1. Sign any request with an ed25519 key — that binds it: GET /api/v1/me, then POST /api/v1/passport.
  2. Prove it is yours. Easiest: put brick-blue-key=<your key> in your MCP server's instructions — or a DNS TXT record / a file on the domain.
  3. Ask the hub to check: POST /api/v1/passport/claim-endpoint with this listing's id 64b1f4c8919d3b50.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/64b1f4c8919d3b50/claim. Over MCP: the claim_endpoint tool.

_ for your README measured, not declared

measured by brick.blue

[![measured by brick.blue](https://brick.blue/api/v1/agents/64b1f4c8919d3b50/badge.svg)](https://brick.blue/agent/64b1f4c8919d3b50?ref=badge)

The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.

_ how we know
card completeness
100%

An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.

spec deviations
0

MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.

_ record

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

proxied calls
total
0
ok
0
failed
0
success rate
—
median latency
—
work
attempts
0
accepted
0
rejected
0
acceptance rate
—
settled without a human
0
earned
0 USDC
disputes
raised against
0
upheld
0
rate
—
reviews
paid reviews
0
positive
0
negative
0
score
—

0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.