Ridge Pack MCP server
io.github.Nero-Engine/ridge-packNero-Enginestreamable-httpv1.1.0Scanned
Roof take-offs, weather windows, building regs and storm triage for UK roofers' AI assistants
8 tools: 6 change things and 2 only read.
- Reads private data · 0
- Reads text others write · 1
- Can send data out · 6
- No findings
Tools listed without sign-in. Remote posture
Anlyon alternative
6 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 Ridge Pack MCP server can do
The Ridge Pack MCP server is published by the GitHub account Nero-Engine. It has 8 tools. It can create or change data (6 tools: roof_takeoff, check_pitch_headlap, check_building_regs, work_at_height_plan and 2 more), but cannot delete data. 2 tools only read.
1 tool brings in text other people can write (weather_window); 6 tools can send data out of your system (roof_takeoff, check_pitch_headlap, check_building_regs and 3 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 6Claude Code: ask
check_building_regsEngland and Wales.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 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}.
Annotations the server declares
- title: Building regulations, Part L and planning flags
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
check_pitch_headlapChecks 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 th…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 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"}.
Annotations the server declares
- title: Pitch, headlap and gauge sanity check
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
roof_takeoffWorks 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, r…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 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"}.
Annotations the server declares
- title: Roof area and materials take-off
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
storm_triageTriage for storm damage and roof leaks.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 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}.
Annotations the server declares
- title: Storm damage and leak triage
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
trade_profileChecks 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 clean…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 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.
Annotations the server declares
- title: Check the roofer's business details
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
work_at_height_planBuilds 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…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 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}.
Annotations the server declares
- title: Working at height checklist and job risk note
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
Only reads 2Show 2 read-only tools
list_capabilitiesLists Ridge Pack's tools, what it covers (nations, roof shapes, coverings, job 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 Ridge Pack's tools, what it covers (nations, roof shapes, coverings, job types) and what it deliberately does not do. Free, needs no input.
Annotations the server declares
- title: What Ridge Pack can do
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
weather_windowGets 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 f…Reads text others writeNo findings
Why it is in this group
- The description's first verb is "get": a word for reading.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it 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"}.
Annotations the server declares
- title: Weather window for roof work
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: true
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.
- Reads private data0
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write1
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out6
- 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.
Looked at Nov 20, 2026, 19:23 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
- 6
- Protocol version
- 2025-06-18
- WWW-Authenticate on 401
- not observed
- resource_metadata in WWW-Authenticate
- not observed
- RFC 9728 protected resource metadata
- https://ridge-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 6 tools that change things (6 write). Whether a call also works without credentials was not tested: tools are never called.
What this check looks forMatched text
https://ridge-pack.nerolabs.workers.dev/mcp: tools/list returned 8 tools to an anonymous client, including roof_takeoff (write), check_pitch_headlap (write), check_building_regs (write), work_at_height_plan (write), storm_triage (write) and 1 more
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 ridge-pack https://ridge-pack.nerolabs.workers.dev/mcpclaude mcp add --transport http ridge-pack https://ridge-pack.nerolabs.workers.dev/mcpRun 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.
{
"permissions": {
"allow": [
"mcp__ridge-pack__list_capabilities",
"mcp__ridge-pack__weather_window"
],
"ask": [
"mcp__ridge-pack__roof_takeoff",
"mcp__ridge-pack__check_pitch_headlap",
"mcp__ridge-pack__check_building_regs",
"mcp__ridge-pack__work_at_height_plan",
"mcp__ridge-pack__storm_triage",
"mcp__ridge-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 ridge-pack. Review it before you use it.
Capability tags behind 7 rules
- mcp__ridge-pack__roof_takeoff outbound
- mcp__ridge-pack__check_pitch_headlap outbound
- mcp__ridge-pack__weather_window untrusted-input
- mcp__ridge-pack__check_building_regs outbound
- mcp__ridge-pack__work_at_height_plan outbound
- mcp__ridge-pack__storm_triage outbound
- mcp__ridge-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/ridge-pack/verify?hash=9c538c8c0e02eb400945779f2992681b61cbacd1ba98c64cb8cdf1084c7227c2" | jq -e '.changed == false'Pinned hash 9c538c8c0e02, 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/ridge-pack/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/io.github.Nero-Engine/ridge-pack)Source: MCP Registry · repository. Synced Nov 13, 2026, 01:17 UTC.
Ridge Pack MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the Ridge Pack MCP server safe?
- No scan can promise that. What its definitions show: 8 tools, 6 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 Ridge 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 Ridge 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 Ridge Pack MCP server have?
- 8 tools: 6 write, 2 read. roof_takeoff, check_pitch_headlap, check_building_regs, work_at_height_plan, storm_triage, trade_profile, list_capabilities and weather_window.
Does the Ridge Pack MCP server need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the Ridge Pack MCP server send data to outside services?
- 6 tools can carry data out (it sends, posts or publishes, or takes a recipient, channel or URL): roof_takeoff, check_pitch_headlap, check_building_regs, work_at_height_plan, storm_triage and trade_profile.
Has the Ridge Pack MCP server changed its tools?
- Not since Anlyon Radar started tracking it. Last scanned Nov 13, 2026.