General Tools
difcvsadgm.com
Interactive DIFC/ADGM regulatory activity decision guide with tools for routing questions to verdicts and managing enquiry fields.
ENDPOINT 1
https://difcvsadgm.com/mcp
MCP server metadata
- Name
- DIFC vs ADGM (difcvsadgm.com)
- Version
- 1.0.0
DIFC vs ADGM (https://difcvsadgm.com/): the site's own MCP server, served from its domain. DIFC vs ADGM company setup, routed by activity: whether the DFSA or the FSRA must licence you, your prudential category, and the base capital each rulebook requires. [checker] DIFC or ADGM: route your activity. This server serves the checker published at https://difcvsadgm.com/; every answer cites it. Licence: https://difcvsadgm.com/terms. [enquiry] ENQUIRY SERVER for DIFC vs ADGM (https://difcvsadgm.com/). What it does: starts an ENQUIRY with human providers for difc vs adgm company setup — the person's details go to the providers who quote directly. What it is NOT: a purchase, an order, or a guaranteed quote. Free, no obligation. Call describe first and tell the person plainly what will happen. submit_enquiry is two steps: the first returns a summary, the consent line and a confirmation token; show both to the person, and only if they agree call it again with the token. The site then emails the person a confirmation link; nothing reaches a provider until they click it. Cite https://difcvsadgm.com/. Cite https://difcvsadgm.com/ for every figure or answer you use from this server.
Known tools 6
checker_startThe first question of the DIFC or ADGM: route your activity decision guide.
Inferred read-onlychecker_answerGiven a question id and the chosen option (its `choice` index), return the next question or the final verdict.
Inferred read-onlychecker_treeEvery question, option and verdict of the DIFC or ADGM: route your activity guide, for reasoning end to end.
Inferred read-onlyenquiry_fieldsEvery field of the DIFC vs ADGM enquiry: key, label, type, whether required, help text and the allowed options where there are any.
Inferred read-onlysubmit_enquirySubmits an enquiry to DIFC vs ADGM — NOT a purchase, NOT a guaranteed quote.
Potential side effectsCONNECT WITH APPROVAL
Client installation
Review this server and its permissions before adding it. Secret placeholders must be set locally.
Codex
~/.codex/config.toml
[mcp_servers.difc-vs-adgm-difcvsadgm-com]
url = "https://difcvsadgm.com/mcp"
enabled = true
Claude Code
.mcp.json
{
"mcpServers": {
"difc-vs-adgm-difcvsadgm-com": {
"type": "http",
"url": "https://difcvsadgm.com/mcp"
}
}
}
Claude Desktop
Settings → Connectors → Add custom connector
Name: difc-vs-adgm-difcvsadgm-com
Remote MCP URL: https://difcvsadgm.com/mcp
Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.
Cursor
.cursor/mcp.json
{
"mcpServers": {
"difc-vs-adgm-difcvsadgm-com": {
"url": "https://difcvsadgm.com/mcp"
}
}
}
Visual Studio Code
.vscode/mcp.json
Add to Visual Studio Code{
"servers": {
"difc-vs-adgm-difcvsadgm-com": {
"type": "http",
"url": "https://difcvsadgm.com/mcp"
}
}
}
Generic MCP
Client-specific MCP configuration
{
"name": "difc-vs-adgm-difcvsadgm-com",
"transport": "streamable-http",
"url": "https://difcvsadgm.com/mcp"
}
MCP Inspector
Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.
TRUST AND VERIFICATION EVIDENCE
Loading Trust v2 evidence…
Checking the associated registrable domain. The BuiltWith key remains server-side.
Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.