# Site Pack (remote · site-pack.nerolabs.workers.dev)

Permitted development, building regs, party wall dates, CDM and materials for UK builders' AI

- Trust score: 64/100 (medium)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-21

## Components

- remote · `site-pack.nerolabs.workers.dev`: 64/100 (this document), [markdown](https://verifymcp.io/servers/nero-engine-site-pack/site-pack.md), [page](https://verifymcp.io/servers/nero-engine-site-pack/site-pack)

## Channel facts

- Endpoint: `https://site-pack.nerolabs.workers.dev/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.1.0`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, 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-21.

- **Endpoint Security**: 63/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation.
  - HTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 51/100
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 3948 tokens (~493/item across 8 items; 8 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 27/100
  - Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 93/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 78% 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 8 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 9 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 60/100
  - Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28.

## Install

### How do I install the Site Pack MCP server?

Site Pack is a hosted endpoint at https://site-pack.nerolabs.workers.dev/mcp, so there is nothing to install locally. 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 --transport http nero-engine-site-pack 'https://site-pack.nerolabs.workers.dev/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "nero-engine-site-pack": {
      "url": "https://site-pack.nerolabs.workers.dev/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "nero-engine-site-pack": {
      "type": "http",
      "url": "https://site-pack.nerolabs.workers.dev/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.nero-engine-site-pack]
url = "https://site-pack.nerolabs.workers.dev/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "nero-engine-site-pack": {
      "type": "remote",
      "url": "https://site-pack.nerolabs.workers.dev/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add nero-engine-site-pack --url 'https://site-pack.nerolabs.workers.dev/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  nero-engine-site-pack:
    url: "https://site-pack.nerolabs.workers.dev/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "nero-engine-site-pack": {
      "Transport": "http",
      "Url": "https://site-pack.nerolabs.workers.dev/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add nero-engine-site-pack -t streamable-http -u 'https://site-pack.nerolabs.workers.dev/mcp'
```

### Other

```json
{
  "mcpServers": {
    "nero-engine-site-pack": {
      "type": "http",
      "url": "https://site-pack.nerolabs.workers.dev/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## 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-21 (score 64, +1)

No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-18 (score 63, +1)

No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-16 (score 62, +1)

No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-14 (score 61, +1)

- [functional improvement] Stability: unverified → 0.03

### 2026-11-13 (score 60)

First indexed and scored.

## MCP tools (8)

### `list_capabilities` (~50 tokens)

What Site Pack can do

Lists Site Pack's tools, the date its rules were last checked, what it covers (nations, project types, work types) and what it deliberately does not do. Free, needs no input.

### `check_permitted_development` (~1224 tokens)

Planning: permitted development or not? (England)

Checks a householder project in England against the permitted development limits in the GPDO 2015, Schedule 2, Part 1: single and multi storey rear extensions, side and wraparound extensions (Class A), loft dormers and hip to gable (Class B), rooflights (Class C), porches (Class D), outbuildings and garden rooms (Class E), and adding storeys (Class AA). Returns `verdict` (permitted_development, prior_approval_route, needs_planning_permission, needs_listed_building_consent, check_article_4_or_condition, needs_more_info, not_covered), `answer`, one line per limit in `checks` (status pass, fail or needs_input, with the limit and the rule's paragraph), the larger home extension prior approval route when a single storey rear extension is 3 to 6 m (attached) or 4 to 8 m (detached), flags for conservation areas, National Parks, National Landscapes, listed buildings and Article 4, `must_confirm` and sources. Example: 3.5 m single storey rear extension on a semi, 3.8 m high: {"project":"rear_extension_single_storey","house_type":"semi_detached","depth_m":3.5,"height_m":3.8,"eaves_height_m":2.8,"within_2m_of_boundary":true,"curtilage_coverage_percent":20,"materials_similar":true,"higher_than_existing_roof":false,"eaves_higher_than_existing":false,"beyond_principal_or_highway_side_elevation":false,"balcony_veranda_or_raised_platform":false}.

Input parameters:

- `added_volume_m3` (number): Lofts: extra roof space volume including any earlier roof enlargements, m3.
- `balcony_veranda_or_raised_platform` (boolean): Includes a balcony, veranda, or a raised platform (decking) over 0.3 m high.
- `between_side_wall_and_boundary` (boolean): Outbuildings on Article 2(3) land.
- `beyond_principal_or_highway_side_elevation` (boolean): Does it go forward of the front (principal) wall, or of a side wall facing a road?
- `cladding` (boolean): Article 2(3) land: will the outside be clad in stone, render, pebble dash, timber, plastic or tiles?
- `curtilage_coverage_percent` (number): After the work: ground covered by all buildings other than the original house, as a % of the plot excluding the original house footprint.
- `depth_m` (number): Rear extensions: how far it projects beyond the rear wall of the ORIGINAL house, metres.
- `designations` (array): Any that apply at the address. national_landscape is the new name for an AONB. Leave empty if none.
- `distance_from_house_m` (number): Outbuildings in National Parks, National Landscapes, the Broads or World Heritage Sites.
- `distance_to_highway_boundary_m` (number): Porches: distance to the boundary with a road or footway.
- `distance_to_rear_boundary_m` (number): Multi storey rear extensions: distance from the extension to the boundary opposite the rear wall.
- `eaves_height_m` (number): Eaves height, metres.
- `eaves_higher_than_existing` (boolean)
- `eaves_setback_m` (number): Lofts: dormer set back from the eaves along the slope, metres (at least 0.2).
- `floor_area_m2` (number): Porches: external ground floor area. Outbuildings: footprint.
- `forward_of_principal_elevation` (boolean): Outbuildings: in front of the house's front wall?
- `height_m` (number): Highest point of the extension, porch or outbuilding above ground, metres.
- `higher_than_existing_roof` (boolean)
- `hip_to_gable` (boolean): Lofts: is it a hip to gable (no eaves set back needed)?
- `house_type` (string): Needed for rear extensions (4 m detached, 3 m otherwise) and lofts (40 m3 terraced or end terrace, 50 m3 otherwise).
- `materials_similar` (boolean): External materials look similar to the house.
- `nation` (string): Defaults to england. Only england is checked; others return not_covered.
- `on_front_slope_facing_highway` (boolean): Lofts: does the dormer go on the front roof slope facing a road?
- `original_house_width_m` (number): Side extensions: width of the original house.
- `project` (string, required)
- `property_kind` (string): Defaults to house. Flats and maisonettes have no householder permitted development.
- `protrusion_m` (number): Rooflights: how far it stands proud of the roof slope, metres.
- `roof_pitch_matches` (boolean): Multi storey: roof pitch matches the house as far as practical.
- `roof_type` (string): Outbuildings: dual pitched allows 4 m (if not within 2 m of a boundary).
- `side_windows_obscure_and_fixed` (boolean): Upper floor or roof windows in a side wall are obscure glazed and non-opening below 1.7 m.
- `storeys` (number): Storeys in the extension or outbuilding.
- `trade` (object): Optional. The builder's own business details (Nero Trade Profile v1). Used to prefill the contractor details in notices and CDM answers and to give a stable nero_trade_ref. Not stored by Site Pack.
- `used_for_sleeping_or_separate_home` (boolean)
- `width_m` (number): Side extensions: width of the extension.
- `within_2m_of_boundary` (boolean)

### `check_building_regs` (~562 tokens)

Building Regulations: notifiable, which route, which Parts? (England and Wales)

For one or more kinds of building work in England or Wales: is it notifiable building work, exempt (small outbuildings, ground level conservatories and porches up to 30 m2), self-certifiable by a competent person scheme (FENSA, Certass, HETAS, OFTEC, CompetentRoofer), or must it go to the Building Safety Regulator (higher-risk buildings, England). Says whether a building notice is allowed or full plans are required (non-domestic, common parts of flats, within 3 m of a public sewer), and lists the Parts of Schedule 1 likely to apply with the reason for each (indicative). Returns `verdict`, `notifiable`, per-work reasons, routes, `parts_likely_to_apply`, `must_confirm` and sources. Example: {"work":["single_storey_extension","remove_load_bearing_wall"],"within_3m_of_public_sewer":false}.

Input parameters:

- `area_renovated_percent` (number): Re-roofing, re-rendering, wall insulation: share of that roof or wall area being renovated, %.
- `building_type` (string): Defaults to house.
- `competent_person_scheme` (string): If the installer is a member of one (for windows, stoves, roofs).
- `distance_to_boundary_m` (number): Outbuildings of 15 to 30 m2: distance to the nearest boundary.
- `floor_area_m2` (number): Outbuildings, conservatories and porches: internal floor area.
- `heated_from_house_system` (boolean): Conservatories: heated by extending the house heating?
- `higher_risk_building` (boolean): England: at least 18 m or 7 storeys with at least 2 homes (or a care home or hospital of that height).
- `mainly_non_combustible` (boolean): Outbuildings of 15 to 30 m2: built mainly of non-combustible materials?
- `nation` (string): Defaults to england. Scotland and Northern Ireland return not_covered.
- `separated_by_external_doors` (boolean): Conservatories and porches: separated from the house by external quality walls, doors or windows?
- `sleeping_accommodation` (boolean): Outbuildings: will anyone sleep in it?
- `trade` (object): Optional. The builder's own business details (Nero Trade Profile v1). Used to prefill the contractor details in notices and CDM answers and to give a stable nero_trade_ref. Not stored by Site Pack.
- `within_3m_of_public_sewer` (boolean)
- `work` (array, required): All the kinds of work in the job.

### `party_wall_notices` (~493 tokens)

Party Wall Act notices and dates (England and Wales)

Works out which notice the Party Wall etc. Act 1996 needs (line of junction, section 1; party structure, sections 2 and 3; adjacent excavation within 3 m or 6 m, section 6), and the dates: from `planned_start_date` the latest day to send it by the chosen method (by hand, first or second class post, email if agreed), or from `serve_date` the day it counts as served and the earliest start; plus the neighbour's 14 day reply deadline, when a dispute is deemed to arise, and when the notice lapses (12 months). Uses England and Wales bank holidays to 2028. Returns `notice`, `section`, `dates` (each as YYYY-MM-DD plus plain words), step by step `working`, what the notice must say, warnings and sources. Example: cutting a steel beam into a party wall, work to start 1 March 2027, posted first class: {"work":"insert_beam_or_dpc_into_party_wall","planned_start_date":"2027-03-01","serve_method":"first_class_post"}.

Input parameters:

- `adjoining_owners` (number): How many adjoining owners (each gets their own notice). Defaults to 1.
- `distance_to_neighbour_building_m` (number): Excavations: horizontal distance from the excavation to the neighbour's building.
- `excavation_depth_m` (number): Excavations: depth of your excavation or foundation below ground.
- `nation` (string): Defaults to england. The Act applies in England and Wales only.
- `neighbour_foundation_depth_m` (number): Excavations: depth of the neighbour's foundations, if known.
- `neighbour_will_agree_earlier_start` (boolean)
- `planned_start_date` (string): YYYY-MM-DD. Give this or serve_date (or both, to check the start is late enough).
- `serve_date` (string): YYYY-MM-DD: the day the notice was or will be handed over, posted or emailed.
- `serve_method` (string): Defaults to first_class_post.
- `trade` (object): Optional. The builder's own business details (Nero Trade Profile v1). Used to prefill the contractor details in notices and CDM answers and to give a stable nero_trade_ref. Not stored by Site Pack.
- `work` (string, required)

### `cdm_duties` (~430 tokens)

CDM 2015 duties and HSE F10 notification

For a construction project in Great Britain (domestic by default): who holds the client's duties (on a domestic job they pass to the contractor, the principal contractor, or the principal designer under a written agreement), which roles must be filled (principal designer and principal contractor when there is more than one contractor), the core duties (construction phase plan, welfare, induction, health and safety file), and whether the project must be notified to HSE on form F10 (longer than 30 working days with more than 20 workers at once, or over 500 person days), with the arithmetic shown. Returns `f10_notification_needed`, `f10_answer`, `client_duties_held_by`, `roles`, `duties`, `working`, `must_confirm` and sources. Example: an extension with 4 trades, 60 working days, peak 6 on site, average 3: {"contractors":4,"duration_working_days":60,"peak_workers_on_site":6,"average_workers_on_site":3}.

Input parameters:

- `average_workers_on_site` (number): Typical number on site, used to estimate person days.
- `client_type` (string): Defaults to domestic (a homeowner having work done on their own home, not as a business).
- `contractors` (number, required): Firms and self-employed trades working on the project, including subcontractors. 1 if only you.
- `designer_agreed_to_take_client_duties` (boolean): Domestic only: has the client a written agreement for the principal designer to take on the client duties?
- `duration_working_days` (number): Expected length of the construction work in working days.
- `peak_workers_on_site` (number): Most people working on site at the same time.
- `person_days` (number): Total person days, if already known.
- `trade` (object): Optional. The builder's own business details (Nero Trade Profile v1). Used to prefill the contractor details in notices and CDM answers and to give a stable nero_trade_ref. Not stored by Site Pack.

### `estimate_materials` (~377 tokens)

Bricks, blocks, mortar, concrete and plasterboard quantities

Works out quantities from dimensions, with the working: bricks (60 a m2 per half brick leaf), blocks (about 10 a m2), cavity walls with ties, mortar from wall volume minus unit volume, cement bags and sand tonnes for a chosen mix, concrete for strip foundations and slabs (ready mix order rounded up to 0.25 m3, or site mixed 1:2:4 materials), and plasterboard sheets by size. Openings are deducted. Waste allowances default to bricks and blocks 5%, mortar 10%, concrete 5%, plasterboard 10% and can be changed. Returns `order` (what to buy), per item `working`, totals before waste and notes. Example: a 6 m by 2.4 m cavity wall with a 1.2 m2 window, plus a 6 m strip foundation 0.6 m wide and 1 m deep: {"items":[{"kind":"cavity_wall","length_m":6,"height_m":2.4,"openings_m2":1.2},{"kind":"strip_foundation","length_m":6,"width_m":0.6,"depth_m":1}]}.

Input parameters:

- `concrete_supply` (string): Defaults to ready_mix.
- `items` (array, required)
- `mortar_mix_sand_parts` (number): Sand parts to 1 cement, defaults to 5 (1:5). Use what the specification says.
- `trade` (object): Optional. The builder's own business details (Nero Trade Profile v1). Used to prefill the contractor details in notices and CDM answers and to give a stable nero_trade_ref. Not stored by Site Pack.
- `waste_percent` (object): Override any of: bricks, blocks, mortar, concrete, plasterboard (percent).

### `structural_triage` (~430 tokens)

Structural worry: how urgent, and safe first steps

First-response triage when a customer reports a crack, a bulging or leaning wall, a sagging or fallen ceiling, a collapse, storm damage to a roof or chimney, a fallen tree or vehicle impact, a sagging floor, problems after a wall was removed, or signs of subsidence. Cautious by design: any danger to people makes it an emergency. Returns `urgency` (emergency, soon or routine: the same three speeds Nero Work uses), reasons, `safe_first_steps`, who to call now (999, gas 0800 111 999, power 105, the council dangerous structures team, insurer, structural engineer), and the questions to ask if details are missing. Example: a ceiling bulging with water under a bathroom: {"problem":"ceiling_sagging_or_fallen","water_coming_in":true}.

Input parameters:

- `crack_through_bricks_not_just_mortar` (boolean)
- `crack_width_mm` (number): Cracks: widest point in mm.
- `debris_falling` (boolean)
- `doors_or_windows_sticking_recently` (boolean)
- `gas_smell` (boolean)
- `getting_worse_quickly` (boolean)
- `near_road_or_footway` (boolean): Could it fall onto a road, footway or neighbour's property?
- `new_cracks_or_sagging_above` (boolean): After a wall was removed or an impact: new cracks or sagging above?
- `problem` (string, required)
- `rain_or_wind_forecast` (boolean)
- `roof_open_to_weather` (boolean)
- `someone_injured_or_trapped` (boolean)
- `trade` (object): Optional. The builder's own business details (Nero Trade Profile v1). Used to prefill the contractor details in notices and CDM answers and to give a stable nero_trade_ref. Not stored by Site Pack.
- `water_coming_in` (boolean)
- `water_near_electrics` (boolean)

### `trade_profile` (~169 tokens)

Check the builder's business details

Checks the builder's own business details (Nero Trade Profile v1: trading name, Companies House number, trade body or scheme and membership number such as FMB or TrustMark, postcode, contact) and returns them cleaned, with a stable `nero_trade_ref` computed from the scheme membership or company number. The same object, given as `trade` to the other tools, prefills their answers. Site Pack stores nothing. The same profile and reference can later be used to sign the business into Nero Work, the agent job exchange for trades.

Input parameters:

- `trade` (object, required): Optional. The builder's own business details (Nero Trade Profile v1). Used to prefill the contractor details in notices and CDM answers and to give a stable nero_trade_ref. Not stored by Site Pack.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/nero-engine-site-pack/site-pack#diagnostics

## Score history

- 2026-11-21: 64
- 2026-11-20: 63
- 2026-11-19: 63
- 2026-11-18: 63
- 2026-11-17: 62
- 2026-11-16: 62
- 2026-11-15: 61
- 2026-11-14: 61
- 2026-11-13: 60

## Common questions

### What is the Site Pack MCP server?

Site Pack is an MCP server listed in the public MCP registry as io.github.Nero-Engine/site-pack. Permitted development, building regs, party wall dates, CDM and materials for UK builders' AI. This page covers its hosted endpoint (https://site-pack.nerolabs.workers.dev/mcp).

### Is the Site Pack MCP server safe to use?

Site Pack scores 64 out of 100 on VerifyMCP. 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 Site Pack MCP server expose?

Site Pack exposes 8 tools: list_capabilities, check_permitted_development, check_building_regs, party_wall_notices, cdm_duties, and 3 more. Their descriptions and schemas cost roughly 3,735 tokens of context every time the server is loaded.

### Does the Site Pack MCP server require authentication?

No. We connected to Site Pack without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the Site Pack MCP server still maintained?

Site Pack is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

### What did VerifyMCP test on the Site Pack MCP server?

VerifyMCP ran 12 checks on Site Pack, covering TLS certificate, Authorization, HSTS header, DNSSEC and 8 more. One item could not be completed, a gap on our side rather than a finding about Site Pack: HTTPS. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.

## Links

- Remote endpoint: https://site-pack.nerolabs.workers.dev/mcp
- Repository: https://github.com/Nero-Engine/site-pack-mcp
- Website: https://site-pack.nerolabs.workers.dev/docs
- Changelog RSS feed: https://verifymcp.io/servers/nero-engine-site-pack/site-pack.xml
- Changelog JSON feed: https://verifymcp.io/servers/nero-engine-site-pack/site-pack/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/nero-engine-site-pack/site-pack.json
- HTML version of this page: https://verifymcp.io/servers/nero-engine-site-pack/site-pack
