TwinEthos Lite MCP Server

Binding AI-law obligations that start applying soon, soonest first, with citation, official link and the guard in one sentence. When to use: someone asks what is coming, what to prepare for, or which AI laws take effect next year. For dates already passed, use recently_in_force. Features and markets narrow the list (each left out covers everything); within_days sets how far ahead to look. Each entry's guard is the change to make in the application (a notice, a check, a human review step). Dates can change; returns at most 10, and `total` says how many there are. Limits: informational data, not legal advice.

One rule in plain terms: what it requires (TwinEthos's summary), who it applies to and the uses it excludes, its dates, the exact citations with their official links, and the guard to add in one sentence (a guard is the change to make in the application's code or settings, such as a notice, a check or a human review step, that addresses the rule's duty). When to use: after search_laws, coming_into_force, recently_in_force or plan_guards, with a rule_id one of them returned, or when someone names a rule id. An unknown id returns an error naming search_laws. It never returns the official text itself. Limits: informational data, not legal advice.

Find the AI-law rules (EU AI Act, US state AI laws, China, Korea and other markets) that apply to an AI feature in a market, each with its cited provision and official link. When to use: someone asks which laws, regulations or standards apply to what they are building, or where a kind of AI feature is regulated (chatbot disclosure, hiring and employment decisions, credit or insurance decisions, deepfakes and digital replicas, companion chatbots and minors, AI-generated content labels, training data). The filters combine: a rule must cover one of the markets and one of the patterns given, and match the words if any are given; each filter left out matches everything. Returns at most 10 rules, most relevant first (the words matched, then the rules specific to the features, then binding law in force), each with its lane, citation, official link, applies-from date and its page in the TwinEthos explorer. It does not sort by date: use coming_into_force or recently_in_force for dates. Limits: informational data, not legal advice.

The few guards that address the most rules for these AI features and markets, ranked: each guard in one sentence (a guard is a change to make in the application's code or settings, such as a notice, a check or a human review step), how many rules it addresses by lane, where binding law on it applies, and up to three example rule ids. When to use: someone asks what to build first, or how to cover several markets at once. Ranked by the markets with binding law in force, then law coming, then rules addressed. Leave out features or markets to rank over all of them. Returns at most 5 guards; pass an example rule_id to explain_rule for detail. Limits: informational data, not legal advice.

Binding AI-law obligations that started applying recently, newest first, with citation, official link and the guard in one sentence. When to use: someone asks what took effect recently, when the most recent AI law in a market started applying, or what changed this year. For dates ahead, use coming_into_force. Features and markets narrow the list (each left out covers everything); within_days sets how far back to look. Each date is when a duty started applying, not when the law was enacted; a later phase of a law already in force is marked as one. Each entry's guard is the change to make in the application (a notice, a check, a human review step). Returns at most 10, and `total` says how many there are. Limits: informational data, not legal advice.