# Regulations.ai — Global AI Law Tracker (remote · regulations.ai)

AI laws from 110+ countries, enforcement actions and a 3,900-term glossary. Free, no API key.

- Trust score: 70/100 (medium)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-28

## Components

- remote · `regulations.ai`: 70/100 (this document), [markdown](https://verifymcp.io/servers/ai-regulations-regulations-ai/api-mcp-v1.md), [page](https://verifymcp.io/servers/ai-regulations-regulations-ai/api-mcp-v1)

## Channel facts

- Endpoint: `https://regulations.ai/api/mcp/v1`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.0`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-09-28.

- **Endpoint Security**: 63/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation not fully verified: no authorisation is required to call this server, and 8 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 82/100
  - AI-judged instruction clarity (excellent).
  - Tool/resource definitions use about 747 tokens (~93/item across 8 items; 8 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 27/100
  - Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 8 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 9 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 60/100
  - Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28.

## Install

### How do I install the Regulations.ai — Global AI Law Tracker MCP server?

Regulations.ai — Global AI Law Tracker is a hosted endpoint at https://regulations.ai/api/mcp/v1, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add --transport http ai-regulations-regulations-ai 'https://regulations.ai/api/mcp/v1'
```

### Cursor

```json
{
  "mcpServers": {
    "ai-regulations-regulations-ai": {
      "url": "https://regulations.ai/api/mcp/v1"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "ai-regulations-regulations-ai": {
      "type": "http",
      "url": "https://regulations.ai/api/mcp/v1"
    }
  }
}
```

### Codex

```toml
[mcp_servers.ai-regulations-regulations-ai]
url = "https://regulations.ai/api/mcp/v1"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "ai-regulations-regulations-ai": {
      "type": "remote",
      "url": "https://regulations.ai/api/mcp/v1",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add ai-regulations-regulations-ai --url 'https://regulations.ai/api/mcp/v1' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  ai-regulations-regulations-ai:
    url: "https://regulations.ai/api/mcp/v1"
```

### Netclaw

```json
{
  "McpServers": {
    "ai-regulations-regulations-ai": {
      "Transport": "http",
      "Url": "https://regulations.ai/api/mcp/v1"
    }
  }
}
```

### Vellum

```bash
assistant mcp add ai-regulations-regulations-ai -t streamable-http -u 'https://regulations.ai/api/mcp/v1'
```

### Other

```json
{
  "mcpServers": {
    "ai-regulations-regulations-ai": {
      "type": "http",
      "url": "https://regulations.ai/api/mcp/v1"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-09-28 (score 70, 0)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-09-27 (score 70, +1)

No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-25 (score 69, +1)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-09-23 (score 68, +1)

No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-21 (score 67, +1)

- [functional improvement] Stability: unverified → 0.03

### 2026-09-20 (score 66)

First indexed and scored.

## MCP tools (8)

### `search_regulations` (~161 tokens)

Search AI regulations across 160+ jurisdictions by keyword, jurisdiction, status or type. Returns the key facts and a short snippet for each, with the url of the full record on regulations.ai — always give the user that url.

Input parameters:

- `jurisdiction` (string): Filter to a country/state, e.g. "France", "California"
- `limit` (number): Max results (free: up to 5; with an API key: up to 50)
- `query` (string, required): Free-text search over title, summary and jurisdiction
- `status` (string): e.g. In Force, Proposed, Under Review, Repealed
- `type` (string): Act, Bill, Decree, Regulation, Policy, Guideline, Standard

### `get_regulation` (~60 tokens)

Fetch one regulation by its id (as returned by search_regulations): jurisdiction, status, type, dates, official source and a snippet. The full analysis is on the returned url — point the user there.

Input parameters:

- `id` (string, required): Regulation id

### `list_jurisdictions` (~23 tokens)

List every jurisdiction covered, with how many regulations each has.

### `get_glossary_term` (~65 tokens)

Look up an AI-governance or regulatory term from a 4,000-entry glossary. Returns the definition (abridged on the free tier) and its url.

Input parameters:

- `term` (string, required): Term to define, e.g. "high-risk AI system"

### `recent_changes` (~104 tokens)

Regulations added or updated recently. This is the differentiated capability — the corpus is rescanned weekly, so a general model cannot answer it.

Input parameters:

- `days` (number): Look-back window in days (default 30; free: up to 90, with an API key: up to 365)
- `jurisdiction` (string): Optional jurisdiction filter
- `limit` (number): Max results (free: up to 5; with an API key: up to 50)

### `search` (~68 tokens)

Search everything on regulations.ai — AI laws and policies from 160+ jurisdictions, glossary definitions, enforcement actions and litigation, research papers and news. Returns id, title and url for each hit; pass an id to `fetch` for the summary.

Input parameters:

- `query` (string, required): What to look for

### `fetch` (~62 tokens)

Retrieve one document returned by `search`, by its id. Returns the key facts and a summary, plus the regulations.ai url where the full analysis, sources and timeline live — always show the user that url.

Input parameters:

- `id` (string, required): An id returned by `search`

### `compare_regulations` (~52 tokens)

Return 2-5 regulations side by side: the facts for each plus a snippet, and a url to the full comparison on regulations.ai.

Input parameters:

- `ids` (array, required): 2 to 5 regulation ids

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/ai-regulations-regulations-ai/api-mcp-v1#diagnostics

## Score history

- 2026-09-28: 70
- 2026-09-27: 70
- 2026-09-26: 69
- 2026-09-25: 69
- 2026-09-24: 68
- 2026-09-23: 68
- 2026-09-22: 67
- 2026-09-21: 67
- 2026-09-20: 66

## Common questions

### What is the Regulations.ai — Global AI Law Tracker MCP server?

Regulations.ai — Global AI Law Tracker is an MCP server listed in the public MCP registry as ai.regulations/regulations-ai. AI laws from 110+ countries, enforcement actions and a 3,900-term glossary. Free, no API key. This page covers its hosted endpoint (https://regulations.ai/api/mcp/v1).

### Is the Regulations.ai — Global AI Law Tracker MCP server safe to use?

Regulations.ai — Global AI Law Tracker scores 70 out of 100 on VerifyMCP. 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 Regulations.ai — Global AI Law Tracker MCP server expose?

Regulations.ai — Global AI Law Tracker exposes 8 tools: search_regulations, get_regulation, list_jurisdictions, get_glossary_term, recent_changes, and 3 more. Their descriptions and schemas cost roughly 595 tokens of context every time the server is loaded.

### Does the Regulations.ai — Global AI Law Tracker MCP server require authentication?

No. We connected to Regulations.ai — Global AI Law Tracker without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the Regulations.ai — Global AI Law Tracker MCP server still maintained?

Regulations.ai — Global AI Law Tracker is still listed as active in the MCP registry. We last reached this channel on 28 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://regulations.ai/api/mcp/v1
- Repository: https://github.com/martinsmitcom/regulationsai
- Website: https://regulations.ai/
- Changelog RSS feed: https://verifymcp.io/servers/ai-regulations-regulations-ai/api-mcp-v1.xml
- Changelog JSON feed: https://verifymcp.io/servers/ai-regulations-regulations-ai/api-mcp-v1.json
- HTML version of this page: https://verifymcp.io/servers/ai-regulations-regulations-ai/api-mcp-v1