AI Incident Law MCP server

by snapsynapse·io.github.snapsynapse/ai-incident-law·v0.4.3

Public-record corpus of AI litigation, regulation, and enforcement, anchored to EveryAILaw.

A92/100grade A

What users say

No reviews yet

Safety scan

A92/100

Adoption

Growing

0 stars441 downloads/wk

Reviews

Nobody has reviewed AI Incident Law yet.

If you have run it, two minutes of your experience saves the next person an afternoon.

No tool declarations could be read from the package source. They show once the server is installed.

scanner v0.1.5 · 2026-09-19 · same rubric, same numbers if you re-run it

no findings

Code scan345 source files scanned25/25
–Live reliabilityno gateway calls yet and no remote to proben/a
–Tool poisoningtools not inspected (local package is not executed); not countedn/a
Auth qualitylocal package, no credentials required12/15
Maintenancelast push 7 days ago15/15
Maintainer identityregistry namespace matches repository owner; GitHub account older than a year8/10

Overall 92/100. Components that don't apply are left out of the denominator. Any critical finding is an F.Rubric Appeal a finding JSON

Runs npx -y ai-incident-law on your machine. Read the scan report first; the gateway never runs local packages.

claude mcp add ai-incident-law -- npx -y ai-incident-law

Is AI Incident Law MCP server safe?: Yes, by our scan: it is graded A (92/100). Read the AI Incident Law safety report
How do I install AI Incident Law?: It runs on your machine. Copy the Claude Code, Claude Desktop or Cursor config from the install section.
Does AI Incident Law need an API key?: Not as far as the registry entry and our scan can tell: no credentials are declared or required.
Is AI Incident Law maintained?: The last commit was 8 days ago (2026-09-12). The latest release is v0.4.3.