# Uk Planning Data (npm · @pipeworx/mcp-uk-planning-data)

UK planning designations from planning.data.gov.uk, the MHCLG national planning data platform…

- Trust score: 82/100 (high trust)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- remote · `gateway.pipeworx.io`: 77/100, [markdown](https://verifymcp.io/servers/pipeworx-io-uk-planning-data/uk-planning-data-mcp.md), [page](https://verifymcp.io/servers/pipeworx-io-uk-planning-data/uk-planning-data-mcp)
- npm · `@pipeworx/mcp-uk-planning-data`: 82/100 (this document), [markdown](https://verifymcp.io/servers/pipeworx-io-uk-planning-data/pipeworx-mcp-uk-planning-data.md), [page](https://verifymcp.io/servers/pipeworx-io-uk-planning-data/pipeworx-mcp-uk-planning-data)

## Channel facts

- Registry: `npm`
- Package: `@pipeworx/mcp-uk-planning-data`
- Version: `0.2.0`
- Transport: `stdio`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-05.

- **Supply Chain Security**: 100/100
  - No malware found by supply-chain analysis.
  - No known CVEs affecting this package version or its production dependencies.
  - No install/post-install scripts declared.
  - No production dependencies, so there is no dependency health to assess.
- **Provenance & Transparency**: 97/100
  - Source repository is publicly reachable at the declared URL.
  - Cryptographically verified build provenance (signed, bound to pipeworx-io/mcp-uk-planning-data).
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 6 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 64/100
  - AI-judged instruction clarity (excellent).
  - 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.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 23/100
  - Stability observed for 7 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### 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.

### Claude

```bash
claude mcp add pipeworx-io-uk-planning-data -- npx -y @pipeworx/mcp-uk-planning-data
```

### Cursor

```json
{
  "mcpServers": {
    "pipeworx-io-uk-planning-data": {
      "command": "npx",
      "args": [
        "-y",
        "@pipeworx/mcp-uk-planning-data"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "pipeworx-io-uk-planning-data": {
      "command": "npx",
      "args": [
        "-y",
        "@pipeworx/mcp-uk-planning-data"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add pipeworx-io-uk-planning-data -- npx -y @pipeworx/mcp-uk-planning-data
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "pipeworx-io-uk-planning-data": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "@pipeworx/mcp-uk-planning-data"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add pipeworx-io-uk-planning-data --command npx --arg -y --arg @pipeworx/mcp-uk-planning-data
```

### Hermes

```yaml
mcp_servers:
  pipeworx-io-uk-planning-data:
    command: "npx"
    args: ["-y", "@pipeworx/mcp-uk-planning-data"]
```

### Netclaw

```json
{
  "McpServers": {
    "pipeworx-io-uk-planning-data": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "@pipeworx/mcp-uk-planning-data"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add pipeworx-io-uk-planning-data -t stdio -c npx -a -y @pipeworx/mcp-uk-planning-data
```

### Other

```json
{
  "mcpServers": {
    "pipeworx-io-uk-planning-data": {
      "command": "npx",
      "args": [
        "-y",
        "@pipeworx/mcp-uk-planning-data"
      ]
    }
  }
}
```

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-04 (score 82, +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.

### 2026-11-02 (score 81, +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.

### 2026-10-31 (score 80, +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.

### 2026-10-29 (score 79)

First indexed and scored.

## MCP tools (4)

### `ukplanning_datasets` (~225 tokens)

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" })

Input parameters:

- `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"

### `ukplanning_entities_at_point` (~255 tokens)

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 })

Input parameters:

- `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, required): Latitude in WGS84 decimal degrees, e.g. 51.5074
- `limit` (number): Maximum designations to return (default 25, max 100)
- `longitude` (number, required): Longitude in WGS84 decimal degrees, e.g. -0.1276

### `ukplanning_search` (~353 tokens)

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" })

Input parameters:

- `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"

### `ukplanning_entity` (~125 tokens)

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 })

Input parameters:

- `entity` (number, required): 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)

## Diagnostics

Captured diagnostic sections: Provenance, Dependencies. The full working is on the page: https://verifymcp.io/servers/pipeworx-io-uk-planning-data/pipeworx-mcp-uk-planning-data#diagnostics

## Score history

- 2026-11-05: 82
- 2026-11-04: 82
- 2026-11-03: 81
- 2026-11-02: 81
- 2026-11-01: 80
- 2026-10-31: 80
- 2026-10-30: 79
- 2026-10-29: 79

## Common questions

### 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.

### What did VerifyMCP test on the Uk Planning Data MCP server?

VerifyMCP ran 16 checks on Uk Planning Data, covering Malware scan, Known CVEs, Install scripts, Dependency health and 12 more. Endpoint Security and Transport & Reachability do not apply to an npm package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.

## Links

- npm package: https://www.npmjs.com/package/@pipeworx/mcp-uk-planning-data
- Socket report: https://socket.dev/npm/package/@pipeworx/mcp-uk-planning-data
- Repository: https://github.com/pipeworx-io/mcp-uk-planning-data
- Website: https://pipeworx.io/packs/uk-planning-data
- Changelog RSS feed: https://verifymcp.io/servers/pipeworx-io-uk-planning-data/pipeworx-mcp-uk-planning-data.xml
- Changelog JSON feed: https://verifymcp.io/servers/pipeworx-io-uk-planning-data/pipeworx-mcp-uk-planning-data/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/pipeworx-io-uk-planning-data/pipeworx-mcp-uk-planning-data.json
- HTML version of this page: https://verifymcp.io/servers/pipeworx-io-uk-planning-data/pipeworx-mcp-uk-planning-data