HistoryTimeline

What HistoryTimeline is for

A genuinely global world-history reference — not just a Western-centric timeline — for questions like "what happened in the 15th century", "list events in Africa between 1000 and 1500", "what caused the fall of the Western Roman Empire", answered locally from a hand-curated dataset of roughly 90 events and 6 eras spanning Africa, the Americas, East Asia, South Asia, Southeast Asia, the Middle East/West Asia, Europe, and Oceania.

What it does

era_reference lists the six eras this connector uses (ancient, classical, medieval, early_modern, modern, contemporary) with their year ranges and a global summary, or gives one era's detail and sample events. timeline_query returns every event whose year falls within an inclusive date range you give it — using negative integers for BCE years (so 3100 BCE is -3100) and positive integers for CE years — optionally filtered by region or tag. century_browser is an "on this century" browser: give it a century number (and bce: true for a BCE century) and it resolves the year range and lists everything in it. turning_point gives cause-and-effect notes for ten major historical turning points — the fall of Rome, the fall of Constantinople, the Columbian Exchange, the printing press, the Industrial Revolution, the French Revolution, World War I, decolonization, the end of the Cold War, and the Mongol Empire — each with hand-curated causes, effects, and a note on where historians' interpretations genuinely differ.

Even-handedness on contested history

Several events and turning points in this dataset touch subjects where historians disagree, or where a single popular narrative oversimplifies a contested question — the causes of Rome's fall, the scale and mechanisms of Indigenous depopulation after 1492, the "war guilt" question for World War I, the drivers of the Industrial Revolution, and the interpretation of decolonization and the end of the Cold War, among others. Every turning point entry explicitly names where historians' accounts diverge, rather than presenting one school of thought as settled fact. Dates before reliable written record-keeping are marked "c." (circa) to signal they are scholarly estimates, not precise figures.

What it is not

Not a substitute for primary sources or academic scholarship — this is a study aid and overview built from hand-curated reference content, and the periodization into six eras is a simplifying convention for navigation, not a claim that history moves in clean breaks or that these boundaries are the only valid way to divide it. It never calls any outside service or database — everything is bundled with the server.

HistoryTimeline — Privacy Policy

Effective 28 September 2026. Unify Dynamics LLC ("we", "us"), Menlo Park, California.

What HistoryTimeline is. HistoryTimeline is a connector (an MCP server and REST API) that AI assistants and personal agents call on your behalf for a fully local, hand-curated world-history reference: an era reference, a date-range timeline query tool, an "on this century" browsing tool, and cause-and-effect notes for major historical turning points. You interact with your assistant; the assistant sends us only the arguments needed for that one tool call.

What we receive. The arguments of each tool call — which may include a date range, a century number, a region or tag filter, or a search string for a turning point — the technical headers needed to serve the request (an IP address or a client identifier supplied by the assistant, and a Pro API key if you have one), and standard server logs.

We do not store, log, or retain the content of your queries. Every tool reads from a reference dataset bundled with the server and returns a result computed from your arguments — nothing about a specific query is written to a database, written to a request log, cached, or used to train anything. Request bodies are not logged.

What we do not receive or store. We do not receive your conversation with the assistant or your name, and we do not build a profile from your queries: each request is answered independently. Rate-limit counters (a client identifier and timestamps, never the request content) are held in memory for at most 24 hours. Hosting-provider access logs, which contain IP addresses and request paths but not request bodies, are retained for up to 30 days for security and abuse prevention.

Sub-processors. None — there is no upstream call at all; every tool reads from a reference file bundled with the server. Hosting: Vercel (United States regions).

Legal bases and your rights. Our processing is necessary to provide the service you request through your assistant. Because we store no personal data beyond short-lived, content-free logs, requests to access, correct or delete personal data are usually satisfied automatically; you can still contact agent@connectorbay.com and we will respond within 30 days. We do not sell or share personal information and do not use your data to train models.

Children. HistoryTimeline is a general-audience educational reference service operated by the adult using the assistant.

Changes. We will post changes here with a new effective date.

HistoryTimeline — Terms of Service

Effective 28 September 2026. These terms govern use of the HistoryTimeline connector ("the Service") operated by Unify Dynamics LLC ("we", "us").

1. The Service. HistoryTimeline is a fully local, hand-curated world-history reference — an era reference, a date-range timeline query tool, an "on this century" browsing tool, and cause-and-effect notes for major historical turning points. It is accessed through an AI assistant or directly over MCP or HTTP.
2. An educational reference, not a scholarly or authoritative source. HistoryTimeline's content is hand-curated for broad global coverage and study purposes. It aims for even-handed treatment of contested historical interpretations and flags known points of scholarly disagreement, but it is not a substitute for primary sources, peer-reviewed scholarship, or a qualified historian, and dates before reliable written record-keeping are approximate.
3. No single-narrative claim on contested history. Where historians genuinely disagree — for example on the causes of major imperial collapses, the weighting of factors behind large-scale historical change, or the interpretation of recent and living-memory events — this Service presents multiple perspectives or flags the disagreement rather than asserting one account as definitive. Users should not treat any single entry as the final word on a contested question.
4. Your content. Query arguments you or your assistant submit (a date range, a search term) are used only to compute that one response.
5. Acceptable use. Automated use within the published rate limits is welcome.
6. Availability. The Service is provided "as is" without warranty. We may change, limit or discontinue it at any time.
7. Data. Our Privacy Policy describes what we process. In short: query arguments are used in memory for that one request and never stored or logged.
8. Pro keys. Optional Pro API keys are issued at our discretion, are personal to the holder, and may be revoked for abuse.
9. Liability. To the fullest extent permitted by law, Unify Dynamics LLC is not liable for any loss arising from use of or reliance on the Service, including reliance on its historical content for academic or professional work.
10. Governing law. California law; venue in San Mateo County, California.
11. Contact. Unify Dynamics LLC · agent@connectorbay.com · https://connectorbay.com/historytimeline

HistoryTimeline support

Email agent@connectorbay.com. We answer within two business days.

• MCP endpoint: https://historytimeline.connectorbay.com/mcp
• REST API: https://historytimeline.connectorbay.com/openapi.json
• Live status: https://historytimeline.connectorbay.com/health

When you report a problem, include the question you asked your agent, roughly when, and which agent you used (for example Claude, ChatGPT or Gemini). Never send us passwords, account numbers or ID numbers. HistoryTimeline never asks for them.