EveryAILaw
EveryAILaw is an MCP server published by snapsynapse; its MCP spec-revision support has not been verified yet. Last verified 2026-08-15.
Does EveryAILaw support the current MCP specification (2026-07-28)?
Undetermined. We have not verified which MCP specification revision EveryAILaw supports (as of 2026-08-15).
Is EveryAILaw a first-party (official) MCP server?
Undetermined. We have not verified the publisher relationship for EveryAILaw (as of 2026-08-15).
How do I connect to EveryAILaw?
EveryAILaw is available via the package npm:every-ai-law, the official MCP Registry under io.github.snapsynapse/every-ai-law, the source repository at https://github.com/snapsynapse/every-ai-law. Authentication: unknown. Transports: stdio.
When were EveryAILaw's facts last verified?
2026-08-15. Each fact on this page links to the sources used to verify it.
AI obligation registry: regulations, provisions, evidence, and enforcement deadlines.
How widely adopted is EveryAILaw?
Not ranked in The MCP 500: insufficient public data (coverage floor not met) (snapshot ). The Adoption Index measures public signals only; it says nothing about quality.
Repository and package signals for EveryAILaw
Measured directly from the source registries, not asserted from a document. Each figure carries the date it was read; none of it affects the verified spec status above.
Repository as of
The repository this server declares no longer resolves. That is a measurement, not
a failed lookup: https://github.com/snapsynapse/every-ai-law returned 404 when checked.
Package (npm) as of
- Latest version
0.6.0- Last published
- First published
- Releases
- 3
- License (package)
- SEE LICENSE IN DATA-LICENSE.md
- Maintainers
- 1
- Direct dependencies
- 0
- Unpacked size
- 3.0 MB
- Registry signature
- Signed
- Build provenance
- No attestation
How was this verified, and what are the sources?
Verified · method: registry-record
· confidence 0.85 (Good).