Skip to content

Site Pack MCP server

io.github.Nero-Engine/site-packNero-Enginestreamable-httpv1.1.0Scanned

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

8 tools: 7 change things and 1 only read.

Tools: 0 delete, 0 irreversible, 7 write, 1 read.
  • Reads private data · 0
  • Reads text others write · 0
  • Can send data out · 7
  • No findings

Tools listed without sign-in. Remote posture

Anlyon alternative

7 of these tools change something. Run those as governed actions.

Declare what an action changes, and Anlyon puts it under a shared limit, binds every approval to the exact request, and grades the outcome. It works on any HTTPS API you can describe as an action.

Anlyon Radar does not run, proxy or govern this MCP server. A tool your own code calls directly is not routed through Anlyon and is not governed by it.

Import an OpenAPI spec →

What the Site Pack MCP server can do

The Site Pack MCP server is published by the GitHub account Nero-Engine. It has 8 tools. It can create or change data (7 tools: check_permitted_development, check_building_regs, party_wall_notices, cdm_duties and 3 more), but cannot delete data. 1 tool only reads.

7 tools can send data out of your system (check_permitted_development, check_building_regs, party_wall_notices and 4 more).

None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.

Its remote endpoint lists its tools without sign-in.

Last scanned Nov 13, 2026, version 1.1.0.

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

8 tools

Changes things 7Claude Code: ask
  • cdm_dutiesFor 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 pr…Can send data outNo findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    What it can reach

    • outboundThe input takes a destination (input.trade.phone): what the tool writes goes there.
    Description, as the server wrote it
    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}.

    Annotations the server declares

    • title: CDM 2015 duties and HSE F10 notification
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • check_building_regsFor 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-c…Can send data outNo findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    What it can reach

    • outboundThe input takes a destination (input.trade.phone): what the tool writes goes there.
    Description, as the server wrote it
    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}.

    Annotations the server declares

    • title: Building Regulations: notifiable, which route, which Parts?
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • check_permitted_developmentChecks 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 …Can send data outNo findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    What it can reach

    • outboundThe input takes a destination (input.trade.phone): what the tool writes goes there.
    Description, as the server wrote it
    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}.

    Annotations the server declares

    • title: Planning: permitted development or not? (England)
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • estimate_materialsWorks 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 vol…Can send data outNo findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    What it can reach

    • outboundThe input takes a destination (input.trade.phone): what the tool writes goes there.
    Description, as the server wrote it
    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}]}.

    Annotations the server declares

    • title: Bricks, blocks, mortar, concrete and plasterboard quantities
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • party_wall_noticesWorks out which notice the Party Wall etc.Can send data outNo findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    What it can reach

    • outboundThe input takes a destination (input.trade.phone): what the tool writes goes there.
    Description, as the server wrote it
    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"}.

    Annotations the server declares

    • title: Party Wall Act notices and dates
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • structural_triageFirst-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 vehic…Can send data outNo findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    What it can reach

    • outboundThe input takes a destination (input.trade.phone): what the tool writes goes there.
    Description, as the server wrote it
    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}.

    Annotations the server declares

    • title: Structural worry: how urgent, and safe first steps
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • trade_profileChecks 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, postcod…Can send data outNo findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    What it can reach

    • outboundThe input takes a destination (input.trade.phone): what the tool writes goes there.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Check the builder's business details
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
Only reads 1Show 1 read-only tool
  • list_capabilitiesLists 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.No findings

    Why it is in this group

    • The name "list_capabilities" says "list": a word for reading.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: What Site Pack can do
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or untrusted-input.

Reads private data0
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write0
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out7
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

Tools listed without sign-in

Looked at Nov 20, 2026, 19:24 UTC, unchanged since Nov 13, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
yes
HTTP status of an anonymous initialize
200
tools/list served without credentials
yes
Tools that change things, listed without credentials
7
Protocol version
2025-06-18
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
https://site-pack.nerolabs.workers.dev/.well-known/oauth-protected-resource/mcp
Authorization servers
not observed
Legacy HTTP+SSE transport
no
Dynamic client registration
not observed
Client ID metadata documents
not observed
  • WarnThe whole server

    The endpoint served tools/list without credentials, and the list has 7 tools that change things (7 write). Whether a call also works without credentials was not tested: tools are never called.

    Matched text

    https://site-pack.nerolabs.workers.dev/mcp: tools/list returned 8 tools to an anonymous client, including check_permitted_development (write), check_building_regs (write), party_wall_notices (write), cdm_duties (write), estimate_materials (write) and 2 more

    What this check looks for

Findings

Matches of fixed checks, with the text they matched.

No check matched anything in these tool definitions. That is not a safety guarantee.

History

Changes to its tool definitions and to its remote endpoint, newest first.

No change seen yet. Its tools are rescanned every day, and a remote endpoint is looked at once a week.

Install

Pinned to version 1.1.0. Values in angle brackets are yours to fill in.

claude mcp add --transport http site-pack https://site-pack.nerolabs.workers.dev/mcp
claude mcp add --transport http site-pack https://site-pack.nerolabs.workers.dev/mcp

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__site-pack__list_capabilities"
    ],
    "ask": [
      "mcp__site-pack__check_permitted_development",
      "mcp__site-pack__check_building_regs",
      "mcp__site-pack__party_wall_notices",
      "mcp__site-pack__cdm_duties",
      "mcp__site-pack__estimate_materials",
      "mcp__site-pack__structural_triage",
      "mcp__site-pack__trade_profile"
    ],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as site-pack. Review it before you use it.

Capability tags behind 7 rules
  • mcp__site-pack__check_permitted_development outbound
  • mcp__site-pack__check_building_regs outbound
  • mcp__site-pack__party_wall_notices outbound
  • mcp__site-pack__cdm_duties outbound
  • mcp__site-pack__estimate_materials outbound
  • mcp__site-pack__structural_triage outbound
  • mcp__site-pack__trade_profile outbound

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://radar.anlyon.com/api/v1/servers/io.github.Nero-Engine/site-pack/verify?hash=2a73476b987e5a1cdd4bcf7819f3a9f8e848d334c526a282dfd139ef5e5d8d5e" | jq -e '.changed == false'

Pinned hash 2a73476b987e, from Nov 13, 2026, 01:18 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/io.github.Nero-Engine/site-pack/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for io.github.Nero-Engine/site-pack
[![Anlyon Radar](https://radar.anlyon.com/badge/io.github.Nero-Engine/site-pack.svg)](https://radar.anlyon.com/servers/io.github.Nero-Engine/site-pack)

Source: MCP Registry · repository. Synced Nov 13, 2026, 01:17 UTC.

Site Pack MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the Site Pack MCP server safe?

No scan can promise that. What its definitions show: 8 tools, 7 of which can change, send or delete something, and 0 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.

Can the Site Pack MCP server delete data?

No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.

Can the Site Pack MCP server do things that cannot be undone?

No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.

What tools does the Site Pack MCP server have?

8 tools: 7 write, 1 read. check_permitted_development, check_building_regs, party_wall_notices, cdm_duties, estimate_materials, structural_triage, trade_profile and list_capabilities.

Does the Site Pack MCP server need sign-in or OAuth?

Its remote endpoint listed its tools to an anonymous client, without sign-in.

Does the Site Pack MCP server send data to outside services?

7 tools can carry data out (it sends, posts or publishes, or takes a recipient, channel or URL): check_permitted_development, check_building_regs, party_wall_notices, cdm_duties, estimate_materials, structural_triage and 1 more.

Has the Site Pack MCP server changed its tools?

Not since Anlyon Radar started tracking it. Last scanned Nov 13, 2026.