Source-backed timelines of long-running events in tech, the US economy and gaming. Every dated entry carries the page it was taken from and a verbatim quote, re-checked against that page before publication. Six read-only tools, no auth: list_timelines, get_timeline (with since= for what changed), get_entry (the quote and source to cite), get_party (one company, person or regulator across every timeline), search_entries and upcoming. Results carry entry URLs and name the outlet each quote came fr
Scored across 7 tools
Most tools have clearly distinct purposes: list_timelines for discovery, get_timeline/get_entry for retrieval, search_entries for keyword search, get_party for actor histories, ask for synthesized chains, and upcoming for scheduled events. Some overlap exists between get_party and search_entries (party filtering), and between ask and search_entries/get_timeline, but the descriptions explicitly guide when to use each.
Most tool names follow a clear verb_noun pattern (get_entry, get_party, get_timeline, list_timelines, search_entries). The exceptions are ask and upcoming, which are still readable and intuitive, so the set is mostly consistent with only minor deviations.
Seven tools is well-scoped for a read-only research server covering timelines, entries, parties, search, synthesis, and upcoming events. Each tool earns its place without redundancy or bloat.
The surface covers discovery, deep retrieval, cross-timeline parties, keyword search, synthesized answers, and future events, which is strong for a read-only domain. A minor gap is the lack of a direct way to list or search parties independently; party IDs must first be discovered via entries or timelines.
Answer a why/how question as a chain: an ordered set of dated, sourced entries from the timelines with one line on why each led to the next, written by the editor rather than generated. Returns the best-matching chain with every step's entry (URL, date, summary, sources), or, when no chain fits, the questions that do exist and how to research the answer with the other tools.
Inputs: question (required), since.
One dated entry in full: its summary, type, the parties it names, every source with the outlet, the publication date and the verbatim quote it was read from, plus the relations and cross-timeline links it takes part in. Use it after search_entries or get_timeline has found an entry and you need the exact wording and source URL to cite. Entry ids are unique within a timeline, not across the site, so pass the slug the entry came from.
Inputs: id (required), slug (required).
Everything the site records about one company, person or regulator across every timeline: its role on each, the parties it most often appears alongside, and every dated entry that names it, newest first, with sources. Use it instead of search_entries when you want one actor's whole history rather than a keyword match. Returns at most limit entries, with total_entries saying how many exist; a party is named when the editors listed it among an entry's parties, not merely when the name appears in the text.
Inputs: id (required), limit.
One timeline in full: TL;DR, dated entries newest first with sources and quotes, relations between entries, links to other timelines, what to watch next and open questions. Pass since=YYYY-MM-DD to get only entries dated on or after that day (what changed recently).
Inputs: slug (required), limit, since.
Every timeline on the site with its topic, tags, entry count, date range, last update and a short summary. Start here to find the slug for get_timeline.
Inputs: no named parameters.
Find dated entries across every timeline by keywords, party id, timeline slug and date range. Every keyword must match (title, summary, party or timeline name); results are ranked, newest first among equals. Returns the entry text and url; call get_entry for quotes and sources.
Inputs: to, from, limit, party, +2 more.
Scheduled dates the timelines are watching — earnings, rulings, launches, rule deadlines — each with why it matters, the timeline it belongs to and a source where one exists. Use it to answer what happens next across the site, rather than reading each timeline for its own catalysts. Returns the dates from today to the horizon, oldest first, echoing back today and horizon; a date known only to the month carries precision=month and is matched on the month.
Inputs: days, timeline.
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
Add one secure layer between your agents and this server.