Open Emirates Intelligence
The Emirates, queryable.
Official UAE open data for agents, researchers and builders—over MCP, REST, vector maps and six SDKs.
Maintained by Ahmed Morsy. Released under the MIT license and built on theoriginal open-source UAEMCP work credited in LICENSE.
Open Emirates is an independent open-source initiative. It is not affiliatedwith or endorsed by the UAE Government. Every data product identifies itsofficial source, evidence boundary, retrieval date and available licence terms.
Live instances
| Instance | URL | What it serves |
|---|---|---|
| Cloudflare Worker (production) | uae-open-data.zadstack.com | Every public page, REST /api/v1/*, MCP at /mcp (requires X-API-Key), liveness at /health, contract at /openapi.json |
| Static edition (Maarad canvas) | maarad.zadstack.com/c/uae-mcp | A static export of all 27 public pages with retained JSON snapshots; filters, forms and the MCP console call the Worker live |
The static edition is read-only and rebuilt from this repository. Its retainedsnapshots carry the retrieval time of the export; anything fresher, and everyPOST, is fetched from the Worker, which allows the canvas origin throughUAEMCP_ALLOWED_ORIGINS.
Independent packages
The repository is now a monorepo with separate release lines:
@open-emirates/contractsfor dependency-free response contracts.@open-emirates/sdkfor a hybrid TypeScript client with generated tool types,runtime Schema 2.1 discovery, local validation, bounded retries and pagination.@open-emirates/mcpfor the MCP stdio and Streamable HTTP entry point.uaemcpremains the compatible engine and existing CLI during migration.
The SDK has no MCP dependency. Package boundaries and publishing instructionsare documented in docs/PACKAGES.md.
import { OpenEmiratesClient } from "@open-emirates/sdk";
const client = new OpenEmiratesClient();
const result = await client.tools.call("uae_golden_residency", { action: "list" });
Known tools receive compile-time autocomplete; newer server tools remain callablethrough dynamic discovery. Golden Residency output is informational official-routeguidance, not an eligibility or residence decision.
The server keeps the public uaemcp contract and extends it to 46 source-citedMCP tools, seventeen resources, three prompts, bilingual catalog search, CKAN,OpenDataSoft, ArcGIS, Socrata, JSON, CSV, XLSX, XML, RSS, GraphQL, SDMX andSPARQL connectors, geo queries,aggregation, PII redaction, SSRF protection, andhealth/readiness/Prometheus endpoints. Bun SQLite stores health history andbounded dataset snapshots for repeatable comparisons.
Agents can start with three stable facades instead of learning the completespecialist surface: uae_discover finds local catalog evidence without livefan-out by default, uae_query reads and shapes source data, and uae_analyzecomposes methodology-backed indicators, recipes and dossiers. Existing toolsremain available. Set UAEMCP_TOOL_PROFILE=core to publish only the six coreagent tools, or use research, geo and full profiles.
The public gateway is fully bilingual: navigation, product evidence, catalog,connectors, dataset discovery, playground controls and runtime states switchbetween English and Arabic. Every public application uses Dubai Font with nativeRTL composition.
The MOHRE Employment by Gender ledger publishes ten validated annual ratioobservations for employees registered in MOHRE private-sector systems from2020–2024. It keeps male and female shares separate, never converts ratios intoemployee counts, and does not claim whole-workforce coverage, pay equity,causality or forecasts. Use thehosted ledger,GET /api/v1/employment-gender, or the uae_employment_gender MCP tool.
The UAE Tourism Pulse presents five official national annual aggregates asseparate source-native series with metric and year-range filters. Guest countsare not presented as unique tourists, year-to-year movement is descriptive—notcausal—and occupancy is transparently displayed as a percentage by multiplyingthe published source fraction by 100. It does not create a tourism score orinfer emirate, hotel, traveller or market-segment detail. Use thehosted pulse,GET /api/v1/tourism-pulse, or the uae_tourism_pulse MCP tool.
The UAE Aeronautical Publications ledger reads the current GCAA eAIPpublication index and keeps each package, publication and effective date tied toits source description. AIRAC amendments and supplements can be filteredwithout interpreting regulatory effect, airspace, routes or safety. This is adiscovery index—not NOTAM, flight-planning guidance or a substitute for thecurrent official AIP package. Use thehosted ledger,GET /api/v1/aeronautical-publications, or theuae_aeronautical_publications MCP tool.
The UAE Health Facilities Map exposes the second GIS sheet in MOHAP'sofficial 2026 workbook: 15,326 published rows, of which 7,471 containcoordinates inside a conservative UAE frame. It reports and excludes the other7,855 rows—2,671 blank coordinates, 1,102 90,90 sentinels and 4,082 malformedor out-of-frame values—instead of guessing locations. Names and coordinates donot establish facility type, licence, ownership, current operation, services,capacity, accessibility or quality. Use thehosted map,GET /api/v1/health-facilities-map, or uae_health_facilities_map.
The UAE Connectivity Pulse publishes three separate official TDRA monthlyseries from January 2011 through December 2025: active mobile subscriptions,broadband internet subscriptions per 100 inhabitants, and fixed lines per 100inhabitants. It does not add unlike units or create a connectivity score.Subscriptions are not unique people, and per-100 observations do not measurecoverage, speed, quality, affordability or digital inclusion. Use thehosted ledger, REST, or theuae_connectivity_pulse MCP tool.
The Ajman Parks Footfall product reads the complete official 2017–2023monthly observation dataset, groups valid published visits by year andsource-native park label, and exposes malformed exclusions. Visits are neverpresented as unique people, resident demand, tourism performance, satisfaction,capacity or park quality. Use thehosted explorer, REST, or theuae_ajman_parks_footfall MCP tool.
The UAE Policy Evidence Watch checks five audited official legislation,resolution and announcement surfaces. It retains SHA-256 fingerprints, boundedexcerpts and check observations—not full government pages. A detected pagecontent change is evidence for review; it is never presented as a legal change,effective date or eligibility decision. Use thehosted watch, REST, or theuae_policy_evidence_watch MCP tool.
The UAE Evidence Studio turns two to five existing official evidence pillarsinto one bilingual research dossier. Every card keeps its period, unit, scope,delivery mode, citation and limitations. It uses no generative model, stores noquestion or selection, and never adds unlike units, ranks pillars or invents acomposite score. Use the hosted studio,POST /api/v1/evidence-dossier, or the uae_evidence_dossier MCP tool; print ordownload Markdown and JSON locally in the browser.
The UAE National Evidence Brief brings education, health, industry and FTAservice activity into one evidence surface while keeping each source's originalperiod, unit and limitations. It never adds the pillars together, ranks them orinvents a composite national score. Use the hosted page,the REST endpoint, or the uae_national_evidence_brief MCP tool. See theMCP client setup guide for tested connection patterns.
The UAE Health Facilities Atlas exposes 950 official MOHAP aggregate rowscovering 2015–2024, all seven emirates, government/private sectors and 42 rawfacility-type labels. The default 2024 slice contains 120 rows and a reportedcount of 7,392. These are not individual facility locations, beds, capacity,workforce, accessibility or quality measurements. Use thehosted atlas, REST, oruae_health_facilities_atlas.
The UAE Founder Pathway composes three evidence products into one ordered,privacy-bounded action dossier: route to the competent setup authority, discoverrelevant government-backed support, then prepare entrepreneur Golden Residencyevidence. 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 thechecklist state to the server. It is planning—not licensing, programme acceptanceor an eligibility decision.
The UAE Startup Support Navigator matches a founder's current stage, supportneed and location preference against nine official or government-backedprogrammes. It sends no name, email, phone, financial data, pitch deck orpassport details, and treats every match as discovery—not eligibility,acceptance or funding approval.
The UAE Business Setup Navigator routes founders to the competent officialmainland authority or federal free-zone directory across all seven emirates. Itdoes not collect names, phone numbers, emails or passport data, and neverpretends to choose a licence, calculate final fees or guarantee approval.
The Ajman Business Evidence Explorer turns three large official open-dataviews into bounded rankings for activities, areas, licence types and publishedstatus. It keeps every dataset separate: sampled rows are not added together asunique companies, market size, survival or investment performance.
The Ajman Urban Evidence Explorer publishes bounded observations from six official building, certifiedrent-contract and road datasets as separate source-native annual series. Unitsnever collapse into a composite property score, investment return or growthclaim.
Hosted endpoint
{
"mcpServers": {
"uae-intelligence": {
"type": "http",
"url": "https://uae-open-data.zadstack.com/mcp",
"headers": { "X-API-Key": "oe_…" }
}
}
}
Open Emirates Pro (hosted plan)
The hosted /mcp endpoint requires an API key; the public REST routes under/api/v1 stay free with a per-IP rate limit — they always stay that way. Open Emirates Pro adds a personal API key with a metered monthly quota(10,000 calls/month) and no per-IP throttling, for agents and applications inproduction. The code stays MIT: self-hosting always remains free and unmetered.
- Subscribe: zadstack.com — Open Emirates Pro
- Your key and live usage: zadstack.com/my-key
- Use it by sending
X-API-Key: oe_…on/mcpand every REST route; checkusage anytime viaGET /pro/usage(never billed).
Self-hosters can run the same metering layer against their own control plane —see the SAASPRESS_* and UAEMCP_PRO_* variables in .env.example; leavingthem unset disables the paid layer entirely.
Run with Bun
Requires Bun 1.3 or newer.
The signed npm package is published from GitHub Actions through npm TrustedPublishing, with provenance and no long-lived release token:
bunx --bun uaemcp@latest --version
bunx --bun uaemcp@latest doctor
bunx --bun uaemcp@latest # stdio MCP server
bunx --bun uaemcp@latest http # HTTP server at /mcp
The npm badge at the top of this README is the authoritative registry version.
MCP client configuration:
{
"mcpServers": {
"uae-intelligence": {
"command": "bunx",
"args": ["--bun", "uaemcp@latest"]
}
}
}
From source:
bun install
bun src/index.ts stdio
Run the signed container
Prebuilt linux/amd64 and linux/arm64 images are published to GitHub ContainerRegistry 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/zadstack/uaemcp: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.84.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 /healthor/healthz - Readiness:
GET /readyor/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}/tilejsonand/tiles/{z}/{x}/{y}.pbf - Public Observatory:
GET /observatory— source reliability, incidents and evidence reports - UAE Policy Evidence Watch:
GET /policy-watch— retained hashes, bounded excerpts and change observations for five audited official surfaces; API atGET /api/v1/policy-watchand bounded checks atPOST /api/v1/policy-watch/check - UAE Evidence Studio:
GET /evidence-studio— compose two to five official evidence pillars into a source-cited dossier; API atPOST /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 - Ajman Parks Footfall:
GET /ajman-parks— official 2017–2023 monthly park-visit observations with complete pagination and a visits-not-people boundary; API atGET /api/v1/ajman-parks - 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 atGET /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. StructuredAPI 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.1contract at /openapi.json:
bun run generate:sdks
bun run check:sdks
The second command fails when an API change has not been propagated to everylanguage. It is included in the main release check.
MCP tools
The authoritative tool catalogue is generated directly from the registeredruntime, so names, descriptions and access kinds cannot silently drift from theserver:
- Readable catalogue
- Machine-readable catalogue
- MCP resource:
uae://tools - Public bilingual MCP Developer Console (also
/mcp/tools) with schemas, examples, safe Try-it and client configuration - REST contracts:
GET /api/v1/tools·GET /api/v1/tools/{toolName}·POST /api/v1/tools/{toolName}/call
bun run generate:tools
bun run check:tools
The second command is part of the release gate and fails when either generatedcatalogue is stale.
FTA archive REST mirror: GET /api/v1/tax-services/archive. It returns the2017–2022 selected-services table, the source-native 2024 monthly table, and the2025 quarterly table as separate cited views. comparison.status isunavailable: 2023 is missing and the published scopes and schemas are notequivalent, 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/coveragefor live, blocked, key-required and metadata-only totals.GET /api/v1/catalogfor explicit portal, organization, connector, license and capability models.GET /.well-known/uaemcp.jsonfor the operator and trust manifest.GET /api/v1/sources/{sourceId}/schemaoruae_dataset_schemabefore aggregation.GET /api/v1/sources/{sourceId}/health-historyfor uptime and latency history.GET|POST /api/v1/sources/{sourceId}/snapshotsandGET /api/v1/snapshots/difffor dataset history.GET /api/v1/intelligence/recipesto discover analytical recipes and run them by id.
Current conservative coverage is 48 official sources indexed, 16 live recordconnectors, at least 222 known queryable datasets, 1 blocked connector, and 3key-required portals. Counts never implythat metadata-only portals are queryable.
One live connector is the official FGIC National Gazetteer. It exposesbilingual UAE place names and coordinates through ArcGIS while omitting a knownplaceholder English-description field and retaining FGIC's informational-use disclaimer:
curl 'https://uae-open-data.zadstack.com/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
| Variable | Default | Meaning |
|---|---|---|
UAEMCP_HOST |
127.0.0.1 |
HTTP bind host |
UAEMCP_PORT |
8080 |
HTTP port |
UAEMCP_WRITE_TOKEN |
unset | Enables the write tool |
UAEMCP_HTTP_TIMEOUT |
8 |
Upstream timeout in seconds |
UAEMCP_HEALTH_TIMEOUT |
5 |
Health timeout in seconds |
UAEMCP_CACHE_TTL |
300 |
Dashboard cache TTL in seconds |
UAEMCP_STALE_WHILE_REVALIDATE |
1800 |
Serve stale health/snapshots immediately while one background refresh runs |
UAEMCP_TOOL_PROFILE |
full |
MCP surface: core, research, geo, or backwards-compatible full |
UAEMCP_MAX_RESPONSE_BYTES |
5242880 |
Maximum upstream response size |
UAEMCP_ALLOW_PRIVATE_HOSTS |
false |
Allow private upstream hosts |
UAEMCP_ALLOWED_HOSTS |
unset | Comma-separated public host allowlist |
UAEMCP_ALLOWED_ORIGINS |
unset | Browser origin allowlist; use * only for fully public reads |
UAEMCP_RATE_LIMIT_PER_MINUTE |
120 |
Per-client public request limit; 0 disables it |
UAEMCP_DATABASE_PATH |
data/uaemcp.sqlite |
Durable health-history and snapshot database |
UAEMCP_HEALTH_RETENTION |
10000 |
Maximum stored health checks per source |
UAEMCP_HEALTH_SCAN_INTERVAL_MINUTES |
0 |
Periodic Observatory scan; hosted deployment uses 60 |
UAEMCP_SNAPSHOT_RETENTION |
30 |
Maximum changed snapshots per source/dataset |
UAEMCP_SNAPSHOT_INTERVAL_MINUTES |
0 |
Snapshot schedule; 0 disables it |
UAEMCP_SNAPSHOT_TARGETS |
unset | Comma-separated source or source@dataset targets |
UAEMCP_SNAPSHOT_LIMIT |
100 |
Records captured per scheduled target |
UAEMCP_EMBEDDING_ENDPOINT |
unset | Optional OpenAI-compatible /embeddings endpoint for hybrid reranking |
UAEMCP_EMBEDDING_MODEL |
text-embedding-3-small |
Embedding model sent to that endpoint |
UAEMCP_EMBEDDING_API_KEY |
unset | Optional bearer token for the embedding endpoint |
The scheduler starts with the HTTP server, runs immediately and then at theconfigured interval. Identical payloads are deduplicated. Inspect its state atGET /api/v1/operations/snapshot-scheduler.
Hosted public proxy
The same server can be offered as a public MCP endpoint for users who cannotself-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 /mcpso 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 therunnable examples for the complete developer path.The security review is in docs/THREAT_MODEL.md, and theevidence-backed release audit is in docs/COMPLETENESS.md.The requirement-by-requirement status is tracked in docs/COMPLETENESS.md.