Vixio MCP server: regulatory intelligence for AI assistants

Connect an assistant

The server lives at https://mcp.vixio.support/mcp. Sign-in happens in your browser; there is no password to copy anywhere.

Claude Code

claude mcp add --transport http vixio https://mcp.vixio.support/mcp

Claude Desktop, and claude.ai

Remote servers are added once to your Claude account rather than to a file on one machine, and then work everywhere you use Claude, Desktop included.

Go to Customize → Connectors on claude.ai, choose Add custom connector, and paste:

https://mcp.vixio.support/mcp

Leave Advanced settings alone. It offers an OAuth client ID and secret, and this server does not need them: it registers clients automatically. Click Add, then connect and sign in.

Not claude_desktop_config.json. That file configures local servers that run on your own machine as a subprocess, which is a different mechanism. A remote server put there will not connect.

ChatGPT

Requires developer mode, and on a Business or Enterprise workspace an administrator must enable it first. Settings → Connectors → Advanced settings → Developer mode, then Create, and give it:

Name                Vixio
MCP server URL      https://mcp.vixio.support/mcp
Authentication      OAuth

Gemini CLI

gemini mcp add --transport http vixio https://mcp.vixio.support/mcp

Or in ~/.gemini/settings.json:

{
  "mcpServers": {
    "vixio": {
      "httpUrl": "https://mcp.vixio.support/mcp",
      "oauth": { "enabled": true }
    }
  }
}

Any other MCP client

Point it at the URL above. The server implements OAuth 2.1 discovery (RFC 9728 and RFC 8414) with dynamic client registration, PKCE and RFC 9207 issuer identification, so a conformant client configures itself.

What it can do

Six tools, shaped for the questions compliance teams actually ask.

ask_vixioAsk a regulatory question and get a written answer from VIQ with numbered sources, a confidence level and a warning when newer material sits outside your tier.

search_by_topicFind content about a subject by searching article bodies through VIQ, ranked by relevance, with relevant content outside your subscription listed by title.

whats_changedEverything created or edited since a date, scoped by platform, content type and jurisdiction. Complete, where VIQ is ranked.

search_contentSearch by title text, jurisdiction, authority and date. Returns titles, links, dates, tags and a summary.

get_recordThe full text of a single record. For a country report or guide, it lists the sections and returns whichever one you ask for.

list_taxonomyBrowse the jurisdictions, authorities and other vocabularies that content can be filtered by.

Two routes to the content. The Vixio API tools are exact and complete but match text in article titles only. The VIQ tools search article bodies and come back ranked by relevance; ask_vixio returns the same cited answers as the assistant on the Vixio platforms. The assistant is told which route each kind of question takes, and in particular that "what changed since" always goes to whats_changed, because a ranked search cannot promise it found everything.

Country reports and guides are covered too. They keep almost all of their content in sections rather than in one article body, so get_record lists the sections first and returns whichever one you name. A single gambling country report runs to well over a hundred thousand characters across nineteen of them.

Jurisdictions and authorities are given by name. The server resolves them to Vixio's internal tag ids for you, and asks which you meant when a name is ambiguous rather than guessing.

The Vixio API has no full-text search. search_content matches article titles, not bodies. A topic discussed inside an article but absent from its title will not be found that way; that is what search_by_topic and ask_vixio are for. An empty title search does not mean the content is not there.

What you can see

Every request is made as you.

Platform entitlements and the jurisdiction ceiling are enforced by the Vixio API exactly as they are for any other client. For the VIQ tools, the server asks the Vixio platforms what your subscription covers, by the email you signed in with, and states exactly that to VIQ. It cannot state more, and content outside your subscription is named by title only.

Platform	Code	Content
Gambling Compliance	`gc`	News analysis, sports betting, In Focus briefings, regulatory updates, data forecasts, jurisdictional reports, trackers
Payments Compliance	`pc`	Horizon scanning, insights, requirements, regulatory analysis, guides, trackers
Financial Services	`fs`	Horizon scanning, regulatory analysis

Where your subscription does not cover a platform, the assistant is told so in plain words rather than shown an error.

Getting access

For ask_vixio and search_by_topic you need a Vixio account with a subscription, which is what you already use on the Vixio platforms. For the other four tools you also need a Vixio API account with a matching email address, which your Vixio account manager arranges. If sign-in works but the API tools say no API account exists, that is the usual cause.

For developers

To inspect the protocol itself, including raw tool schemas and request and response envelopes, use the official inspector:

npx @modelcontextprotocol/inspector https://mcp.vixio.support/mcp

There is also a local stdio server for single-developer use, which reads credentials from your environment instead of a browser sign-in. Your Vixio contact can point you at it.

Regulatory intelligence, inside your AI assistant