AI Incident Law
NPM · AI-INCIDENT-LAW · SCANNED SEP 21
Public-record corpus of AI litigation, regulation, and enforcement, anchored to EveryAILaw.
Available components
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security100
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- No production dependencies, so there is no dependency health to assess. View diagnostics → Pass
Provenance & Transparency48
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 8 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability80
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 898 tokens (~112/item across 8 items; 8 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management83
- Stability observed for 25 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 8 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 9 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
How do I install the AI Incident Law MCP server?
AI Incident Law runs locally as an npm package, launched with npx -y ai-incident-law. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · ai-incident-law
claude mcp add snapsynapse-ai-incident-law -- npx -y ai-incident-law
{
"mcpServers": {
"snapsynapse-ai-incident-law": {
"command": "npx",
"args": [
"-y",
"ai-incident-law"
]
}
}
} {
"servers": {
"snapsynapse-ai-incident-law": {
"command": "npx",
"args": [
"-y",
"ai-incident-law"
]
}
}
} codex mcp add snapsynapse-ai-incident-law -- npx -y ai-incident-law
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"snapsynapse-ai-incident-law": {
"type": "local",
"command": [
"npx",
"-y",
"ai-incident-law"
],
"enabled": true
}
}
} openclaw mcp add snapsynapse-ai-incident-law --command npx --arg -y --arg ai-incident-law
mcp_servers:
snapsynapse-ai-incident-law:
command: "npx"
args: ["-y", "ai-incident-law"] {
"McpServers": {
"snapsynapse-ai-incident-law": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"ai-incident-law"
]
}
}
} assistant mcp add snapsynapse-ai-incident-law -t stdio -c npx -a -y ai-incident-law
{
"mcpServers": {
"snapsynapse-ai-incident-law": {
"command": "npx",
"args": [
"-y",
"ai-incident-law"
]
}
}
} Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 21 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.
- 19 Sept 26 −3
- Stability: pass → 0.77 functional
- 18 Sept 26 0
- Stability: 0.97 → pass security
- 17 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 15 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.
- 13 Sept 26 +16
- Malware scan: unverified → pass ▲ security
- 12 Sept 26 −17
- Stability: pass → unverified ▼ security
- Malware scan: pass → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- Schema quality: 72 → 112 ▼ functional
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- Stability: pass → 0.80 functional
- Package version: 0.4.1 → 0.4.3 functional
- 11 Sept 26 0
- Stability: 0.97 → pass security
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 21 Sept 2026 · Analysed npm/ai-incident-law@0.4.3
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Background: How many MCP packages publish verified provenance →
Dependencies 0 packages
| Packages resolved | 0 |
|---|---|
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
get_authority ~73
Get a generated Obligation-First authority record by authority ID, not a source matter ID. Schema: https://obligationfirst.org/; context: https://obligationfirst.org/v1/context.jsonld.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | Authority ID, such as british-columbia-civil-resolution-tribunal. |
No output schema declared.
No examples provided.
get_obligation_first_record ~106
Get a generated Obligation-First authority, proceeding, allegation, determination, or tombstone record by kind and graph ID. Schema: https://obligationfirst.org/; context: https://obligationfirst.org/v1/context.jsonld. A proceeding or allegation does not establish a determination.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | Generated Obligation-First record ID. |
| kind | string | yes | Record kind: authorities, proceedings, allegations, determinations, or tombstones. |
No output schema declared.
No examples provided.
get_record ~42
Get one full AI Incident Law source record by error_id or candidate_id.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | Record ID, such as AIEL-2024-001. |
No output schema declared.
No examples provided.
get_staleness_report ~117
Report record verification decay: records ranked oldest-verified first, with per-bucket counts. Use to find matters overdue for re-verification before relying on them.
| Name | Type | Req | Description |
|---|---|---|---|
| as_of | string | – | Optional ISO date (YYYY-MM-DD) to age records against. When omitted, days_stale is not computed and records are returned sorted by verification date only. |
| dataset | string | – | Optional dataset bucket filter, such as included, review, or global. |
| limit | number | – | Maximum records to return. Default 25. |
No output schema declared.
No examples provided.
list_authorities ~46
List Obligation-First authority records generated from included public matters. Schema: https://obligationfirst.org/; context: https://obligationfirst.org/v1/context.jsonld.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_datasets ~23
Summarize the available AI Incident Law dataset buckets and record counts.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_records ~150
List compact AI incident law records, optionally filtered by dataset, domain, type, jurisdiction, status, source quality, or review flag.
| Name | Type | Req | Description |
|---|---|---|---|
| dataset | string | – | Dataset bucket, such as included, review, or global. |
| domain | string | – | Domain/category substring filter. |
| error_type | string | – | Error or event type substring filter. |
| filing_status | string | – | Outcome or procedural posture substring filter. |
| jurisdiction | string | – | Jurisdiction, country, or authority substring filter. |
| limit | number | – | Maximum records to return. Default 25. |
| needs_review | string | – | Review flag, usually yes or no. |
| source_quality | string | – | Source quality substring filter. |
No output schema declared.
No examples provided.
search_records ~63
Search across record titles, descriptions, parties, jurisdictions, tags, and source metadata.
| Name | Type | Req | Description |
|---|---|---|---|
| dataset | string | – | Optional dataset bucket filter. |
| limit | number | – | Maximum matches to return. Default 10. |
| query | string | yes | Case-insensitive search query. |
No output schema declared.
No examples provided.
What is the AI Incident Law MCP server?
AI Incident Law is an MCP server listed in the public MCP registry as io.github.snapsynapse/ai-incident-law. Public-record corpus of AI litigation, regulation, and enforcement, anchored to EveryAILaw. This page covers its npm package (ai-incident-law).
Is the AI Incident Law MCP server safe to use?
AI Incident Law scores 84 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 21 September 2026. It declares no install or post-install scripts. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the AI Incident Law MCP server expose?
AI Incident Law exposes 8 tools: list_datasets, list_records, get_record, search_records, get_staleness_report, and 3 more. Their descriptions and schemas cost roughly 620 tokens of context every time the server is loaded.
Is the AI Incident Law MCP server still maintained?
AI Incident Law is still listed as active in the MCP registry. We last reached this channel on 21 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the AI Incident Law MCP server under?
AI Incident Law declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.