AI Incident Law MCP server

AI Incident Law

When an AI system causes harm, the legal and regulatory fallout ends up scattered across dockets, tribunal orders, and agency actions with no common index. AI Incident Law is an open, searchable corpus of those public matters, queryable by both humans and agents.

It ships as a standalone, dependency-free single-page application over a curated dataset of public matters involving AI-related incidents, failures, and resulting legal or regulatory action.

Who this is for

Compliance teams, legal counsel, AI governance leads, and researchers tracking how AI failures turn into legal and regulatory action.

What problem it solves

AI incidents and their legal consequences are scattered across public records with no structured, searchable index. AI Incident Law is an open corpus of public AI-related matters, queryable by humans and agents.

Canonical URL

https://aiincidentlaw.org/

Install as an MCP server

Configure your MCP-aware agent client (Claude Desktop, Cursor, etc.):

Replace: VERSION -> an npm-verified version from https://registry.npmjs.org/ai-incident-law and https://aiincidentlaw.org/design/publication-state.json. Customize

{
  "mcpServers": {
    "ai-incident-law": {
      "command": "npx",
      "args": ["-y", "ai-incident-law@VERSION"]
    }
  }
}

Replace VERSION with the version verified at the npm registry and in the canonical publication state. Do not infer a package's publication status from this source README. The server exposes eight recorded tools for querying the corpus by case attributes, anchored obligations, and verification freshness. It speaks MCP spec revision 2026-07-28 (stateless core, server/discover) and the legacy 2024-11-05 handshake in the same process. See docs/legal-graph.html for a cross-graph example pairing this with the EveryAILaw MCP.

Published packages, signed tags, GitHub Releases, and Official MCP Registry entries are independent delivery facts. The hosted publication state records those provider observations and exact artifact snapshots; it may be newer than this package's source documentation.

Part of the PAICE legal graph

AI Incident Law is one component of the PAICE legal graph (with EveryAILaw, PubLedge, and Obligation First). It is intentionally open: code under MIT, dataset under CC BY 4.0, commercial use permitted with attribution. The open siblings are funded by EveryAILaw Pro, the graph's single restricted layer; openness here is a deliberate PBC-charter choice. The canonical model is in the PAICE Foundation INTENT. Attribution: "AI Incident Law, PAICE.work PBC, CC BY 4.0".

Maintenance scope

Weekly source-link and record-age diagnostics identify review work; they do not reverify the corpus. A separate manual pilot observes five active matters and two official discovery indexes, preserves source failures and pending findings, and requires human review before any record or verification date changes. Source access remains incomplete. Independent missing-run monitoring and recovery email acceptance remain open. See the matter-monitor pilot for dated coverage evidence and methodology for the public boundary.

Repo layout

Shortened. The full README is on GitHub.