Uk Planning Data
NPM · @PIPEWORX/MCP-UK-PLANNING-DATA · 2 COMPONENTS
UK planning designations from planning.data.gov.uk, the MHCLG national planning data platform…
Available components
Last scanned (10 hours ago)
Scores higher than 72% of npm servers
Category Maps and Location
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security100
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- No production dependencies, so there is no dependency health to assess. View diagnostics → Pass
Provenance & Transparency97
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to pipeworx-io/mcp-uk-planning-data). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 6 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability64
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 1015 tokens (~253/item across 4 items; 4 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management23
- Stability observed for 7 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 4 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.
- 2 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.
- 31 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.
- 29 Oct 26 79
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 5 Nov 2026 · Analysed npm/@pipeworx/mcp-uk-planning-data@0.2.0
Provenance Verified
A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.
| Result | Verified |
|---|---|
| Ecosystem | npm |
| Reason | Verified |
| Discovered via | Registry attestation endpoint |
| Source repo | pipeworx-io/mcp-uk-planning-data |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/pipeworx-io/mcp-uk-planning-data/.github/workflows/publish.yml@refs/heads/main |
| Rekor log index | 3560656200 |
| Predicate type | SLSA build provenance https://slsa.dev/provenance/v1 |
| Subject digest | sha512:aa9e50e49ad6b505379b885ef7bfcedd610b66ca84e2d7f52574a1b856d581e60fbf18c11dcfe8c485b0126f9623539846255dcb9b38612464c1ad950 |
Background: How many MCP packages publish verified provenance →
Dependencies 0 packages
| Packages resolved | 0 |
|---|---|
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
ukplanning_datasets ~225
List the datasets published on planning.data.gov.uk — the UK government's national planning data platform (MHCLG). Each row gives the dataset slug you pass to the other tools, its plain-English name, typology, licence and the number of entities it holds. AUTHORITATIVE for "what UK planning designations can I look up" — conservation areas, listed buildings, article 4 directions, green belt, brownfield land, flood risk zones, tree preservation zones and ~70 more. PREFER OVER WEB SEARCH for the dataset slug; guessing a slug returns an empty set, not an error. Example: ukplanning_datasets({ query: "conservation" })
| Name | Type | Req | Description |
|---|---|---|---|
| headline_only | boolean | – | Only return the ~17 designations most used for property and site due diligence (default false) |
| query | string | – | Optional case-insensitive substring matched against the dataset slug, name and description (filtered here, not upstream) |
| typology | string | – | Optional typology filter, e.g. "geography", "category", "organisation", "document" |
No output schema declared.
No examples provided.
ukplanning_entities_at_point ~255
Return every UK planning designation whose boundary covers one latitude/longitude — the single most useful call for site or property due diligence. Answers "is this address in a conservation area / green belt / flood risk zone", "is there an article 4 direction here", "which local planning authority is this". Pass a dataset to restrict to one layer, or omit it to get every layer at once. AUTHORITATIVE, sourced from the publishing local authorities via planning.data.gov.uk. Example: ukplanning_entities_at_point({ latitude: 51.5074, longitude: -0.1276 })
| Name | Type | Req | Description |
|---|---|---|---|
| dataset | string | – | Optional dataset slug from ukplanning_datasets to restrict to one layer, e.g. "conservation-area" |
| include_geometry | boolean | – | Include the full WKT boundary of each designation (default false — a single area can be 60 KB of coordinates) |
| latitude | number | yes | Latitude in WGS84 decimal degrees, e.g. 51.5074 |
| limit | number | – | Maximum designations to return (default 25, max 100) |
| longitude | number | yes | Longitude in WGS84 decimal degrees, e.g. -0.1276 |
No output schema declared.
No examples provided.
ukplanning_entity ~125
Fetch one UK planning entity by its numeric entity id (from ukplanning_search or ukplanning_entities_at_point). Returns the full record — name, dataset, publisher reference, start/end dates, the publisher's documentation URL — and the WKT boundary when asked for. Example: ukplanning_entity({ entity: 44000001, include_geometry: false })
| Name | Type | Req | Description |
|---|---|---|---|
| entity | number | yes | Numeric planning.data.gov.uk entity id, e.g. 44000001 |
| include_geometry | boolean | – | Include the full WKT boundary (default false — can be tens of KB) |
No output schema declared.
No examples provided.
ukplanning_search ~353
Filter UK planning entities by dataset, typology, publisher reference, curie or publishing organisation. NOTE: planning.data.gov.uk has NO free-text search — its documented `q` parameter is silently ignored upstream and returns the whole 25-million-row platform, so this tool does not accept one. To find a designation by place, use ukplanning_entities_at_point instead. Use this for "list the conservation areas published by organisation X", "which entity has reference CA18", "how many brownfield-land records exist". Example: ukplanning_search({ dataset: "conservation-area", reference: "CA18" })
| Name | Type | Req | Description |
|---|---|---|---|
| curie | string | – | Prefixed reference in "prefix:reference" form, e.g. "conservation-area:CA18" |
| dataset | string | – | Dataset slug from ukplanning_datasets, e.g. "conservation-area", "listed-building", "green-belt" |
| entry_date_year | number | – | Restrict to records first entered in this year, e.g. 2026 |
| include_geometry | boolean | – | Include the full WKT boundary of each row (default false) |
| limit | number | – | Maximum rows to return (default 25, max 100) |
| offset | number | – | Row offset for paging (default 0) |
| organisation_entity | number | – | Entity id of the publishing organisation (a local planning authority), e.g. 278 |
| reference | string | – | The publisher's own reference for the entity, e.g. "CA18". NOT unique across councils — pair with organisation_entity |
| typology | string | – | Typology filter, e.g. "geography", "category", "organisation" |
No output schema declared.
No examples provided.
How do I install the Uk Planning Data MCP server?
Uk Planning Data runs locally as an npm package, launched with npx -y @pipeworx/mcp-uk-planning-data. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · @pipeworx/mcp-uk-planning-data
claude mcp add pipeworx-io-uk-planning-data -- npx -y @pipeworx/mcp-uk-planning-data
What is the Uk Planning Data MCP server?
Uk Planning Data is an MCP server listed in the public MCP registry as io.github.pipeworx-io/uk-planning-data. UK planning designations from planning.data.gov.uk, the MHCLG national planning data platform… This page covers its npm package (@pipeworx/mcp-uk-planning-data).
Is the Uk Planning Data MCP server safe to use?
Uk Planning Data scores 82 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 November 2026. It declares no install or post-install scripts. Its build provenance is signed and verified. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the Uk Planning Data MCP server expose?
Uk Planning Data exposes 4 tools: ukplanning_datasets, ukplanning_entities_at_point, ukplanning_search, ukplanning_entity. Their descriptions and schemas cost roughly 958 tokens of context every time the server is loaded.
Is the Uk Planning Data MCP server still maintained?
Uk Planning Data is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the Uk Planning Data MCP server under?
Uk Planning Data declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.