Open Emirates Intelligence

Maintained by Ahmed Morsy. Released under the MIT license and built on the original open-source UAEMCP work credited in LICENSE.

The server keeps the public uaemcp contract and extends it to 28 source-cited MCP tools, nine resources, three prompts, bilingual catalog search, CKAN, OpenDataSoft, ArcGIS, Socrata, JSON, CSV, XLSX, XML, RSS, GraphQL, SDMX and SPARQL connectors, geo queries, aggregation, PII redaction, SSRF protection, and health/readiness/Prometheus endpoints. Bun SQLite stores health history and bounded dataset snapshots for repeatable comparisons.

The public gateway is fully bilingual: navigation, product evidence, catalog, connectors, dataset discovery, playground controls and runtime states switch between English and Arabic. Every public application uses Dubai Font with native RTL composition.

The UAE Business Setup Navigator routes founders to the competent official mainland authority or federal free-zone directory across all seven emirates. It does not collect names, phone numbers, emails or passport data, and never pretends to choose a licence, calculate final fees or guarantee approval.

Hosted endpoint

{
  "mcpServers": {
    "uae-intelligence": {
      "type": "http",
      "url": "https://uaemcp.zad.tools/mcp"
    }
  }
}

Related MCP server: MCP-Dubai

Run with Bun

Requires Bun 1.3 or newer.

bun install
bun src/index.ts stdio

The installed CLI also provides deployment diagnostics and shell completion:

uaemcp doctor
source <(uaemcp completion zsh)
uaemcp --help

For Streamable HTTP:

bun src/index.ts http --host 0.0.0.0 --port 8080

Endpoints:

• MCP: POST /mcp

• Liveness: GET /health or /healthz

• Readiness: GET /ready or /readyz

• Prometheus metrics: GET /metrics

• REST API: GET /api/v1/sources, /api/v1/search, and source capability routes

• Vector maps: GET /api/v1/sources/{sourceId}/tilejson and /tiles/{z}/{x}/{y}.pbf

• Public Observatory: GET /observatory — source reliability, incidents and evidence reports

• UAE Industry Atlas: GET /industry-atlas — bounded industrial-establishment evidence by emirate, area and product label

• UAE Trade Flow Radar: GET /trade-flow — bounded Ajman 2023 certificate-of-origin evidence by destination, transport, product code and origin

• UAE Tax Service Activity: GET /tax-services — official FTA 2025 service-activity totals and quarterly evidence, explicitly not revenue or taxpayer counts

• FTA Archive Explorer: GET /tax-services/archive — source-native 2017–2022, 2024 and 2025 workbooks with comparison disabled when scopes are incompatible

• UAE Place Names Explorer: GET /places — bilingual official place-name search and mapped FGIC evidence

• UAE Health Indicators: GET /health-indicators — 111 official MOHAP indicator rows with source-native 2016–2023 series and explicit scale limitations

• UAE Education Ledger: GET /education — FCSC-accredited 2023/2024 national totals, reconciliation checks and the separate seven-resource Ministry of Education catalogue

• UAE Golden Residency Navigator: GET /golden-residency — 14 official routes with direct category pages at ICP/GDRFA/ADRO, federal-vs-local criteria warnings and a printable non-identifying readiness dossier

MCP client configuration

{
  "mcpServers": {
    "uae-intelligence": {
      "command": "bun",
      "args": ["/absolute/path/to/uaemcp/src/index.ts", "stdio"]
    }
  }
}

TypeScript SDK

The same Bun package includes a zero-dependency typed REST client:

import { UaemcpClient } from "uaemcp";

const uae = new UaemcpClient();
const matches = await uae.search("عقارات دبي", { deep: true });
const records = await uae.records("moiat_industrial_licenses", { limit: 10 });

Point baseUrl at the hosted endpoint or any self-hosted instance. Structured API failures throw UaemcpClientError with the HTTP status and public error code.

Generated SDKs

The repository also ships generated clients for Python, Go, Rust, Java and C# under sdk/. All clients are generated from the live OpenAPI 3.1 contract at /openapi.json:

bun run generate:sdks
bun run check:sdks

The second command fails when an API change has not been propagated to every language. It is included in the main release check.

Tools

FTA archive REST mirror: GET /api/v1/tax-services/archive. It returns the 2017–2022 selected-services table, the source-native 2024 monthly table, and the 2025 quarterly table as separate cited views. comparison.status is unavailable: 2023 is missing and the published scopes and schemas are not equivalent, so UAEMCP does not manufacture a trend or annual total.

Unified catalog and coverage

The project does not present every indexed portal as live data. Use:

• GET /api/v1/coverage for live, blocked, key-required and metadata-only totals.

• GET /api/v1/catalog for explicit portal, organization, connector, license and capability models.

• GET /.well-known/uaemcp.json for the operator and trust manifest.

• GET /api/v1/sources/{sourceId}/schema or uae_dataset_schema before aggregation.

• GET /api/v1/sources/{sourceId}/health-history for uptime and latency history.

• GET|POST /api/v1/sources/{sourceId}/snapshots and GET /api/v1/snapshots/diff for dataset history.

• GET /api/v1/intelligence/recipes to discover analytical recipes and run them by id.

Current conservative coverage is 40 official sources indexed, 8 live record connectors, 1 blocked connector, and 3 key-required portals. Counts never imply that metadata-only portals are queryable.

One live connector is the official FGIC National Gazetteer. It exposes bilingual UAE place names and coordinates through ArcGIS while omitting a known placeholder English-description field and retaining FGIC's informational-use disclaimer:

curl 'https://uaemcp.zad.tools/api/v1/sources/fgic_national_gazetteer/records?query=%D8%AF%D8%A8%D9%8A&limit=5'

Tool results use { ok, data, error, meta }. Data responses include source, license, citation, fetch time, completeness, sample coverage, source trust, freshness, schema stability, record-count trend and a composite quality score. Unknown measurements stay explicitly unknown until history can prove them.

Configuration

The scheduler starts with the HTTP server, runs immediately and then at the configured interval. Identical payloads are deduplicated. Inspect its state at GET /api/v1/operations/snapshot-scheduler.

Hosted public proxy

The same server can be offered as a public MCP endpoint for users who cannot self-host. Put it behind Nginx using deploy/nginx.conf, set the public host/origin allowlists, keep write tools disabled, and expose:

https://your-domain.example/mcp

The Nginx configuration disables buffering, caching, and compression on /mcp so Streamable HTTP responses are not delayed or rewritten.

Verify

bun run check
bun run benchmark
docker compose up --build

MIT licensed. See CONTRIBUTING.md and SECURITY.md. Connector authors should start with docs/CONNECTORS.md. See docs/API.md, docs/RECIPES.md, docs/DEPLOYMENT.md, docs/FAQ.md, and the runnable examples for the complete developer path. The security review is in docs/THREAT_MODEL.md, and the evidence-backed release audit is in docs/COMPLETENESS.md. The requirement-by-requirement status is tracked in docs/COMPLETENESS.md.