Open Emirates Intelligence
The Open Emirates Intelligence server provides secured, source-cited access to official UAE open government data, with built-in PII redaction and SSRF protection.
List all sources (
uae_sources_list): Enumerate every registered official UAE open-data source and its metadata.Get source details (
uae_source_get): Retrieve full metadata for a specific source by ID.Check source health (
uae_source_health): Run a live, timeout-bounded health probe on a source to verify it is reachable.Fetch records (
uae_source_records): Retrieve live records with automatic PII (phone/email) redaction and source citations. Supports optional keyword querying and result limits.Market snapshot (
uae_market_snapshot): Generate aggregated counts by emirate, area, or product for a given topic (default: industry).Dashboard summary (
uae_dashboard_summary): Run concurrent, cached health checks across all registered sources for a fast ecosystem-wide overview.Add custom sources (
uae_source_add_metadata): Register a new metadata-only source into the local registry. Requires a write token; disabled by default if none is set.
Deployment & Access: Supports stdio and HTTP transports. Use the public hosted instance at https://uaemcp.zad.tools or self-host via npm, Docker, or from source. All tools are also mirrored as REST endpoints under /api/v1/ with interactive Swagger documentation.
Provides tools for discovering datasets and fetching records from ArcGIS portals hosting UAE open data.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@Open Emirates Intelligence show me the latest real estate market snapshot"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
A standalone MCP server that gives any MCP client (Claude Desktop, Claude Code, Cursor) source-cited access to official UAE open data — with direct-contact PII redacted, every server-side fetch SSRF-guarded, and both stdio and HTTP transports in one package.
It is self-contained: no dependency on any private or sibling service. Ships in two
flavors at feature parity — a Python implementation (this directory) and a
TypeScript / npm port (ts/), published as
uaemcp (v0.2.0). Both expose the same
11 MCP tools, resources, and prompts.
Two ways to use it
Open source under the MIT license — use the instance we host, or run your own.
1. Use our hosted instance — zero setup
A public instance is live at https://uaemcp.zad.tools. Point any MCP client at its endpoint — nothing to install:
{
"mcpServers": {
"uae-intelligence": {
"type": "http",
"url": "https://uaemcp.zad.tools/mcp"
}
}
}Or just open the dashboard: https://uaemcp.zad.tools
2. Self-host it — run your own, anywhere
npm, no install:
npx uaemcp(stdio) ·npx uaemcp http(HTTP at/mcp)Docker:
docker build -t uaemcp . && docker run -p 8080:8080 uaemcp uaemcp httpFrom source: clone this repo (Python below, or the TypeScript port in
ts/)
Self-hosting gives you full control: add your own sources, set a write token, and keep every fetch on your own infrastructure.
Related MCP server: io.github.raheb77/saudi-open-data-mcp
Quickstart
Fastest — via npm (no install)
npx uaemcp # stdio MCP server
npx uaemcp http # Streamable-HTTP server at /mcpLatest release: v0.2.0 — published to npm with provenance via GitHub Actions OIDC (no tokens).
npx uaemcpalways fetches it.
Local (stdio) — for an MCP client
The published npm package is the easiest way to run it in a client:
{
"mcpServers": {
"uae-intelligence": { "command": "npx", "args": ["-y", "uaemcp"] }
}
}To run the Python implementation from source instead:
pip install -e .
uaemcp stdioRemote (HTTP) — landing page + REST + MCP endpoint
uaemcp http --host 0.0.0.0 --port 8080Landing page:
http://localhost:8080/REST API:
http://localhost:8080/api/v1/...— full API reference → APIs.mdMCP (Streamable):
http://localhost:8080/mcpObservability:
/health·/ready·/metrics(Prometheus) — plus cheap/healthz,/readyz
Showcase
The hosted dashboard is bilingual (EN / العربية) and styled with the official Dubai Font:
Interactive API docs — Dubai-Font-themed Swagger UI at /docs:
Tools
Tool | Kind | Description |
| read | List every registered official source |
| read | Full metadata for one source |
| read | Live, timeout-bounded health probe |
| read | Discover datasets inside a portal (CKAN/ODS/ArcGIS) |
| read | Live, redacted, cited records (per dataset) |
| read | Federated bilingual search across the catalog |
| read | Spatially-filtered records as GeoJSON (maps) |
| read | group_by + count/sum/avg/min/max |
| read | Counts by emirate / area / product |
| read | Concurrent, cached health across all sources |
| write | Add a metadata source (token required) |
Every data-returning tool wraps results in { ok, data, error, meta } and attaches
source_id, license, citation, fetched_at, and a data_quality
{ confidence, warnings, validation } block. Multi-dataset portals expose their
datasets via uae_source_datasets; pass a returned id as the dataset
argument to uae_source_records.
Source status (honest by design)
32 official sources are registered. Data is never fabricated — each source is typed by what it can actually return:
Live records, no key: MOIAT industrial licenses (
http_json) and Ajman (ods, 211 datasets). Any ArcGIS FeatureServer you wire works too.Key-gated official APIs (
requires_api_key): Dubai Pulse / DLD real-estate transactions, Abu Dhabi Open Data — supply a developer key to enable them.Metadata / discovery-only: everything else — a portal with no reachable machine API returns an actionable error, not empty-looking success.
Usage examples
Ask your MCP client (natural language)
Once connected, just ask — the client picks the right tool:
"List UAE industrial factories licensed in Abu Dhabi." →
uae_source_records"Find official UAE datasets about real estate." →
uae_search"Map licensed factories within 60 km of Abu Dhabi." →
uae_source_geo"Break down industrial licenses by emirate." →
uae_source_aggregate"Which official UAE open-data sources can you access?" →
uae_sources_list"Is the Dubai Land Department data source up right now?" →
uae_source_health
Call a tool over HTTP (Streamable-HTTP MCP)
# initialize → grab the mcp-session-id header, then call tools/list, tools/call
curl -s -X POST https://uaemcp.zad.tools/mcp/ \
-H 'Content-Type: application/json' \
-H 'Accept: application/json, text/event-stream' \
-d '{"jsonrpc":"2.0","id":1,"method":"tools/call",
"params":{"name":"uae_market_snapshot","arguments":{"topic":"industry","limit":50}}}'Or hit the REST mirror directly
# 32 registered sources
curl -s https://uaemcp.zad.tools/api/v1/sources | jq '.meta.total'
# live, PII-redacted records from the MOIAT industrial-licenses API
curl -s 'https://uaemcp.zad.tools/api/v1/sources/moiat_industrial_licenses/records?limit=2'
# discover datasets in a multi-dataset portal (Ajman = OpenDataSoft, 211 datasets)
curl -s 'https://uaemcp.zad.tools/api/v1/sources/ajman_data_portal/datasets?limit=5'
# then fetch live records from one of those datasets
curl -s 'https://uaemcp.zad.tools/api/v1/sources/ajman_data_portal/records?dataset=developed-crossroads&limit=3'
# federated bilingual search (deep = also search live portal datasets)
curl -s 'https://uaemcp.zad.tools/api/v1/search?q=real%20estate&deep=true'
# GeoJSON for map apps — factories within 60 km of Abu Dhabi
curl -s 'https://uaemcp.zad.tools/api/v1/sources/moiat_industrial_licenses/geo?near=24.45,54.37,60'
# aggregate: licensed factories grouped by emirate
curl -s 'https://uaemcp.zad.tools/api/v1/sources/moiat_industrial_licenses/aggregate?group_by=EmirateNameEN'
# export records as csv | geojson | xlsx | json
curl -s -OJ 'https://uaemcp.zad.tools/api/v1/sources/moiat_industrial_licenses/export?format=geojson'Full parameter tables + real response examples for every endpoint are in the API reference (APIs.md).
// sample record (contact fields are redacted by default)
{
"CompanyName": "…",
"EmirateNameEN": "Abu Dhabi",
"AreaNameEN": "Musaffah Industrial",
"ContactPhone": "[redacted-open-data-contact]",
"ContactEmail": "[redacted-open-data-contact]"
}Interactive API docs (Dubai-Font themed Swagger UI): https://uaemcp.zad.tools/docs
Security model
Writes gated. Reads are open; mutating tools require
UAEMCP_WRITE_TOKEN. No token set → writes are disabled entirely (safe default).SSRF guard. Every fetch resolves the host and rejects private, loopback, link-local, and cloud-metadata addresses. See
core/ssrf.py.PII redaction. Phone/email fields are redacted by name and by value pattern before any record leaves the server.
Bounded fetches. Browser-like User-Agent (so bot-mitigated portals don't hang), strict timeouts, capped redirects and response size.
Design notes — what this fixes vs. the prior version
No auth on writes → token-gated writes, disabled by default.
SSRF surface → mandatory
validate_urlon every egress.stdio-only → real remote MCP at
/mcp.dashboard-summarystall → checks run concurrently with a strict per-source timeout and a browser UA, served from cache, with DNS resolved off the event loop so the fan-out truly overlaps. Worst case is the slowest single source, not the sum of all.Cold-start 502 →
/healthzand/readyzdo no upstream work.
Development
pip install -e ".[dev]"
pytest -m "not network" # offline unit tests (ssrf, redaction, dashboard)
pytest # include live-endpoint integration tests
ruff check . && mypy srcLicense
MIT. Data served is open government data — verify each source's terms before redistribution.
Available Tools
11 toolsuae_dashboard_summaryA
Concurrent, cached health snapshot across all sources (fast, never stalls).
Inputs: no named parameters. Returns: object
uae_market_snapshotC
Build a source-backed market snapshot (counts by emirate/area/product).
Inputs: limit, topic. Returns: object
uae_searchA
Federated bilingual (ar/en) search across the catalog.
Ranks official sources by relevance. With deep=true it also searches each
portal's live dataset catalogue (OpenDataSoft/CKAN/ArcGIS) so individual
datasets surface — ideal for a dataset-discovery agent.
Inputs: query (required), deep, limit. Returns: object
uae_source_add_metadataC
[WRITE — requires token] Add a metadata-only source to the local registry.
Inputs: id (required), owner (required), name_ar (required), name_en (required), +5 more. Returns: object
uae_source_aggregateB
Group records and reduce with count|sum|avg|min|max.
group_by is a comma-separated list of fields (dotted paths allowed, e.g.
"Products.ProductNameEN"). A generalized form of uae_market_snapshot.
Inputs: group_by (required), source_id (required), top, limit, +4 more. Returns: object
uae_source_datasetsB
List the datasets inside a multi-dataset portal (CKAN/OpenDataSoft/ArcGIS).
Simple single-dataset sources (like MOIAT) return one entry. Use the returned
id as the dataset argument to uae_source_records.
Inputs: source_id (required), limit, query, offset. Returns: object
uae_source_geoA
Spatially-filtered records as GeoJSON — powers map apps.
bbox = "min_lon,min_lat,max_lon,max_lat"; near = "lat,lon,radius_km".
Works on any source with coordinates (e.g. MOIAT industrial licenses).
Inputs: source_id (required), bbox, near, limit, +2 more. Returns: object
uae_source_getC
Get the full metadata for one source by id.
Inputs: source_id (required). Returns: object
uae_source_healthC
Run a live, timeout-bounded health probe for one source.
Inputs: source_id (required). Returns: object
uae_source_recordsA
Fetch up to limit live, redacted, source-cited records from a source.
For multi-dataset portals pass dataset (an id from uae_source_datasets).
Every response carries provenance + a data-quality block in meta.
Inputs: source_id (required), limit, query, offset, +1 more. Returns: object
uae_sources_listA
List every registered official UAE open-data source with its metadata.
Inputs: no named parameters. Returns: object
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 11 tools
Each tool has a clearly distinct purpose: dashboard summary, market snapshot, search, source management (add, list, get, health), data retrieval (records, datasets, geo), and aggregation. No ambiguity between tools.
Tools consistently use the 'uae_' prefix. Most tools follow a 'uae_source_<action>' pattern, though 'uae_dashboard_summary' and 'uae_market_snapshot' deviate slightly. Overall pattern is predictable.
With 11 tools, the set is well-scoped for an open data intelligence server. Each tool serves a specific function without redundancy, and the count feels appropriate for the complexity of the domain.
The tool set covers core operations: search, catalog browsing, data retrieval, aggregation, and health checks. It lacks update/delete for sources, but for a read-heavy intelligence service, this is a minor gap.
Maintenance
Related MCP Connectors
The world's public data, one API. License-cleared public data sources for agents, via MCP and REST.
Agent-native MCP server over 49M+ US public and government records, privacy-first, always current.
This MCP server provides seamless access to Malaysia's government open data, including datasets, w…
Official UK, US and Australia public datasets as filtered CSV, REST API and MCP for AI agents.
Related MCP Servers
- AlicenseBqualityBmaintenanceAn MCP server that provides AI agents with access to Dubai and UAE public data (prayer times, exchange rates, school ratings, etc.) and curated business setup knowledge for entrepreneurs.12043 PyPI6MIT
- AlicenseAqualityDmaintenanceA governed MCP server for Saudi open data sources (SAMA, stats.gov.sa, Ministry of Finance, data.gov.sa), providing typed contracts, registry-backed metadata, and CLI/API access for dataset search, preview, and controlled export.77Apache 2.0
- AlicenseAqualityFmaintenanceEnables querying British cybersecurity data, including regulations, decisions, and requirements from the NCSC, directly from any MCP-compatible client.81Apache 2.0
- AlicenseAqualityBmaintenanceUnifies 24 Dutch public-sector data sources into a single MCP interface, enabling AI assistants to search, combine, and retrieve structured data with provenance and cross-source linking.46431Apache 2.0