AI Incident Law
NPM · AI-INCIDENT-LAW · SCANNED AUG 3
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 →
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 & Transparency45
- 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
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability70
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 525 tokens (~65/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 Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
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
Capabilities20
- Spec-recency check failed: implements MCP spec 2024-11-05; the latest is 2026-07-28. See how to fix → Fail
Unverified: 1 category
A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.
Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.
npm · ai-incident-law
claude mcp add snapsynapse-ai-incident-law -- npx -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": {
"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.
- 2 Aug 26 +15
- Malware scan: unverified → pass ▲ security
- 1 Aug 26 −12
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 27 Jul 26 +32
- Tool coverage: unverified → 100 ▲ functional
- First check of Schema quality: pass functional
- First check of Tool coverage: 100 functional
- First check of Schema quality: good functional
- First check of Schema quality: fail functional
- 26 Jul 26 29
First indexed and scored.
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
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 3 Aug 2026 · Analysed npm/[email protected]
Provenance none
Ecosystem: npm · Outcome: none
Dependencies 0 packages
0 packages in the resolved dependency tree.
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.
get_authority ~43
Get a generated Obligation-First authority record by authority ID.
| 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 ~65
Get a generated Obligation-First proceeding, allegation, determination, or authority record by kind and ID.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | Generated Obligation-First record ID. |
| kind | string | yes | Record kind: proceedings, allegations, determinations, or authorities. |
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 ~22
List Obligation-First authority records generated from included public matters.
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.