Skip to main content
Glama
Sign In
regintel-mcp

regintel-mcp

by regintelapi
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

regintel-mcp

PyPI version MCP Registry License: MIT

Drop-in regulatory data for your Claude agent. Query 212+ regulations across 41 jurisdictions (GDPR, MiCA, DORA, AASB-S2, NGER, FATF, FCA, ASIC, MAS, SEC, FINRA…) with regulator citations. Works with Claude Desktop, Claude Code, and any MCP-compatible LLM client.

uvx regintel-mcp        # or: pip install regintel-mcp

Smoke-test the install in 5 seconds — list_jurisdictions works without an API key. Once you confirm the package is wired into your client, get a free key (100 credits, no card, ~20 seconds): regintelapi.com/k

Tools

Tool

What it does

Credits

list_jurisdictions

All 41 supported jurisdictions with codes and regulation counts

Free, no key required

search_regulations

Filter the catalog by jurisdiction, tag, keyword, category. Paginated.

1

get_regulation

Full record (obligations, penalties, scope, source URL) for one regulation by ID

1

get_recent_updates

Regulations added or modified since a date. Useful for incremental sync of vector stores.

free

check_compliance

Decision signal (allowed / requires_license / restricted / prohibited) for an activity in a country

1

get_aasb_s2_obligations

Australian AASB-S2 climate-disclosure obligations. Filterable by Group tier, category code, reporting year. Information only — does not calculate emissions or judge assurance.

1

Related MCP server: lawyer-mcp

Configure with Claude Desktop

Add to claude_desktop_config.json:

{
  "mcpServers": {
    "regintel": {
      "command": "uvx",
      "args": ["regintel-mcp"],
      "env": {
        "REGINTEL_API_KEY": "your-api-key-here"
      }
    }
  }
}

Restart Claude Desktop. Six tools appear under the regintel server. Ask: "is crypto trading allowed in Australia?" — the model routes that to check_compliance(country="AU", activity="crypto") on its own.

Configure with Claude Code

claude mcp add regintel -e REGINTEL_API_KEY=your-api-key-here -- uvx regintel-mcp

Try it without a key

list_jurisdictions is auth-optional — useful as a sanity check after install:

Ask Claude: "list the jurisdictions in the regintel server"

If you get back a JSON list with EU, US, AU, SG, UK and 36 others, the package is wired in. Now grab a key for the rest of the tools: regintelapi.com/k

Environment variables

  • REGINTEL_API_KEY (required for billed tools) — your API key. Without it, list_jurisdictions still works; every other tool returns an actionable signup prompt.

  • REGINTEL_API_BASE (optional) — override the API base URL. Defaults to https://api.regintelapi.com.

Pricing

Plan

Credits

Price

Free

100 (one-time, no expiry)

$0, no card

Starter

1,000/month

$10/month

Pro

10,000/month

$50/month

One-time credit packs also available. See regintelapi.com/pricing.

Links

License

MIT

Available Tools

5 tools
check_complianceA

Check the regulatory status of an activity in a country. Returns a decision signal — one of allowed, requires_license, restricted, prohibited, or unknown — along with risk level, penalties, obligations, and the source regulations behind the decision.

NOT LEGAL ADVICE. This endpoint provides regulatory intelligence derived from structured data; always consult a qualified legal professional before acting on it.

Args: country: Country code or name, e.g. "AU", "US", "EU", "SG", "UK". Required. activity: One of "crypto", "finance", "banking", "payments", "lending", "privacy", "data_protection", "aml", "kyc". Required.

Inputs: country (required), activity (required). Returns: result

get_recent_updatesA

List regulations added or amended recently — the regulatory change feed.

Use this when the user asks "what's new in [jurisdiction] compliance", "what regulations changed this quarter", "are there any recent updates to MiCA / GDPR / etc.", or for incremental sync of a downstream cache or vector store (only re-process what changed). Each item carries a canonical uri, an upstream source_url, and a change_type of new or amended.

Args: since: ISO date (YYYY-MM-DD) lower bound for the modification timestamp, e.g. "2026-01-01". If omitted, the API returns the default recent window. jurisdiction: Optional jurisdiction code to scope the query, e.g. "EU".

Inputs: since, jurisdiction. Returns: result

get_regulationA

Get the full record for a single regulation by its integer ID.

Use this when the user asks for the specific obligations, penalties, scope, or article-level detail of a named regulation (e.g. "what are the obligations under GDPR?", "what's the penalty range for MiCA?", "summarise Article 17 of GDPR"). Returns the complete regulation document: jurisdiction (and legacy country), category (and legacy industry), regulation text, obligations, penalties, scope, tags, upstream source_url, canonical uri, key articles, and timestamps.

IDs are integers (e.g. 123 = GDPR, 124 = GDPR Art. 17, 126 = MiCA). Use search_regulations first to discover IDs — every result includes an id field you can pass here.

Args: regulation_id: Integer ID of the regulation, e.g. 123. Required.

Inputs: regulation_id (required). Returns: result

list_jurisdictionsA

List all regulatory jurisdictions supported by RegIntel, with their codes and regulation counts.

Use this to discover the universe of supported regions (currently 41) and the canonical jurisdiction codes you can pass to other tools like search_regulations or check_compliance. This endpoint does not consume API credits.

Inputs: no named parameters. Returns: result

search_regulationsA

Search the RegIntel database of global regulatory and compliance rules.

Use this tool when the user asks about regulatory obligations, compliance requirements, legal changes, cross-border regulatory differences, or industry-specific rules in any of 41 supported jurisdictions (e.g. GDPR and MiCA in the EU, MAS rules in Singapore, FCA in the UK, APRA/ASIC in Australia, SEC/FINRA in the US). Returns a paginated list of matching regulations; each result includes title, jurisdiction, category, tags, a summary, a canonical uri, and an upstream source_url (the original regulator's page) for citation. To get the full obligations/penalties/ scope for a specific regulation, follow up with get_regulation(id).

Args: jurisdiction: ISO-style jurisdiction code, e.g. "EU", "US", "AU", "SG", "UK". Optional. tag: Tag filter, e.g. "GDPR", "KYC", "AML", "crypto". Optional. q: Free-text keyword search across regulation title and body. Optional. category: Category filter, e.g. "Privacy", "Finance", "Crypto", "AML". Optional. limit: Number of results per page (max 100). Optional. page: Page number for pagination, 1-indexed. Optional.

Inputs: jurisdiction, tag, q, category, +2 more. Returns: result

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A4.7/5.0

    Scored across 5 tools

    Disambiguation5/5

    Each tool has a clearly distinct role: jurisdiction discovery, full-text search, record retrieval by ID, change feed, and compliance checking. Even though search_regulations and get_recent_updates both produce regulation lists, their keyword-query vs. time-based-change semantics are unambiguous.

    Naming Consistency5/5

    All tool names follow a consistent lowercase verb_noun imperative pattern: list_, get_, check_, and search_. There are no mixed conventions or vague single-verb names.

    Tool Count5/5

    Five tools is well-scoped for a read-only regulatory intelligence server. Each tool maps to a discrete user workflow step without redundant or filler endpoints.

    Completeness5/5

    The tool set covers the core read lifecycle: discover jurisdictions, search regulations, fetch details, track updates, and get a compliance decision. Any minor conveniences like browsing tags are workable via existing search filters and do not create dead ends.

    Maintenance

    ActivityNo data
    ResponsivenessOutdated data

    Resources

    Related MCP Connectors

    Related MCP Servers

    Appeared in Searches