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.

Harrowgate Group Tools

REMOTE · HARROWGATEGROUP.COM

Planning tools for commercial paving and site work.

70 Trust /100

Last scanned (18 hours ago)

Scores higher than 54% 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 Security74
  • 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 is enforced; there's no plaintext access path. View diagnostics → Pass
  • 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 Usability54
  • AI-judged instruction clarity (good).Pass
  • Context-footprint check failed: tool/resource definitions use about 3732 tokens (~311/item across 12 items; 12 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 Management17
  • Stability observed for 5 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 12 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 13 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a current MCP spec version (2026-07-28).Pass
What we tested

Checks we ran (13)

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

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.

  • 21 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.

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

  • 17 Nov 26 +1
    • Stability: unverified → 0.03 ▲ functional
  • 16 Nov 26 67

    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://harrowgategroup.com/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=harrowgategroup.com CN=WE1,O=Google Trust Services,C=US 9 Nov 2026 7 Feb 2027 ECDSA 256 ECDSA-SHA256 8b1c8a77ed2ba51413b050a031a72256
SANs: harrowgategroup.com
CN=WE1,O=Google Trust Services,C=US (CA) CN=GTS Root R4,O=Google Trust Services LLC,C=US 13 Dec 2023 20 Feb 2029 ECDSA 256 ECDSA-SHA384 7ff31977972c224a76155d13b6d685e3
CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE 15 Nov 2023 28 Jan 2028 ECDSA 384 SHA256-RSA 7fe530bf331343bedd821610493d8a1b

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of harrowgategroup.com. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
com. DS published 19718 13 Verified
harrowgategroup.com. 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://harrowgategroup.com/mcp Verified 200
http (plaintext) http://harrowgategroup.com/mcp HTTPS enforced 301 https://harrowgategroup.com/mcp
MCP tools · 12 exposed · ~3,680 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
accessible_parking_calculator ~154

Minimum accessible parking spaces for a new or redeveloped Ontario lot under Ontario Regulation 191/11 section 80.36, the Type A and Type B split, access aisles and painted stall line length. Every parameter is optional and has a default. Preliminary planning only. Municipal zoning by-laws and the Building Code can add requirements, and the designer of record governs.

NameTypeReqDescription
rowsinteger–Rows of stalls, used for the stall line length.
spacesinteger–Total number of parking spaces in the lot.
stall_lengthnumber–Stall length. Use the dimension from your municipal zoning by-law. Unit: m or ft.
unitsstring–Units for stall length.

No output schema declared.

No examples provided.

asphalt_concrete_calculator ~372

Tonnes of hot mix asphalt for a paving area, or cubic metres and truck loads of ready-mix concrete for a slab, footing or column. Every parameter is optional and has a default. Material estimate from the numbers entered. It is not a quote and does not include base, forming, reinforcing or site conditions.

NameTypeReqDescription
areanumber–Total paving area, used when how=area. Unit: sq ft or m2.
countinteger–Number of columns or piers, used when shape=col.
densitynumber–Compacted asphalt density. 2350 kg/m3 equals 110 lb per square yard per inch. Unit: kg/m3.
diameternumber–Column diameter, used when shape=col. Unit: ft or m.
heightnumber–Column height or depth, used when shape=col. Unit: ft or m.
howstring–Enter the paving area as length and width (lw) or as a total area (area).
lengthnumber–Length of the paving area or slab. Unit: ft or m.
modestring–Which calculation to run.
shapestring–Slab or footing (slab), or round column or pier (col).
thicknessnumber–Compacted asphalt thickness, or concrete slab thickness. Unit: in or mm.
thickness_unitstring–Unit for thickness.
trucknumber–Ready-mix truck capacity. Unit: m3.
unitsstring–Units for lengths and areas.
wastenumber–Waste allowance on the concrete order. Unit: percent.
widthnumber–Width of the paving area or slab. Unit: ft or m.

No output schema declared.

No examples provided.

concrete_slab_thickness_and_reinforcing_guide ~252

Minimum slab thickness, subbase, joint spacing, joint depth and reinforcing notes for a walk, patio, driveway, parking lot or truck pad, from published ready-mix concrete association guidance. Every parameter is optional and has a default. Guidance only, not a slab design. Loads, soil, frost, drainage, concrete mix and the municipal or project specification decide the final thickness and reinforcing, and an engineer designs parking lots, truck pads and anything carrying heavy equipment.

NameTypeReqDescription
lengthnumber–Slab length. Unit: m or ft.
subgradestring–Firm, or unstable, organic or uncompacted material under the slab.
thicknessnumber–Slab thickness. Leave out to use the minimum for the use. Parking lots and truck pads have no minimum here; enter the thickness your engineer designs. Unit: mm.
unitsstring–Units for slab length and width.
usestring–walk_patio, driveway_car (passenger vehicles), driveway_heavy (delivery vehicles or other heavy loads), parking_lot or truck_pad.
widthnumber–Slab width. Unit: m or ft.

No output schema declared.

No examples provided.

curb_sidewalk_concrete_calculator ~265

Concrete volume, order quantity and ready-mix truck loads for a run of sidewalk, curb or curb and gutter, with an Ontario accessible path width check. Every parameter is optional and has a default. Preliminary planning only. A volume is one input to a quote; base, forming, reinforcing, joints, drainage and the municipal standard drawing also matter, and the engineer of record governs.

NameTypeReqDescription
curb_heightnumber–Curb height. Unit: mm.
curb_widthnumber–Average curb width. Unit: mm.
elementstring–Sidewalk (walk) or curb or curb and gutter (curb).
gutter_thicknessnumber–Gutter thickness. Unit: mm.
gutter_widthnumber–Gutter width, 0 for curb only. Unit: mm.
lengthnumber–Run length. Unit: m or ft.
thicknessnumber–Sidewalk thickness. Unit: mm.
trucknumber–Ready-mix truck capacity. Unit: m3.
unitsstring–Units for length and width.
wastenumber–Waste allowance. Unit: percent.
widthnumber–Sidewalk width. Unit: m or ft.

No output schema declared.

No examples provided.

excavation_spoil_volume_calculator ~286

Bank volume, loose volume after swell and truck loads for a trench or pit, with vertical or sloped walls. Every parameter is optional and has a default. Preliminary planning only. Swell factors are planning values; use your geotechnical figure where you have one. The engineer of record and conditions on site govern.

NameTypeReqDescription
depthnumber–Depth. Unit: m or ft.
lengthnumber–Bottom length. Unit: m or ft.
materialstring–Material, used to set the swell factor when swell is not given.
sidesstring–Where the slope applies: long sides only (trench with vertical ends) or all four sides (pit).
slopenumber–Horizontal run per 1 vertical on the walls: 0 for vertical, 1 (Type 1 to 3 soil, 1 vertical to 1 horizontal), 3 (Type 4 soil, 1 vertical to 3 horizontal), or any other number.
swellnumber–Swell factor. Default is the middle of the published range for the material (earth 25). Unit: percent.
trucknumber–Truck body capacity, loose. Unit: m3.
unitsstring–Units for dimensions.
widthnumber–Bottom width. Unit: m or ft.

No output schema declared.

No examples provided.

excess_soil_tracker_and_reuse_site_checker ~585

Which parts of Ontario Regulation 406/19 apply to a soil removal project or a reuse site, and the records to keep, based on soil volume, past land use and where the soil is going. Every parameter is optional and has a default. General information on the regulation, not legal or environmental advice. A qualified person under Ontario Regulation 153/04 prepares the assessments and reports, and the Soil Rules and the Registry forms set the detail. Confirm with your qualified person or the Ministry.

NameTypeReqDescription
destinationstring–Where the soil is going: reuse_site, class1 (a soil bank storage or soil processing site), landfill (a landfilling site or dump) or unknown.
enhancedstring–Is any part of the project area, or has it ever been, used for an industrial use, as a garage, as a bulk liquid dispensing facility including a gasoline outlet, or for dry cleaning equipment?
infrastructurestring–Is the reuse site part of an undertaking related to an infrastructure project?
instrumentstring–Is the reuse site governed by a site-specific instrument such as a municipal fill permit, a by-law, an Aggregate Resources Act licence or a Planning Act approval?
known_dischargestring–Is any part of the project area known to be affected by the discharge of a contaminant?
land_usestring–Use of the whole project area as defined in Ontario Regulation 153/04: res_park_inst (residential, parkland or institutional, or a mix), agri_other (agricultural or other) or other (anything else, su…
pcastring–Has an assessment of past uses or a phase one environmental site assessment identified a potentially contaminating activity?
remediationstring–Is the primary purpose of the project to remediate contaminated land?
reuse_land_usestring–If the soil is going to a reuse site: is that site an agricultural or other use (agri_other) under Ontario Regulation 153/04, or something else (other)?
rolestring–project_leader (the person responsible for the project that excavates the soil) or reuse_site (the owner or operator receiving excess soil).
settlementstring–Is any part of the project area in an area of settlement under the Planning Act?
urgentstring–Is the soil being excavated because of danger to health or safety, serious risk to the natural environment or to property, an order of an authority, or to maintain infrastructure in a fit state of re…
volumenumber–Cubic metres of soil to be removed from the project area (project_leader) or expected to be deposited for final placement at the reuse site (reuse_site). Unit: m3.

No output schema declared.

No examples provided.

gravel_and_granular_base_calculator ~337

Tonnes, cubic metres, truck loads and the number of compaction lifts for a Granular A or Granular B base, using the 150 mm lift limit in Toronto standard specification TS 501. Every parameter is optional and has a default. Preliminary planning only. The project specification, the geotechnical report and your supplier's weights govern. The default weight per cubic metre is a general federal stone conversion, not a Granular A or Granular B test result.

NameTypeReqDescription
allowancenumber–Extra material for compaction loss, uneven subgrade and waste. Set it from your supplier or engineer; the default is 0. Unit: percent.
densitynumber–Weight per cubic metre used to convert volume to tonnes. The default is the federal stone conversion of 1.77 tonnes per cubic metre. Use your supplier's figure when you have it. Unit: kg/m3.
depthnumber–Finished (compacted) depth of the granular layer. Unit: mm or in.
depth_unitstring–Unit for depth.
lengthnumber–Length of the area. Unit: m or ft.
materialstring–Granular A (base course) or Granular B (subbase), as named in OPSS.MUNI 1010.
trucknumber–Payload of one truck load. 18 is an example; enter your hauler's figure. Unit: tonnes.
unitsstring–Units for length and width.
widthnumber–Width of the area. Unit: m or ft.

No output schema declared.

No examples provided.

hydro_excavation_vs_mechanical_checker ~246

Which excavation method the Electrical Safety Authority guideline allows near a located underground electrical distribution line: hand, vacuum (hydro) or machine. Every parameter is optional and has a default. Preliminary planning only. This covers electrical distribution lines only; gas, communication, water and sewer owners set their own requirements, and the instructions on your locate form govern.

NameTypeReqDescription
areastring–Whether the excavation is inside or outside the located area on the locate form.
clearancenumber–Planned clearance from the line to the dig. Unit: m or ft.
locatestring–Locate status: current (received, not expired, markings clear), none (not yet requested or received), expired (expired or markings unclear).
methodstring–Method being considered: mech (mechanical), vac (vacuum excavation) or hand.
orientationstring–Whether the dig runs parallel to the line (parallel) or crosses it or works near a point on it (cross).
test_holesstring–Whether the line has been exposed by test holes with depth and alignment confirmed.
unitsstring–Units for clearance.

No output schema declared.

No examples provided.

parking_lot_striping_and_stall_layout_calculator ~324

Stalls per row, rows, total stalls, painted stall line length and the minimum accessible spaces for a lot, using the stall sizes and drive aisle widths in Toronto Zoning By-law 569-2013 and the accessible count in Ontario Regulation 191/11. Every parameter is optional and has a default. Preliminary layout only. Other municipalities set their own stall sizes and aisle widths, and a site plan must meet the zoning by-law, fire route, drainage and accessibility rules that apply to the site. Confirm with your municipality.

NameTypeReqDescription
angleinteger–Stall angle to the drive aisle in degrees. 90 is perpendicular.
lot_depthnumber–Depth of the paved area, measured across the rows of stalls. Unit: m or ft.
lot_widthnumber–Length of one row of stalls, measured along the drive aisle. Unit: m or ft.
stall_lengthnumber–Stall length along the stall. The default is the 5.6 m minimum in By-law 569-2013 section 200.5.1.10(2). Unit: mm.
stall_widthnumber–Stall width across the stall. If left out, 2,600 mm is used with a 6.0 m aisle and 2,900 mm with a narrower aisle, as in section 200.5.1.10(2)(A) and (B). Unit: mm.
unitsstring–Units for the lot width and depth.

No output schema declared.

No examples provided.

rebar_quantity_calculator ~273

Bar count, total length, stock bars and mass for a slab or pad mat or a strip footing, using CSA G30.18 metric bar sizes. Every parameter is optional and has a default. Preliminary planning only. Take the bar list, cover, laps and hooks from the drawings; the engineer of record governs.

NameTypeReqDescription
barstring–CSA G30.18 bar size.
covernumber–Concrete cover. Unit: mm.
lapnumber–Lap splice length from the drawings. 0 adds no laps. Unit: mm.
layersinteger–Number of layers (mats).
layoutstring–Slab or pad mat (mat) or strip footing (strip).
lengthnumber–Slab length or footing length. Unit: m or ft.
long_barsinteger–Number of longitudinal bars in the footing.
spacingnumber–Bar spacing each way (mat) or transverse bar spacing (strip). Unit: mm.
stocknumber–Stock bar length. Unit: m.
unitsstring–Units for lengths.
wastenumber–Waste allowance. Unit: percent.
widthnumber–Slab width or footing width. Unit: m or ft.

No output schema declared.

No examples provided.

snow_load_and_snow_removal_volume_calculator ~291

Cubic metres, weight and truck loads of snow from a lot area and snow depth, with the footprint and base width of a snow pile of a chosen height. Every parameter is optional and has a default. Planning estimate only. Real snow varies with temperature, wind, rain and time on the ground, and real piles are windrows, not cones. Weigh or measure loads when it matters, for example for roof loads or truck limits.

NameTypeReqDescription
areanumber–Area to be cleared. Unit: m2 or sq ft.
depthnumber–Depth of snow to be cleared. Unit: cm or in.
depth_unitstring–Unit for depth.
pile_heightnumber–Height of the snow pile on site. Unit: m or ft.
snow_typestring–light 70 kg/m3, average 95, heavy 110, compacted 350.
trucknumber–Volume of one truck load. 15 is an example; enter your hauler's figure. Unit: m3.
unitsstring–Units for area and pile height. Area is square metres or square feet.
volume_factornumber–Multiplier on the fallen volume for plowed or loosened snow. 1 means the same volume as fallen. Set it from your contractor's experience.

No output schema declared.

No examples provided.

trench_shoring_checker ~295

Whether Ontario Regulation 213/91 requires a support system for an excavation, by depth, width and soil type, which kinds are permitted, and which other excavation rules apply. Every parameter is optional and has a default. Preliminary planning only. Regulations are amended from time to time; confirm against the current consolidation. The engineer of record and the competent person on site govern.

NameTypeReqDescription
adjacentstring–Whether the excavation could affect an adjacent building or structure.
depthnumber–Excavation depth. Unit: m or ft.
engineer_opinionstring–Whether there is a written engineer opinion that an unsupported wall is stable (section 234(2)(h), non-trench excavations only).
enterstring–Whether a worker will be required to enter the excavation.
hydrostaticstring–Whether hydrostatic pressure or groundwater is present in the soil.
soilinteger–Soil type 1 to 4 under section 226. If more than one type is present, use the highest number.
unitsstring–Units for depth and width.
wallstring–How the walls are formed: vertical or near vertical, sloped back at the gradient in section 234(2) for the soil type, or cut in sound and stable rock.
widthnumber–Excavation width at the bottom. Unit: m or ft.

No output schema declared.

No examples provided.

Install

How do I install the Harrowgate Group Tools MCP server?

Harrowgate Group Tools is a hosted endpoint at https://harrowgategroup.com/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 · harrowgategroup.com

# add to Claude Code
claude mcp add --transport http com-harrowgategroup-tools 'https://harrowgategroup.com/mcp'
Common questions

What is the Harrowgate Group Tools MCP server?

Harrowgate Group Tools is an MCP server listed in the public MCP registry as com.harrowgategroup/tools. Planning tools for commercial paving and site work. This page covers its hosted endpoint (https://harrowgategroup.com/mcp).

Is the Harrowgate Group Tools MCP server safe to use?

Harrowgate Group Tools scores 70 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 Harrowgate Group Tools MCP server expose?

Harrowgate Group Tools exposes 12 tools: asphalt_concrete_calculator, trench_shoring_checker, excavation_spoil_volume_calculator, hydro_excavation_vs_mechanical_checker, rebar_quantity_calculator, and 7 more. Their descriptions and schemas cost roughly 3,680 tokens of context every time the server is loaded.

Does the Harrowgate Group Tools MCP server require authentication?

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

Is the Harrowgate Group Tools MCP server still maintained?

Harrowgate Group Tools 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 Harrowgate Group Tools MCP server?

VerifyMCP ran 13 checks on Harrowgate Group Tools, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. 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.