Connect an AI assistant to our pages
Some readers reach a website through a program instead of a browser. We run a public server for exactly that purpose: an AI assistant connected to it can look up the pages we publish about slots at operators outside UK licensing, and what it gets back is the same material a person would open here.
Mistakes and questions
A reader does not need any technical standing to point something out. If a page here looks mistaken, or a question about the website goes unanswered after a careful look, it can be sent to the editorial team through the contacts page. We would rather receive a rough note about a real error than have it sit unnoticed, and a plain question is just as welcome. Either way, the message goes to the people who put this website together, so there is no guessing about who should read it.
Cost and limits
Connecting asks for nothing up front. There is no account to open, no key to obtain and no payment to make, so a first try can happen the moment the idea occurs, without any preparation. For a reader weighing whether the experiment is worth a few minutes, that removes the usual reasons to wait. The only limit is volume: when requests arrive too frequently from a single address, they are limited. Looking up a page now and then sits far inside that line; the limit is there for heavy, repeated traffic.
A public MCP server
MCP is the name of a standard way for one program to ask another for information, and the server we run on it is public. An AI assistant is itself a kind of program: it takes a request and fetches whatever is needed to answer it. Once connected, it can use our server to look up the pages published here, and other programs can use the same interface. Nothing in the arrangement depends on whose assistant sits on the other end, which leaves the choice of program with the reader.
What the server reaches
A lookup reaches published pages only: our game reviews and, where this website has them, the search, collections and studio pages. That set is exactly what we publish, so the server and the website show the same thing; an assistant fetching a review passes on what a reader would see opening it here. Nothing about the connection can change the website itself. It reads what we have published, and that is the whole of what it does.
- URL
https://non-uk-slots.uk/mcp- curl
curl \ -s \ -X POST \ 'https://non-uk-slots.uk/mcp' \ -H 'Content-Type: application/json' \ -H 'Accept: application/json, text/event-stream' \ -H 'MCP-Protocol-Version: 2025-11-25' \ -d '{"jsonrpc": "2.0", "id": "1", "method": "tools/call", "params": {"name": "pokies", "arguments": {"url": "https://non-uk-slots.uk/pokies/big-bass-bonanza-slot/"}}}'- Cursor
{ "mcpServers": { "non-uk-slots.uk": { "url": "https://non-uk-slots.uk/mcp" } } }- VS Code
{ "servers": { "non-uk-slots.uk": { "type": "http", "url": "https://non-uk-slots.uk/mcp" } } }- MCP
-
online_slots- The themed collections of games published on this website and the page address of every collection. Themed collections of games: 1
pokies- Fetches what one page of the website shows for a given address: the facts of a single game or the page's list of games.
lookup_slots- Searches the names of game pages, game studio pages and collection pages for the entered text. Topics, themes and descriptions are not searched. Reviews: 10