EveryAILaw
NPM · EVERY-AI-LAW
AI law obligations, evidence, deadlines, saved profiles, audit trails, and signed change alerts.
Available components
Last scanned (15 hours ago)
Scores higher than 56% of npm servers
Category Security
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 & Transparency6
- Repository check failed: the declared repository URL returned HTTP 404. See how to fix → View diagnostics → Fail
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Licence could not be checked: the licence is shipped as a file inside the package, not declared as a standard (SPDX) licence identifier, so we cannot tell whether it is OSI-approved.Unverified
- Actively maintained (last published 54 days ago).Pass
- Security-disclosure policy not yet verified: we couldn't inspect the source repository.Unverified
Schema Quality & AI Usability78
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 1106 tokens (~55/item across 20 items; 20 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
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 20 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 20 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
Checks we ran (14)
- Malware scan
- Known CVEs
- Install scripts
- Dependency health
- Source repository
- Provenance
- Maintenance
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Checks we could not complete (2)
These are gaps on our side, not findings about this package. We only credit what we can confirm, so a category made up entirely of them scores 0.
- License in Provenance & TransparencyLicence could not be checked: the licence is shipped as a file inside the package, not declared as a standard (SPDX) licence identifier, so we cannot tell whether it is OSI-approved.
- Security disclosure in Provenance & TransparencySecurity-disclosure policy not yet verified: we couldn't inspect the source repository.
Does not apply to this package (2)
- Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
- Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
The score does not measure everything. What the score does not measure →
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.
- 3 Nov 26 0
- Stability: 0.97 → pass security
- 2 Nov 26 0
- Stability: pass → 0.97 functional
- 27 Oct 26 0
- Stability: 0.97 → pass security
- 26 Oct 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.
- 25 Oct 26 −1
- Stability: pass → 0.93 functional
- 19 Oct 26 0
- Stability: 0.97 → pass security
- 18 Oct 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.
- 16 Oct 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.
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 6 Nov 2026 · Analysed npm/every-ai-law@0.9.2
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 →
check_requirement ~64
Check whether the pinned EveryAILaw corpus maps a regulation to a specific obligation category. The backward-compatible required boolean reports that modeled mapping, not legal applicability or a complete no-duty conclusion.
| Name | Type | Req | Description |
|---|---|---|---|
| obligation | string | yes | Obligation ID |
| regulation | string | yes | Regulation ID |
No output schema declared.
No examples provided.
compare_regulations ~47
Compare two regulations by obligation overlap. Explicit regulation IDs may include terminal historical instruments.
| Name | Type | Req | Description |
|---|---|---|---|
| regulation_a | string | yes | First regulation ID |
| regulation_b | string | yes | Second regulation ID |
No output schema declared.
No examples provided.
custom_matrix ~72
Build a sparse obligation-by-instrument evidence matrix for a saved Pro profile. Missing cells mean not represented in the corpus, not no legal obligation or compliance.
| Name | Type | Req | Description |
|---|---|---|---|
| obligations | array | – | Optional obligation IDs to include. Omit for all obligations. |
| profile_id | string | yes | Saved EveryAILaw Pro profile ID. |
No output schema declared.
No examples provided.
find_regulations_by_obligations ~44
Find current regulations that address ALL specified obligations. Terminal historical instruments are excluded.
| Name | Type | Req | Description |
|---|---|---|---|
| obligations | array | yes | Array of obligation IDs that must ALL be addressed |
No output schema declared.
No examples provided.
get_audit_log ~63
Retrieve the authenticated customer's append-only EveryAILaw Pro tool-event history. Raw tool arguments and API keys are never returned or stored.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | number | – | Maximum events to return, from 1 to 100. The Pro API bounds out-of-range values. |
No output schema declared.
No examples provided.
get_authority ~28
Get full details for a regulatory authority by ID.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | Authority ID |
No output schema declared.
No examples provided.
get_evidence ~29
Get verification sources and freshness dates for a provision.
| Name | Type | Req | Description |
|---|---|---|---|
| provision_id | string | yes | Provision ID |
No output schema declared.
No examples provided.
get_obligation ~57
Get full details for an obligation by ID, including which current regulations address it. Terminal historical instruments are excluded from this aggregate.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | Obligation ID (e.g. "transparency", "human-oversight") |
No output schema declared.
No examples provided.
get_provision ~81
Read a stored provision by its local slug, including complete current requirement and penalty rows, official source locator, Obligation First links, and qualified dates. No historical as-of lookup or organization-specific applicability determination.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | Provision ID returned by get_regulation (e.g. "eu-ai-act-literacy"), not an Obligation First URI. |
No output schema declared.
No examples provided.
get_regulation ~67
Get regulation metadata, timeline, provision IDs and obligations covered. Use get_provision with a returned provision ID for its complete stored requirements, penalties and source locator.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | Regulation ID (e.g. "eu-ai-act", "colorado-sb24-205") |
No output schema declared.
No examples provided.
get_staleness_report ~40
Get provisions whose verified date exceeds a threshold. Default 30 days.
| Name | Type | Req | Description |
|---|---|---|---|
| threshold_days | number | – | Days threshold (default: 30) |
No output schema declared.
No examples provided.
get_timeline ~42
Get upcoming enforcement dates and milestones across current regulations. Terminal historical instruments are excluded.
| Name | Type | Req | Description |
|---|---|---|---|
| after | string | – | Show dates after this ISO date (default: today) |
No output schema declared.
No examples provided.
list_authorities ~20
List all regulatory bodies with their jurisdictions and regulation counts.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_obligations ~26
List all tracked compliance obligations with IDs, names, groups, and provision counts.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_regulations ~72
List current tracked regulations by default. Optionally filter by jurisdiction or status; an explicit terminal status returns historical records.
| Name | Type | Req | Description |
|---|---|---|---|
| jurisdiction | string | – | Filter by jurisdiction (e.g. "EU", "California") |
| status | string | – | Filter by status (e.g. "enforcing", "enacted") |
No output schema declared.
No examples provided.
list_standards ~18
List all voluntary and harmonized standards.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
query_with_profile ~52
Deterministically filter current EveryAILaw instruments by a saved Pro profile. This is corpus filtering, not legal advice or an applicability determination.
| Name | Type | Req | Description |
|---|---|---|---|
| profile_id | string | yes | Saved EveryAILaw Pro profile ID. |
No output schema declared.
No examples provided.
save_profile ~130
Create or update a customer-scoped EveryAILaw Pro jurisdiction and role profile. A profile is filtering input, not a legal applicability determination.
| Name | Type | Req | Description |
|---|---|---|---|
| idempotency_key | string | – | Stable retry key required when creating a profile. Reuse it after an uncertain response. |
| jurisdictions | array | yes | EveryAILaw jurisdiction slugs. |
| name | string | yes | Human-readable profile name. |
| profile_id | string | – | Existing profile ID to update. Omit to create a profile. |
| roles | array | – | EveryAILaw role slugs. An empty list means all roles in the saved jurisdictions. |
No output schema declared.
No examples provided.
search ~29
Search across obligations, regulations, provisions, and authorities by keyword.
| Name | Type | Req | Description |
|---|---|---|---|
| query | string | yes | Search query |
No output schema declared.
No examples provided.
subscribe_to_changes ~125
Manage informational HTTPS webhook subscriptions for deterministic EveryAILaw corpus changes. Registration returns a signing secret once and requires endpoint challenge verification.
| Name | Type | Req | Description |
|---|---|---|---|
| action | string | yes | One of: list, register, verify, rotate_secret, remove. |
| endpoint_id | string | – | Webhook endpoint ID for verify, rotate_secret, or remove. |
| filters | object | – | Optional exact filters: jurisdictions, roles, obligations, and change_types. |
| profile_id | string | – | Saved Pro profile ID for registration. |
| url | string | – | Public HTTPS webhook URL on port 443 for registration. |
No output schema declared.
No examples provided.
How do I install the EveryAILaw MCP server?
EveryAILaw runs locally as an npm package, launched with npx -y every-ai-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 · every-ai-law
claude mcp add snapsynapse-every-ai-law -- npx -y every-ai-law
What is the EveryAILaw MCP server?
EveryAILaw is an MCP server listed in the public MCP registry as io.github.snapsynapse/every-ai-law. AI law obligations, evidence, deadlines, saved profiles, audit trails, and signed change alerts. This page covers its npm package (every-ai-law).
Is the EveryAILaw MCP server safe to use?
EveryAILaw scores 77 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 6 November 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 EveryAILaw MCP server expose?
EveryAILaw exposes 20 tools: list_obligations, get_obligation, list_regulations, get_regulation, get_provision, and 15 more. Their descriptions and schemas cost roughly 1,106 tokens of context every time the server is loaded.
Is the EveryAILaw MCP server still maintained?
EveryAILaw is still listed as active in the MCP registry. We last reached this channel on 6 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What did VerifyMCP test on the EveryAILaw MCP server?
VerifyMCP ran 14 checks on EveryAILaw, covering Malware scan, Known CVEs, Install scripts, Dependency health and 10 more. 2 items could not be completed, a gap on our side rather than a finding about EveryAILaw: License and Security disclosure. Endpoint Security and Transport & Reachability do not apply to an npm package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.