AI Regulation Tracker MCP server

• Registry nameai.regulations/regulations-aiverified in the MCP registry

The registry name sits under regulations.ai. The registry only lets a publisher use that namespace after proving control of the domain through DNS or HTTP.

• Stateanswerschecked 2026-10-17
• Tools8
• Server calls itselfregulations-ai
• Server version1.0.0
• Protocol version2025-06-18

On 2026-10-17 the server answered initialize and tools/list without a sign-in. First answer in 383 ms.

• Whether its tools do the product's job has not been judged yet.

Said by rules from the measurements above. The likely first call is a model's pick from the tool list; read its description before relying on it.

• INITE MCP score100 of 100answers 100 · definitions 100 · context 100 · connects 100
• Answered100% of days10 of 10 daily checks
• Median first answer191 ms
• Space in an agent's context≈ 881 tokensthe definitions of all its tools (8), which an agent carries on every turn
• Tool definitionsA · 100 of 100
• Typed results0 of 8 toolsdeclared outputSchema: results come typed, read once

• Every tool passes all six checks.

A program checks the server once a day: initialize and tools/list, no model. Tokens are the definitions' length at about four characters a token. The grade averages six checks of every tool's name, description, schema and annotations; it says how well the tools are described, not whether they work. The score weighs what was measured and nothing else: answering (25%), doing the product's job (25%), definitions (20%), context (10%), use (10%) and how readily a client connects (10%). A part that was not measured is left out, and a hidden instruction caps the score at 40. The state of vendors' MCP servers: method and numbers →

• search_regulations

  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.

• get_regulation

  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.

• list_jurisdictions

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

• get_glossary_term

  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.

• recent_changes

  What changed in AI regulation recently: records newly added, records whose status, dates or milestones changed (with the previous and new values), and dated milestones that fell due in the window, such as a law taking effect. Each result…

• search

  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…

• fetch

  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.

• compare_regulations

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