Regulations.ai — Global AI Law Tracker
REMOTE · REGULATIONS.AI · SCANNED SEP 28
AI laws from 110+ countries, enforcement actions and a 3,900-term glossary. Free, no API key.
Available components
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. How we score → Why this is hard to score →
Endpoint Security63
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- 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. See how to fix → View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability82
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 747 tokens (~93/item across 8 items; 8 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management27
- Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
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 8 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 9 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
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.
remote · regulations.ai
claude mcp add --transport http ai-regulations-regulations-ai 'https://regulations.ai/api/mcp/v1'
{
"mcpServers": {
"ai-regulations-regulations-ai": {
"url": "https://regulations.ai/api/mcp/v1"
}
}
} {
"servers": {
"ai-regulations-regulations-ai": {
"type": "http",
"url": "https://regulations.ai/api/mcp/v1"
}
}
} [mcp_servers.ai-regulations-regulations-ai] url = "https://regulations.ai/api/mcp/v1"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"ai-regulations-regulations-ai": {
"type": "remote",
"url": "https://regulations.ai/api/mcp/v1",
"enabled": true
}
}
} openclaw mcp add ai-regulations-regulations-ai --url 'https://regulations.ai/api/mcp/v1' --transport streamable-http
mcp_servers:
ai-regulations-regulations-ai:
url: "https://regulations.ai/api/mcp/v1" {
"McpServers": {
"ai-regulations-regulations-ai": {
"Transport": "http",
"Url": "https://regulations.ai/api/mcp/v1"
}
}
} assistant mcp add ai-regulations-regulations-ai -t streamable-http -u 'https://regulations.ai/api/mcp/v1'
{
"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.
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.
- 28 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 27 Sept 26 +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.
- 25 Sept 26 +1
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 23 Sept 26 +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.
- 21 Sept 26 +1
- Stability: unverified → 0.03 ▲ functional
- 20 Sept 26 66
First indexed and scored.
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 28 Sept 2026 · Probed https://regulations.ai/api/mcp/v1
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=regulations.ai | CN=YE1,O=Let's Encrypt,C=US | 4 Sept 2026 | 3 Dec 2026 | ECDSA 256 | ECDSA-SHA384 | 6781f328ad9ca9aba8a7e5f5167427a1ea9 |
| SANs: *.regulations.ai, regulations.ai | ||||||
| CN=YE1,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 5ddd70dd31f801c85c186a7a04b80afe |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of regulations.ai. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| ai. | present | 3799 | 8 | Verified |
| regulations.ai. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=63072000; includeSubDomains; preload |
| content-security-policy | default-src 'self'; script-src 'self' 'unsafe-inline' 'wasm-unsafe-eval' https://www.googletagmanager.com https://www.google-analytics.com https://www.google.com https://www.gstatic.com https://apis.google.com https://translate.google.com https://translate.googleapis.com https://translate-pa.googleapis.com https://static.cloudflareinsights.com; script-src-attr 'none'; style-src 'self' 'unsafe-inline' https://www.gstatic.com https://translate.googleapis.com https://fonts.googleapis.com; img-src 'self' data: https: blob:; font-src 'self' data: https://fonts.gstatic.com; connect-src 'self' https://firebasestorage.googleapis.com https://*.google-analytics.com https://*.analytics.google.com https://www.googletagmanager.com https://firestore.googleapis.com https://www.google.com https://www.googleapis.com https://www.gstatic.com https://fonts.gstatic.com https://identitytoolkit.googleapis.com https://securetoken.googleapis.com https://content-firebaseappcheck.googleapis.com https://translate.google.com https://tran |
| x-content-type-options | nosniff |
| x-frame-options | DENY |
| referrer-policy | strict-origin-when-cross-origin |
| permissions-policy | camera=(), microphone=(self), geolocation=(), payment=(), usb=(), interest-cohort=() |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://regulations.ai/api/mcp/v1 | Verified | 200 | |
| http (plaintext) | http://regulations.ai/api/mcp/v1 | HTTPS enforced | 301 | https://regulations.ai/api/mcp/v1 |
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 →
compare_regulations ~52
Return 2-5 regulations side by side: the facts for each plus a snippet, and a url to the full comparison on regulations.ai.
| Name | Type | Req | Description |
|---|---|---|---|
| ids | array | yes | 2 to 5 regulation ids |
No output schema declared.
No examples provided.
fetch ~62
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.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | An id returned by `search` |
No output schema declared.
No examples provided.
get_glossary_term ~65
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.
| Name | Type | Req | Description |
|---|---|---|---|
| term | string | yes | Term to define, e.g. "high-risk AI system" |
No output schema declared.
No examples provided.
get_regulation ~60
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.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | Regulation id |
No output schema declared.
No examples provided.
list_jurisdictions ~23
List every jurisdiction covered, with how many regulations each has.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
recent_changes ~104
Regulations added or updated recently. This is the differentiated capability — the corpus is rescanned weekly, so a general model cannot answer it.
| Name | Type | Req | Description |
|---|---|---|---|
| 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) |
No output schema declared.
No examples provided.
search ~68
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.
| Name | Type | Req | Description |
|---|---|---|---|
| query | string | yes | What to look for |
No output schema declared.
No examples provided.
search_regulations ~161
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | 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 |
No output schema declared.
No examples provided.
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.