DIFC vs ADGM MCP Server

Endpoint

Hosted endpoint · transport

Connect

This is a remote MCP server — point an MCP client at the endpoint URL. Clients with native remote support (Claude, Cursor, VS Code, …):

For stdio-only clients (older Claude Desktop, etc.), bridge with mcp-remote:

If the server requires authentication, add the provider's token/header (e.g. an X-API-Key) per its docs. A quick reachability check:

Tools

• checker_start — The first question of the DIFC or ADGM: route your activity decision guide.
• checker_answer — Given a question id and the chosen option (its `choice` index), return the next question or the final verdict.
• checker_tree — Every question, option and verdict of the DIFC or ADGM: route your activity guide, for reasoning end to end.
• enquiry_describe — Read first. States plainly what submit_enquiry does on DIFC vs ADGM: it starts an enquiry with human providers who quote directly. Nothing is bought, ordered or paid; no quote is guaranteed; it is free. Also returns who receives the details, the consent wording, and how the person confirms.
• enquiry_fields — Every field of the DIFC vs ADGM enquiry: key, label, type, whether required, help text and the allowed options where there are any. Pass answers to submit_enquiry keyed by field key.
• submit_enquiry — Submits an enquiry to DIFC vs ADGM — NOT a purchase, NOT a guaranteed quote. Step 1: call with the answers (keyed by field key from enquiry_fields) and consent=true; it validates and returns a summary, the consent line and a confirmation token — show the person the summary and the consent line. Step 2: only if the person agrees, call again with the same answers, consent=true and the confirmation token; the enquiry is then submitted, and the person receives an email with a link they must click before any provider sees it. Consent means the person has read and agreed to: "Send my contact details to up to three UAE and Saudi company set-up agents, chosen by DIFC vs ADGM, who'll contact me directly. I'll be emailed each firm's name as my details go to it, and can stop any more firms getting them."

About MCP

The Model Context Protocol (MCP) is an open protocol Anthropic introduced for connecting LLM-based agents to external tools and data sources. Providers publish MCP servers that expose their API surface as structured, discoverable tools — an MCP-compatible client (Claude Desktop, Cursor, Cline, Continue, etc.) can connect to the server and call its tools without any per-provider integration code.

Browse every MCP server on the APIs.io network or compare with the broader Agent Skill surfaces of the same providers.

Work with this as data

Every MCP server here is available over the APIs.io API and to AI agents over MCP.

curl "https://apis.io/api/v1/mcp/difc-vs-adgm-mcp-server"

curl "https://apis.io/api/v1/mcp?limit=25"