io.github.beshogun/planwire-mcp
NPM · PLANWIRE-MCP · SCANNED AUG 3
UK planning application data for AI agents: search, geo-query and fetch applications.
Available components
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 →
Supply Chain Security86
- No malware found by supply-chain analysis.Pass
- Only part of the dependency tree could be resolved (94 of 98), so this covers what we could see, not the whole tree.Partial
- No install/post-install scripts declared.Pass
- Only part of the dependency tree could be resolved (94 of 98), so this covers what we could see, not the whole tree. View diagnostics → Partial
Provenance & Transparency45
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 23 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability77
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 396 tokens (~99/item across 4 items; 4 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management27
- Stability observed for 8 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
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.
npm · planwire-mcp
claude mcp add beshogun-planwire-mcp -- npx -y planwire-mcp
codex mcp add beshogun-planwire-mcp -- npx -y planwire-mcp
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"beshogun-planwire-mcp": {
"type": "local",
"command": [
"npx",
"-y",
"planwire-mcp"
],
"enabled": true
}
}
} openclaw mcp add beshogun-planwire-mcp --command npx --arg -y --arg planwire-mcp
mcp_servers:
beshogun-planwire-mcp:
command: "npx"
args: ["-y", "planwire-mcp"] {
"mcpServers": {
"beshogun-planwire-mcp": {
"command": "npx",
"args": [
"-y",
"planwire-mcp"
]
}
}
} 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.
- 2 Aug 26 +48
- Provenance: unverified → fail ▼ security
- Known CVEs: unverified → partial ▲ security
- Install scripts: unverified → pass ▲ security
- Malware scan: unverified → pass ▲ security
- Tool coverage: 100 → unverified ▼ functional
- Stability: unverified → 0.23 ▲ functional
- MCP protocol: unverified → pass ▲ functional
- Maintenance: unverified → pass ▲ functional
- Dependency health: unverified → partial ▲ functional
- License: unverified → pass ▲ functional
- Schema quality: unverified → excellent ▲ functional
- Licence: MIT functional
- 1 Aug 26 −5
- Stability: Stability not yet verified: we do not have a sandbox capture of the MCP schema this version of the package serves yet. security
- Capabilities: pass → unverified ▼ functional
- 31 Jul 26 −20
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 30 Jul 26 +22
- Tool coverage: unverified → 100 ▲ functional
- First check of Schema quality: pass functional
- First check of Schema quality: fail functional
- First check of Tool coverage: 100 functional
- First check of Schema quality: unverified functional
- 27 Jul 26 24
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 3 Aug 2026 · Analysed npm/[email protected]
Provenance none
Ecosystem: npm · Outcome: none
Dependencies 94 packages
94 packages in the resolved dependency tree · 94 deprecated · 29 stale.
The dependency tree was only partially resolved, so these counts may be incomplete.
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.
get_planning_application ~32
Fetch a single planning application by its PlanWire id.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | PlanWire application id. |
No output schema declared.
No examples provided.
list_councils ~32
List the UK councils (local planning authorities) PlanWire covers, with their IDs for use in searches.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
nearby_planning_applications ~101
Find planning applications within a radius of a point (latitude/longitude). Use for 'what's been applied for near this location'.
| Name | Type | Req | Description |
|---|---|---|---|
| lat | number | yes | Latitude (WGS84). |
| limit | integer | — | Max results (paid keys up to 100; free keys 10). |
| lng | number | yes | Longitude (WGS84). |
| radius_km | number | — | Radius in kilometres (paid plans allow larger radii). |
No output schema declared.
No examples provided.
search_planning_applications ~231
Search UK planning applications by keyword, council, postcode, status, type, or date range. Returns matching applications with address, description, reference, status, and dates. Use for questions like 'recent planning applications in Camden' or 'refused extensions in OX1'.
| Name | Type | Req | Description |
|---|---|---|---|
| council | string | — | Council ID, e.g. 'camden', 'oxford'. |
| date_from | string | — | Earliest application date, YYYY-MM-DD. |
| date_to | string | — | Latest application date, YYYY-MM-DD. |
| limit | integer | — | Results per page (paid keys up to 100; free keys 10). |
| page | integer | — | Page number (default 1). |
| postcode | string | — | Postcode or postcode prefix, e.g. 'OX1' or 'SW1A 1AA'. |
| q | string | — | Full-text search across address, description, and reference. |
| status | string | — | Filter by decision status. |
| type | string | — | Application type, e.g. 'Householder', 'Full', 'Listed Building'. |
No output schema declared.
No examples provided.