Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Ridge Pack

REMOTE · RIDGE-PACK.NEROLABS.WORKERS.DEV

Roof take-offs, weather windows, building regs and storm triage for UK roofers' AI assistants

+3 this week 64 Trust /100

Last scanned (13 hours ago)

Scores higher than 46% of remote servers

Reachable. Last reached 21 Nov 2026.

Category Cloud Infrastructure

Trust breakdown (7 categories)

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. How we score → Why this is hard to score →

Endpoint Security63
  • The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
  • 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. See how to fix → View diagnostics → Partial
  • HTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement. View diagnostics → Unverified
  • HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
  • DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
Schema Quality & AI Usability53
  • AI-judged instruction clarity (good).Pass
  • Context-footprint check failed: tool/resource definitions use about 3047 tokens (~380/item across 8 items; 8 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
  • 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 Coverage93
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 80% of tool parameters carry a description.Partial
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 8 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 9 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
  • Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
What we tested

Checks we ran (12)

  • TLS certificate
  • Authorization
  • HSTS header
  • DNSSEC
  • Transport
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Checks we could not complete (1)

These are gaps on our side, not findings about this hosted endpoint. We only credit what we can confirm, so a category made up entirely of them scores 0.

  • HTTPS in Endpoint SecurityHTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement.

Does not apply to this hosted endpoint (2)

  • Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
  • Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.

The score does not measure everything. What the score does not measure →

Changelog

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.

  • 20 Nov 26 +1

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

  • 18 Nov 26 +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.

  • 15 Nov 26 +1

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

  • 14 Nov 26 0
    • Stability: unverified → 0.03 ▲ functional
  • 13 Nov 26 61

    First indexed and scored.

Diagnostics

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 21 Nov 2026 · Probed https://ridge-pack.nerolabs.workers.dev/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=nerolabs.workers.dev CN=YE1,O=Let's Encrypt,C=US 10 Nov 2026 8 Feb 2027 ECDSA 256 ECDSA-SHA384 6de4049323d6abaa327886d7b5c76757b3a
SANs: *.nerolabs.workers.dev, nerolabs.workers.dev
CN=YE1,O=Let's Encrypt,C=US (CA) CN=Root YE,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 ECDSA 384 ECDSA-SHA384 5ddd70dd31f801c85c186a7a04b80afe
CN=Root YE,O=ISRG,C=US (CA) CN=ISRG Root X2,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 ECDSA-SHA384 872165fc34b6e5fba8add5b3705fb53a
CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 SHA256-RSA 6c8f1dc727c7117f7baf853ac980f9cd

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of ridge-pack.nerolabs.workers.dev. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
dev. DS published 60074 8 Verified
workers.dev. No DS Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://ridge-pack.nerolabs.workers.dev/mcp Verified 200
http (plaintext) http://ridge-pack.nerolabs.workers.dev/mcp Inconclusive 405
MCP tools · 8 exposed · ~2,874 tokens

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. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
check_building_regs ~489

England and Wales. Says whether a roofing job is notifiable to building control (re-covering 25% or more of a roof, a change of covering, structural work, rooflights, dormers, solar, new roofs), whether Part L wants the whole roof insulated (England: more than 50% of the roof or more than 25% of the whole envelope renovated, target 0.16 W/m2K from Approved Document L; Wales: over 25%), who signs it off (competent person scheme such as CompetentRoofer, or building control), and flags for listed buildings, conservation areas, Article 4, flats, bats and asbestos. Each answer cites the official source. Typical call: {"nation":"england","work_type":"re_cover_pitched","percent_of_roof":100,"insulation":"ceiling_level","competent_person_scheme_member":true}.

NameTypeReqDescription
article_4_directionboolean––
building_usestring–Default dwelling.
built_before_2000boolean–For the asbestos flag.
changes_external_appearanceboolean–Will the roof look noticeably different?
competent_person_scheme_memberboolean–Is the roofer registered with a roofing competent person scheme (for example CompetentRoofer)?
conservation_areaboolean––
fire_performance_changesboolean––
flat_or_maisonetteboolean––
insulationstring–Where the roof insulation is or will be.
listed_buildingboolean––
nationstring–Default england.
new_covering_weight_change_percentnumber–How much heavier (+) or lighter (-) the new covering is, percent.
percent_of_roofnumber–Share of this roof's area being stripped, re-covered or repaired, 0 to 100. Needed for re-covering and repairs.
percent_of_whole_envelopenumber–Optional: share of the whole building envelope (walls, roof, floor) being renovated, for the major renovation test.
tradeobject–Optional. The roofer's own business details (Nero Trade Profile v1). Used to put the contractor on risk notes and to give a stable nero_trade_ref. Not stored by Ridge Pack.
work_typestringyes–

No output schema declared.

No examples provided.

check_pitch_headlap ~407

Checks a roof covering type against the pitch, the headlap and the batten gauge: is the pitch below the typical minimum for that kind of tile or slate, is the headlap enough for the exposure, does the gauge leave the headlap you want. Returns overall (ok_subject_to_maker_data, check_with_maker or fail), each check with its working, and what to confirm. Indicative: always confirm against the maker's data for the exact product. Pass maker_min_pitch_deg and maker_min_headlap_mm from the data sheet to check against those instead. Typical call: {"covering":"natural_slate","pitch_deg":25,"headlap_mm":75,"exposure":"severe"}.

NameTypeReqDescription
coveringstringyesRoof covering. concrete_interlocking: Concrete interlocking tile (large format); clay_interlocking: Clay interlocking tile; clay_pantile: Clay pantile (traditional); plain_tile: Plain tile, clay or c…
exposurestring–Exposure to wind-driven rain. Default moderate.
gauge_mmnumber–Batten gauge planned, mm.
headlap_mmnumber–Headlap planned, mm.
maker_min_headlap_mmnumber–Minimum headlap from the maker's data sheet, if known.
maker_min_pitch_degnumber–Minimum pitch from the maker's data sheet, if known.
pitch_degnumberyesRafter pitch in degrees.
tile_length_mmnumber–Unit length, mm (to check the gauge).
tradeobject–Optional. The roofer's own business details (Nero Trade Profile v1). Used to put the contractor on risk notes and to give a stable nero_trade_ref. Not stored by Ridge Pack.

No output schema declared.

No examples provided.

list_capabilities ~44

Lists Ridge Pack's tools, what it covers (nations, roof shapes, coverings, job types) and what it deliberately does not do. Free, needs no input.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

roof_takeoff ~701

Works out a pitched roof's slope area, rafter length, ridge, hips, eaves and verges from the plan size and pitch, then a materials list: tiles or slates, battens, underlay rolls, ridge and hip tiles, hip irons, valleys, nails, eaves trays, ventilation and dry verge units, with waste. Every step of the working is shown. Geometry is exact; quantities resting on product figures are indicative unless you pass the maker's gauge, cover width and headlap. Run complex roofs one section at a time. Typical call: a 10 x 8 m gable roof at 35 degrees in concrete interlocking tiles: {"shape":"gable","plan_length_m":10,"plan_width_m":8,"pitch_deg":35,"covering":"concrete_interlocking"}.

NameTypeReqDescription
cover_width_mmnumber–Maker's cover width per unit, mm.
coveringstringyesRoof covering. concrete_interlocking: Concrete interlocking tile (large format); clay_interlocking: Clay interlocking tile; clay_pantile: Clay pantile (traditional); plain_tile: Plain tile, clay or c…
eaves_overhang_mnumber–Horizontal eaves overhang, metres. Default 0.3.
extra_hip_lengths_marray–True length of any extra hips (for example on an L-shaped roof), metres.
gauge_mmnumber–Batten gauge, mm, if already set (otherwise worked out from length and headlap).
headlap_mmnumber–Headlap, mm.
membrane_roll_m2number–Underlay roll size, m2. Default 50.
pitch_degnumberyesRafter pitch in degrees (10 to 75).
plan_length_mnumberyesWall plate length along the ridge, metres (outside of walls, before overhangs).
plan_width_mnumberyesSpan from eaves wall to eaves wall, metres (before overhangs). For mono pitch, low wall to high wall.
rafter_centres_mmnumber–Rafter or truss centres for batten nails. Default 400.
ridge_tile_cover_mmnumber–Effective cover of one ridge or hip tile, mm. Default 400.
shapestringyesgable (two slopes, ridge along plan_length_m), hipped (four slopes, same pitch all round), mono_pitch (one slope rising across plan_width_m).
tile_length_mmnumber–Maker's tile or slate length, mm (overrides the typical figure).
tradeobject–Optional. The roofer's own business details (Nero Trade Profile v1). Used to put the contractor on risk notes and to give a stable nero_trade_ref. Not stored by Ridge Pack.
valley_lengths_marray–True length of each valley, metres, as measured.
verge_overhang_mnumber–Verge overhang at gable ends, metres. Default 0.05.
waste_percentnumber–Waste on the covering. Default 5 (gable, mono) or 10 (hips or valleys).

No output schema declared.

No examples provided.

storm_triage ~289

Triage for storm damage and roof leaks. Gives an urgency of routine, soon or emergency (the same three speeds as Nero Work) with the reasons, safe first steps for the homeowner (no climbing, electrics, bulging ceilings, gas, falling debris, insurer), the temporary cover the roofer should use for each problem (tarpaulin battened over the ridge, tile clips, tingles, flashing tape, cold patch), what to photograph, and a Nero Work job title. Typical call: {"symptoms":["water_coming_through_ceiling","tiles_or_slates_missing"],"missing_count":12,"more_bad_weather_within_24h":true}.

NameTypeReqDescription
missing_countnumber–Roughly how many tiles or slates are missing.
more_bad_weather_within_24hboolean––
public_path_or_road_belowboolean––
raining_nowboolean––
smell_gasboolean––
symptomsarrayyesWhat the homeowner sees.
tradeobject–Optional. The roofer's own business details (Nero Trade Profile v1). Used to put the contractor on risk notes and to give a stable nero_trade_ref. Not stored by Ridge Pack.
vulnerable_people_in_homeboolean–Elderly, disabled, very young or unwell people living there.

No output schema declared.

No examples provided.

trade_profile ~157

Checks the roofer's own business details (Nero Trade Profile v1: trading name, Companies House number, competent person scheme and number, postcode, contact) and returns them cleaned, with a stable `nero_trade_ref` computed from the scheme registration or company number. The same object, given as `trade` to the other tools, prefills their answers. Ridge 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.

NameTypeReqDescription
tradeobjectyesOptional. The roofer's own business details (Nero Trade Profile v1). Used to put the contractor on risk notes and to give a stable nero_trade_ref. Not stored by Ridge Pack.

No output schema declared.

No examples provided.

weather_window ~354

Gets the hourly forecast for a UK postcode (today and up to 8 days ahead, from MET Norway) and checks each working hour against wind, gusts, rain, frost and the material's limits for the job type (tiling, membranes and sheets, torch-on, liquid coatings, EPDM adhesive, mortar bedding, lead work, inspection). Returns each day as good, caution or no_go with good hours, the best window, max gust in mph and the reasons, plus the limits used. Limits are Ridge Pack's cautious defaults (HSE sets no single wind speed) and can be overridden. Typical call: {"postcode":"BS1 4DJ","job_type":"membrane_or_sheets","start_date":"2026-11-16","end_date":"2026-11-20"}.

NameTypeReqDescription
end_datestring–Last day, YYYY-MM-DD, at most 8 days after today. Default start + 6 days.
end_hournumber–End of the working day, 1 to 23. Default 17.
job_typestring–What is being done. Default tiling_slating.
limitsobject–Optional overrides.
postcodestringyesFull UK postcode of the job.
start_datestring–First day, YYYY-MM-DD. Default today.
start_hournumber–Start of the working day, 0 to 22 (UK time). Default 8.
tradeobject–Optional. The roofer's own business details (Nero Trade Profile v1). Used to put the contractor on risk notes and to give a stable nero_trade_ref. Not stored by Ridge Pack.

No output schema declared.

No examples provided.

work_at_height_plan ~433

Builds the working at height and scaffold checklist for a roofing job (hierarchy of controls, scaffold to TG20 with guardrails, 7-day inspections, ladders only for short work, roof ladders, flat roof edges, fragile surfaces, power lines, highway licences, hot works, asbestos, rescue), the CDM 2015 duties (construction phase plan, domestic client, F10 notification test), a scored risk register (likelihood x severity) and a short risk note ready to print. From the Work at Height Regulations 2005, CDM 2015 and free HSE guidance. Typical call: {"job_type":"re_roof","eaves_height_m":5.5,"pitch_deg":35,"duration_days":5,"workers":3,"access":"scaffold","next_to_public_highway":true}.

NameTypeReqDescription
accessstring–Planned access. Default none_yet.
asbestos_suspectedboolean––
client_typestring–Default domestic.
contractor_namestring–Shown on the risk note.
duration_daysnumber–Working days on site. Default 1.
eaves_height_mnumberyesHeight to the eaves from the ground, metres.
fragile_surfacesboolean–Rooflights, old cement sheets or other fragile materials on or near the work.
hot_worksboolean–Torch-on felt or other hot works.
job_typestringyes–
next_to_public_highwayboolean––
occupied_buildingboolean––
overhead_power_linesboolean––
pitch_degnumber–Roof pitch, degrees (0 for flat).
site_addressstring–Shown on the risk note.
tradeobject–Optional. The roofer's own business details (Nero Trade Profile v1). Used to put the contractor on risk notes and to give a stable nero_trade_ref. Not stored by Ridge Pack.
workersnumber–Most people on site at once. Default 2.

No output schema declared.

No examples provided.

Install

How do I install the Ridge Pack MCP server?

Ridge Pack is a hosted endpoint at https://ridge-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.

remote · ridge-pack.nerolabs.workers.dev

# add to Claude Code
claude mcp add --transport http nero-engine-ridge-pack 'https://ridge-pack.nerolabs.workers.dev/mcp'
Common questions

What is the Ridge Pack MCP server?

Ridge Pack is an MCP server listed in the public MCP registry as io.github.Nero-Engine/ridge-pack. Roof take-offs, weather windows, building regs and storm triage for UK roofers' AI assistants. This page covers its hosted endpoint (https://ridge-pack.nerolabs.workers.dev/mcp).

Is the Ridge Pack MCP server safe to use?

Ridge 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 Ridge Pack MCP server expose?

Ridge Pack exposes 8 tools: list_capabilities, roof_takeoff, check_pitch_headlap, weather_window, check_building_regs, and 3 more. Their descriptions and schemas cost roughly 2,874 tokens of context every time the server is loaded.

Does the Ridge Pack MCP server require authentication?

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

Is the Ridge Pack MCP server still maintained?

Ridge 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 Ridge Pack MCP server?

VerifyMCP ran 12 checks on Ridge 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 Ridge 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.