Gibraltar Prediction Markets MCP Server
by 0xJB-dev
README.md
# Gibraltar Prediction Markets โ MCP Server
Query the **Prediction Market Regulations 2026 (LN.2026/176)** in plain English from Claude Desktop, Claude Code, ChatGPT, Cursor, or any [MCP](https://modelcontextprotocol.io) client. Ask a question โ *"What must an application for authorisation include?"* โ and get back the exact, cited regulation text instead of a guess.
Built for lawyers and regulatory professionals who want the statute inside the tools they already use.
๐ **Official text:** [Prediction Market Regulations 2026 (LN.2026/176) โ gibraltarlaws.gov.gi](https://www.gibraltarlaws.gov.gi/uploads/legislations/gambling/2026s176/2026s176.pdf)
> โ๏ธ **Not legal advice.** This server reproduces Gibraltar legislation for research and reference only. It is **not legal advice** and **not an official version of the law**. Always verify against the [official text](https://www.gibraltarlaws.gov.gi/uploads/legislations/gambling/2026s176/2026s176.pdf) and consult qualified Gibraltar counsel before relying on it.
---
## Connect your client
| Client | Guide |
|--------|-------|
| **Claude Desktop** | [docs/claude-desktop.md](docs/claude-desktop.md) |
| **Claude Code (CLI)** | [docs/claude-code.md](docs/claude-code.md) |
| **ChatGPT** (custom connector) | [docs/chatgpt.md](docs/chatgpt.md) |
| **Cursor** & other MCP clients | [docs/cursor.md](docs/cursor.md) |
| **Claude API / Agent SDK** | [docs/api-sdk.md](docs/api-sdk.md) |
| The law & data model | [docs/concepts.md](docs/concepts.md) |
## Quick start
The server is hosted at **`https://mcp.0xjb.dev/mcp`** โ nothing to install. Connect from any MCP client:
### Claude Desktop
1. Open **Settings โ Connectors** (under your profile menu).
2. Click **Add custom connector**.
3. Name it (e.g. `Gibraltar Prediction Markets`) and paste the URL: `https://mcp.0xjb.dev/mcp`
4. Leave the OAuth **Client ID blank** โ no sign-in is required โ and click **Add**.
5. In a new chat, open the tools menu (sliders icon) and check the connector is enabled, then ask away.
### ChatGPT
1. Enable developer mode: **Settings โ Apps & Connectors โ Advanced settings** โ toggle **Developer mode** (requires a paid plan).
2. Go to **Settings โ Apps & Connectors โ Create** (custom connector).
3. Name it, set **MCP server URL** to `https://mcp.0xjb.dev/mcp`, authentication: **None**.
4. Save, then enable the connector in a chat via the **+ / tools** menu. ChatGPT retrieves through the server's `search` and `fetch` tools.
### Claude Code (CLI)
```bash
claude mcp add --transport http gibraltar-pm https://mcp.0xjb.dev/mcp
```
### Cursor / other MCP clients
Add a remote (streamable HTTP) MCP server with URL `https://mcp.0xjb.dev/mcp` โ see [docs/cursor.md](docs/cursor.md).
### Local via npm (stdio)
Every client can also run the [npm package](https://www.npmjs.com/package/gibraltar-prediction-markets-mcp) locally โ no build, no paths:
```json
{
"mcpServers": {
"gibraltar-prediction-markets": {
"command": "npx",
"args": ["-y", "gibraltar-prediction-markets-mcp"]
}
}
}
```
```bash
# Claude Code CLI
claude mcp add gibraltar-prediction-markets -- npx -y gibraltar-prediction-markets-mcp
```
For local testing before publishing, see [PUBLISHING.md](PUBLISHING.md) and the per-client guides (`node dist/index.js` over stdio, or `npm run start:http` for ChatGPT/remote).
## What you can ask
- *"List the arrangement of the Prediction Market Regulations 2026."*
- *"What does regulation 12 say about approving contracts?"*
- *"Give me the checklist for an authorisation application."*
- *"Define 'prediction market contract'."*
- *"Which contracts can the Authority prohibit under regulation 14?"*
- *"Can operators accept stablecoins?"* (regulation 22)
## Tools
Ten tools; `search` + `fetch` also satisfy ChatGPT's connector contract.
| Tool | Purpose |
|------|---------|
| `search(query, limit?)` | Ranked keyword search; returns ids for `fetch`. |
| `fetch(id)` | Full verbatim text by id (`reg-12`, `schedule-2`, `definitions`). |
| `get_regulation(number)` | A regulation, 1โ34, with its Part. |
| `list_regulations()` | The full arrangement of provisions. |
| `get_part(number)` | Every regulation in a Part, 1โ7. |
| `get_schedule(number)` | A Schedule, 1โ3. |
| `get_definition(term?)` | A defined term (reg 3); omit to list all. |
| `get_application_checklist()` | Schedule 1 โ application requirements. |
| `get_authorisation_conditions()` | Schedule 2 โ core conditions. |
| `about()` | Metadata, source and status of this server. |
Every response carries its **source citation** and a not-legal-advice reminder.
## Data model
One authoritative file, [`data/regulations.json`](data/regulations.json), holds the verbatim text. Each unit is an addressable document with a stable id โ `reg-1`โฆ`reg-34`, `schedule-1`โฆ`schedule-3`, and `definitions` (the 14 defined terms of reg 3). This single shape serves every tool. Full walkthrough in [docs/concepts.md](docs/concepts.md).
## Source
- **Law:** Prediction Market Regulations 2026, **LN.2026/176** โ subsidiary legislation under the **Gambling Act 2025** (ss. 34 and 159). Commencement **13 July 2026**.
- **Official text:** [2026s176.pdf](https://www.gibraltarlaws.gov.gi/uploads/legislations/gambling/2026s176/2026s176.pdf) ยท ยฉ Government of Gibraltar, [gibraltarlaws.gov.gi](https://www.gibraltarlaws.gov.gi).
## License
MIT for the server code. The legislative text is ยฉ Government of Gibraltar, reproduced for reference.
TDQS
A4.1/5.0
Scored across 10 tools
Disambiguation5/5
Each tool serves a distinct purpose: metadata, search, list, or retrieval of specific components (regulations, parts, schedules, definitions, checklists, conditions). No two tools overlap in functionality.
Naming Consistency4/5
Most retrieval tools follow a consistent 'get_' prefix pattern, but 'about', 'fetch', 'search', and 'list_regulations' break this convention. While still readable, the naming is not perfectly uniform.
Tool Count5/5
10 tools cover the domain of a regulatory document server comprehensively without being excessive. Each tool earns its place.
Completeness5/5
The tool set covers all necessary operations for a static legal document: metadata, search, listing, and retrieval of any component. There are no obvious gaps for the stated purpose.
Maintenance
ActivityStale
ResponsivenessNo issues