mcp · United Kingdom

scotland-opendata

Feature or claim this listing

Represent scotland-opendata? Send a claim for review so we can discuss listing updates. Claims do not automatically grant ownership or verification.

Data offered docs-verified: dataset catalogue metadata from data.gov.scot · statistics.gov.scot data cube observations served as rows · Spatial Hub Scotland catalogue (council WFS and ArcGIS REST services) · council open data catalogues (14 harvested councils) · live row-level queries proxied from CKAN datastore and SPARQL sources
Coverage docs-verified: Scotland
Formats docs-verified: MCP stdio · MCP streamable HTTP · REST API
Access llm-inferred: Read access appears open (no key documented for read endpoints or MCP tools). ADMIN_TOKEN is optional and only enables POST /v1/admin/sync. Licence MIT per entry metadata. The entry's 'API key' auth note overstates the requirement for reads.

Use cases llm-inferred: Locate council WFS or ArcGIS REST spatial layers for a site's local authority area · Check which councils publish open data for a project area before requesting data · Pull Scottish statistical observations for a socio-economic baseline in a planning or EIA statement · Find open datasets with live API endpoints for planning context layers
Audience llm-inferred: GIS analysts · planners · environmental consultants · data analysts

Constraints llm-inferred: Only 14 of 32 councils are harvested; 13 publish nothing on their council site and 4 have only a landing page · Dumfries and Galloway portal is not yet harvested · Angus and North Lanarkshire may fail to sync · Edinburgh, Glasgow, Dundee and Perth and Kinross have retired older CKAN portals · Council provision snapshot is dated 2026-10-14 and may drift · Datasets without an api resource are hidden from /v1/datasets and search_datasets unless requested · Row queries are proxied live, so results depend on upstream API availability · DuckDB allows one process per database file; run stdio and HTTP servers with separate CATALOGUE_DB files · Resolution, update frequency and time span are not stated

Auto-extracted, unverified fields: tools, install, auth. Check upstream documentation.

Daily discovery 2026-10-18: GitHub search; verified via GitHub API. Tools/install/auth auto-extracted from README.

Metadata observed 14/10/2026 · daily-2026-10-18 (github-search)