- Data
- MCP server
- Planning
- Chosen planning designation checks
Chosen planning designation checks
planning_checkThe planning designation checks you choose, for one location, in one call. `checks` is any of: article_4, brownfield, ancient_woodland, heritage_at_risk, tpo, aqma, scheduled_monument, sssi, agricultural_land, flood_risk, green_belt, listed_buildings, aonb, national_park, conservation_area — omit it for all fifteen. Each check reports its own result, and one that could not be read says `status: unknown` rather than disappearing. Use `planning_designations` for the fixed bundle of thirteen; use this when you need SSSI or agricultural land grade, or only two or three checks. Give either `postcode` or `location` as "lat,lng". UK only.
Same call over REST
Planning check/v1/planning/checkNot connected yet? Connect your assistant. Sign in with your MarketCode account; no API key needed.
Inputs
Before you call it
- postcode
- The postcode must be a full UK postcode ("SE22 8HN"), not a district. Where a tool works at district grain it truncates the postcode itself.
- location
- Coordinates are WGS84 latitude and longitude, the order a map gives them. A postcode is accepted wherever
locationis, and is usually the easier input.
Inputs
Arguments planning_check takes
| Name | Type | Required | Description |
|---|---|---|---|
| postcode | string | No | |
| location | string | No | |
| checks | string[] | No |
Usage
How to run planning_check in your assistant
Ask your assistant in plain English, for example:
"Use the MarketCode tool planning_check for <address or area>.
Show the result and the credits charged."The connect steps for Claude, ChatGPT, Codex, Cursor and Claude Code are on the MCP page.
Price and licence
What it costs, and where the data comes from
planning_check is free over MCP and over REST, and the two surfaces share one credit balance. Free calls need a signed-in account or an API key and appear in your usage, but they never touch your balance.
Credits are granted on sign-up and bought in packs; the pricing page lists every call.
Related
Tools used with planning_check
- Planning designations at a locationFree
planning_designationsEvery planning designation affecting a location, in one call: conservationNamed in the description - Approval rate and decision time nearby2 credits
planning_precedentsWhat happened to applications like this one nearby — the planning precedent record. Give a point (`lat`/`lon`) or an `lpa_code`, optionally narrowed by `application_types` (substrings of the authority's own type labels, e.g. ["Householder"]).Same category - Planning history at a property1 credit
property_planning_historyPlanning history AT this property: applications linked to the unit or its building — each with decision, dates, appeal, CIL liability, development type and `match_level` (`unit`, `building`, or `nearby` within 25 m when nothing is linked) — a summary (approved / refused / withdrawn / pending), what needs consent here from the designation flags read three-valued (`applies` against `unchecked`), the LPA, and `coverage`: official planning data covers the 33 London boroughs today, so `status: not_covered` outside London is a different answer from `no_applications`, and is not charged. UK only.Same category - Planning histories for up to 100 properties1 credit
property_planning_history_batch`property_planning_history` for up to 100 properties in one call, per-item outcomes (ok | no_applications | not_covered | not_found | error) in input order. Charged per property answered — the sum of the single calls, never more; not_covered rows are free. UK only.Same category - Planning authority for a locationFree
planning_applicationsThe local planning authority for a location and its planning-portal URL.Same category
FAQ
Questions about planning_check
How much does `planning_check` cost?
+
planning_check is free over MCP and over REST, and the two surfaces share one credit balance. Free calls need a signed-in account or an API key and appear in your usage, but they never touch your balance.
Which assistants can run `planning_check`?
+
Any MCP client: Claude (claude.ai, Claude Desktop, Claude Code), ChatGPT in developer mode, Codex and Cursor, each documented on the MCP page. You sign in with your MarketCode account over OAuth; there is no key to paste, and the connection is read-only.
Where does the data come from?
+
The answer is computed by MarketCode. Coverage is the UK.
Does `planning_check` change anything?
+
No. The tool is annotated read-only on the server, so it never writes to your data or ours and an assistant can call it without a confirmation step.
Try planning_check in your assistant.
30-minute call. We'll connect your assistant live on a real address.