io.github.snapsynapse/ai-incident-law
AI Incident Law
Public-record corpus of AI litigation, regulation, and enforcement, anchored to EveryAILaw.
alive probed 2026-10-19
8tools
≈ 820tokens, estimate
≈ 0.4 %of Claude's 200k window
0.6×the median server
115 msto initialize
4 msto list tools
- Run it
- npx -y ai-incident-law@0.4.3 (stdio, probed in a container with the network off)
- Host
- npmjs.com
- Reports itself as
- ai-incident-law 0.4.3
- Capabilities
- tools
- Instructions
- 1 436 characters
- Of a 1M window
- ≈ <0.1 % of a 1M context window, estimate
- Claude count
- The count_tokens endpoint refused the tool schemas: invalid x-api-key. The estimate stands in.
- Repository
- https://github.com/snapsynapse/ai-incident-law
- Website
- https://aiincidentlaw.org/
- Registry
- active, updated 2026-09-12 · registry entry
- Reachable
- 1 of the last 1 probe
Most expensive tools
Estimates with the o200k_base tokenizer.
| Tool | o200k estimate | Share of this server |
|---|---|---|
| list_records | 191 | 23 % |
| get_staleness_report | 141 | 17 % |
| get_obligation_first_record | 134 | 16 % |
| get_authority | 96 | 12 % |
| search_records | 92 | 11 % |
Badge for the README
The result of the latest probe, the tool count and the token cost. The feed has an entry for every probe that changed them.
A mail when this server changes
Stops answering, comes back, tool set or cost changes. One confirmation mail first, a stop link in every mail.
For the publisher
- The Anthropic count_tokens endpoint refused the tool schemas (invalid x-api-key). A client that validates schemas can refuse them too.