Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, email [email protected] and we’ll put it right.

EveryAILaw

NPM · EVERY-AI-LAW · SCANNED AUG 3

AI obligation registry: regulations, provisions, evidence, and enforcement deadlines.

Available components

−41 this week 31 Trust /100
Trust breakdown (6 categories)

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 & Transparency6
Schema Quality & AI Usability0
  • Schema quality not yet verified: we do not have a sandbox capture of the MCP schema this version of the package serves yet.Unverified
Stability & Change Management0
  • Stability not yet verified: we do not have a sandbox capture of the MCP schema this version of the package serves yet.Unverified
Tool Coverage0
  • Tool coverage not yet verified: we do not have a sandbox capture of the tool definitions this version of the package serves yet.Unverified
Capabilities0
  • Protocol version not yet verified: we do not have a sandbox capture of the MCP handshake this version of the package performs yet.Unverified

Unverified: 4 categories

Categories scored 0 because our sandbox run of this package has not given us the schema these checks need to read. That is a gap on our side rather than a finding about the package, and we only credit what we can confirm, so the score stands at 0 until the capture succeeds. We are working through the fleet, so this normally clears without any action from you. How we score packages →

Install

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 · every-ai-law

# add to Claude Code
claude mcp add snapsynapse-every-ai-law -- npx -y every-ai-law
# add to Codex CLI
codex mcp add snapsynapse-every-ai-law -- npx -y every-ai-law
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "snapsynapse-every-ai-law": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "every-ai-law"
      ],
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add snapsynapse-every-ai-law --command npx --arg -y --arg every-ai-law
# ~/.hermes/config.yaml
mcp_servers:
  snapsynapse-every-ai-law:
    command: "npx"
    args: ["-y", "every-ai-law"]
// mcp.json
{
  "mcpServers": {
    "snapsynapse-every-ai-law": {
      "command": "npx",
      "args": [
        "-y",
        "every-ai-law"
      ]
    }
  }
}
Changelog

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 Aug 26 −27
    • Stability: Stability not yet verified: we do not have a sandbox capture of the MCP schema this version of the package serves yet. security
    • Tool coverage: 100 → unverified functional
    • Capabilities: fail → unverified functional
    • Package version: 0.3.0 → 0.5.0 functional
  • 2 Aug 26 +15
    • Malware scan: unverified → pass security
  • 1 Aug 26 −11
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 31 Jul 26 −18
    • Malware scan: pass → unverified security
  • 27 Jul 26 +35
    • Tool coverage: unverified → 100 functional
    • First check of Tool coverage: 100 functional
    • First check of Schema quality: pass functional
    • First check of Schema quality: excellent functional
    • First check of Schema quality: fail functional
  • 26 Jul 26 37

    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
Diagnostics

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.

MCP tools — 14 exposed · ~508 tokens

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.

Tool Tokens
check_requirement ~36

Check whether a regulation requires a specific obligation.

NameTypeReqDescription
obligationstringyesObligation ID
regulationstringyesRegulation ID

No output schema declared.

No examples provided.

compare_regulations ~47

Compare two regulations by obligation overlap. Shows shared obligations, unique-to-each.

NameTypeReqDescription
regulation_astringyesFirst regulation ID
regulation_bstringyesSecond regulation ID

No output schema declared.

No examples provided.

find_regulations_by_obligations ~37

Find regulations that address ALL specified obligations.

NameTypeReqDescription
obligationsarrayyesArray of obligation IDs that must ALL be addressed

No output schema declared.

No examples provided.

get_authority ~28

Get full details for a regulatory authority by ID.

NameTypeReqDescription
idstringyesAuthority ID

No output schema declared.

No examples provided.

get_evidence ~29

Get verification sources and freshness dates for a provision.

NameTypeReqDescription
provision_idstringyesProvision ID

No output schema declared.

No examples provided.

get_obligation ~47

Get full details for an obligation by ID, including which regulations address it.

NameTypeReqDescription
idstringyesObligation ID (e.g. "transparency", "human-oversight")

No output schema declared.

No examples provided.

get_regulation ~53

Get full details for a regulation by ID, including timeline, provisions, and obligations covered.

NameTypeReqDescription
idstringyesRegulation 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.

NameTypeReqDescription
threshold_daysnumberDays threshold (default: 30)

No output schema declared.

No examples provided.

get_timeline ~36

Get upcoming enforcement dates and milestones across all regulations.

NameTypeReqDescription
afterstringShow 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 ~62

List all tracked regulations. Optionally filter by jurisdiction or status.

NameTypeReqDescription
jurisdictionstringFilter by jurisdiction (e.g. "EU", "California")
statusstringFilter 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.

search ~29

Search across obligations, regulations, provisions, and authorities by keyword.

NameTypeReqDescription
querystringyesSearch query

No output schema declared.

No examples provided.