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 36 source-cited MCP tools, ten 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 Evidence Studio turns two to five existing official evidence pillars into one bilingual research dossier. Every card keeps its period, unit, scope, delivery mode, citation and limitations. It uses no generative model, stores no question or selection, and never adds unlike units, ranks pillars or invents a composite score. Use the hosted studio, POST /api/v1/evidence-dossier, or the uae_evidence_dossier MCP tool; print or download Markdown and JSON locally in the browser.

The UAE National Evidence Brief brings education, health, industry and FTA service activity into one evidence surface while keeping each source's original period, unit and limitations. It never adds the pillars together, ranks them or invents a composite national score. Use the hosted page, the REST endpoint, or the uae_national_evidence_brief MCP tool. See the MCP client setup guide for tested connection patterns.

The UAE Health Facilities Atlas exposes 950 official MOHAP aggregate rows covering 2015–2024, all seven emirates, government/private sectors and 42 raw facility-type labels. The default 2024 slice contains 120 rows and a reported count of 7,392. These are not individual facility locations, beds, capacity, workforce, accessibility or quality measurements. Use the hosted atlas, REST, or uae_health_facilities_atlas.

The UAE Founder Pathway composes three evidence products into one ordered, privacy-bounded action dossier: route to the competent setup authority, discover relevant government-backed support, then prepare entrepreneur Golden Residency evidence. Every task links to its official action, starts honestly as not begun, and can be checked in-memory, printed or downloaded as JSON without sending the checklist state to the server. It is planning—not licensing, programme acceptance or an eligibility decision.

The UAE Startup Support Navigator matches a founder's current stage, support need and location preference against nine official or government-backed programmes. It sends no name, email, phone, financial data, pitch deck or passport details, and treats every match as discovery—not eligibility, acceptance or funding approval.

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.

The Ajman Business Evidence Explorer turns three large official open-data views into bounded rankings for activities, areas, licence types and published status. It keeps every dataset separate: sampled rows are not added together as unique companies, market size, survival or investment performance.

The Ajman Urban Evidence Explorer publishes bounded observations from six official building, certified rent-contract and road datasets as separate source-native annual series. Units never collapse into a composite property score, investment return or growth claim.

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.

The Bun rewrite is currently newer than npm's latest tag. Until npm Trusted Publishing is connected, run the CI-tested main branch directly from GitHub:

bunx --bun github:ahmedvnabil/Open-Emirates-Intelligence-MCP#main --version
bunx --bun github:ahmedvnabil/Open-Emirates-Intelligence-MCP#main doctor
bunx --bun github:ahmedvnabil/Open-Emirates-Intelligence-MCP#main       # stdio MCP server
bunx --bun github:ahmedvnabil/Open-Emirates-Intelligence-MCP#main http # HTTP server at /mcp

The npm badge at the top of this README is the authoritative registry version. Use bunx uaemcp only after that badge reaches 1.66.0 or newer.

MCP client configuration:

{
  "mcpServers": {
    "uae-intelligence": {
      "command": "bunx",
      "args": ["--bun", "github:ahmedvnabil/Open-Emirates-Intelligence-MCP#main"]
    }
  }
}

From source:

bun install
bun src/index.ts stdio

Run the signed container

Prebuilt linux/amd64 and linux/arm64 images are published to GitHub Container Registry with an SBOM and build provenance:

docker run --rm -p 127.0.0.1:8080:8080 \
  -e UAEMCP_ALLOWED_HOSTS=127.0.0.1,localhost \
  ghcr.io/ahmedvnabil/open-emirates-intelligence-mcp:edge

Or use the hardened registry Compose file with a persistent SQLite volume, read-only root filesystem, dropped Linux capabilities and no-new-privileges:

docker compose -f compose.ghcr.yml up -d
curl http://127.0.0.1:8080/ready

Release tags such as :1.66.0 and :latest are produced from verified Git tags; :edge tracks the tested main branch.

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 Evidence Studio: GET /evidence-studio — compose two to five official evidence pillars into a source-cited dossier; API at POST /api/v1/evidence-dossier

• UAE Founder Pathway: GET /founder-pathway — build, track, print and export a privacy-bounded action dossier across official setup, startup support and entrepreneur residency readiness

• UAE Startup Support Navigator: GET /startup-support — privacy-first matching across nine official or government-backed support programmes by stage, support need and emirate

• 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

• Ajman Business Evidence: GET /ajman-business — three separately ranked official licence-data views with bounded sampling, citations and explicit non-market limitations

• Ajman Urban Evidence: GET /ajman-urban — six separate building, certified-rent and road series in source-native units with no composite score

• 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 — normalized bilingual official place-name search and mapped FGIC evidence; API at GET /api/v1/places

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

• UAE Health Facilities Atlas: GET /health-facilities — 950 aggregate MOHAP rows for 2015–2024, explicitly not a facility directory, beds, capacity or quality

• 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 41 official sources indexed, 9 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/places?q=%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.