# Site Pack

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

- name: io.github.Nero-Engine/site-pack
- version: 1.1.0
- connection class: R0 (autonomous)
- trust: 97/100
- quality: 85/100 (new)
- owner: not claimed
- descriptor: https://api.protogrid.dev/v1/servers/io.github.Nero-Engine%2Fsite-pack
- tools: https://api.protogrid.dev/v1/servers/io.github.Nero-Engine%2Fsite-pack/tools

**An agent can connect right now, no human step.** Remote endpoint, no authentication, reachable on the last probe.

## Connection (mcpServers)

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


## Trust

- hygiene: 100
- liveness: 100
- freshness: 100
- provenance: 90
- drivers: +repository +namespace-matches-repo +website +reachable +uptime-100% +updated-1d-ago
- Derived from observable signals (official registry feed and our own credential-free probes); no code audit performed.

## Quality 85/100 (new)

### protocol: 75 (weight 25)

- warn `protocol.modern`: newest supported version is 2025-06-18; 2026-07-28 not supported, older versions are deprecated until 2027-07-28
- n/a `protocol.stateless`: only applies to 2026-07-28 servers
- pass `protocol.transport`: streamable HTTP
- n/a `protocol.list_ttl`: only applies to 2026-07-28 servers

### authorization: n/a (weight 15)

- n/a `auth.prm`, `auth.as_metadata`, `auth.cimd`: no remote uses OAuth
- n/a `auth.secret_in_url`: no templated URL

### tool hygiene: 94 (weight 30)

- pass `tools.descriptions`: every tool has a description
- warn `tools.description_length`: 1 tools have descriptions over 1,024 characters, which crowds the context
- pass `tools.schemas`: every tool has an object input schema
- pass `tools.annotations`: 8 of 8 tools declare readOnlyHint or destructiveHint
- pass `tools.directory_hints`: every tool declares readOnlyHint, destructiveHint, idempotentHint and openWorldHint
- pass `tools.token_cost`: about 7,188 tokens to load every tool
- pass `tools.api_dump`: tools are not a one-to-one API dump
- pass `tools.hidden_text`: no hidden text in tool names, descriptions, schemas or annotations

### stability: n/a (weight 15)

- n/a `stability.changes`, `stability.rug_pull`, `stability.new_links`: tool history recorded for 1 of the 7 days needed

### dependencies: n/a (weight 15)

- n/a `deps.known_vulns`, `deps.mcp_sdk_version`, `deps.resolvable`: no npm or PyPI package

- tools: 8, about 7,188 tokens to load them all
- tool set hash: 3d8247bc92120f71fe3740cab847b503
- tools last changed: 2026-11-13T06:39:07.541Z
- badge: [![protogrid quality](https://protogrid.dev/badge/io.github.Nero-Engine/site-pack.svg)](https://protogrid.dev/servers/io.github.Nero-Engine/site-pack)
- Checks run on what our credential-free, read-only probes observe; tools are never called and no code audit is performed.

### Tool changes

- 2026-11-13 `trade_profile` changed (description)
  - before: 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. Pass the same object as `trade` to any other tool. 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.
  - after: 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.

Full history: https://api.protogrid.dev/v1/servers/io.github.Nero-Engine%2Fsite-pack/changes

## Remotes

- https://site-pack.nerolabs.workers.dev/mcp (streamable-http, auth none, reachable true, uptime30d 1)

## Packages

_none_

## Tools (8)

- `cdm_duties`: 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}.
- `check_building_regs`: 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}.
- `check_permitted_development`: 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}.
- `estimate_materials`: 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}]}.
- `list_capabilities`: 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.
- `party_wall_notices`: 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"}.
- `structural_triage`: 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}.
- `trade_profile`: 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.