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.

io.github.iarfhlaith/gaff-check

NPM · GAFF-CHECK · SCANNED SEP 20

Irish property due diligence: planning, prices, flood, radon, zoning, BER and crime context.

Available components

0 this week 82 Trust /100
Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →

Supply Chain Security98
  • No malware found by supply-chain analysis.Pass
  • No known CVEs affecting this package version or its production dependencies.Pass
  • No install/post-install scripts declared.Pass
  • 31 of 96 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
Schema Quality & AI Usability65
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 3178 tokens (~397/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 Management97
  • Stability observed for 29 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 8 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 8 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Install

How do I install the io.github.iarfhlaith/gaff-check MCP server?

io.github.iarfhlaith/gaff-check runs locally as an npm package, launched with npx -y gaff-check. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

npm · gaff-check

# add to Claude Code
claude mcp add iarfhlaith-gaff-check -- npx -y gaff-check
// .cursor/mcp.json
{
  "mcpServers": {
    "iarfhlaith-gaff-check": {
      "command": "npx",
      "args": [
        "-y",
        "gaff-check"
      ]
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "iarfhlaith-gaff-check": {
      "command": "npx",
      "args": [
        "-y",
        "gaff-check"
      ]
    }
  }
}
# add to Codex CLI
codex mcp add iarfhlaith-gaff-check -- npx -y gaff-check
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "iarfhlaith-gaff-check": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "gaff-check"
      ],
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add iarfhlaith-gaff-check --command npx --arg -y --arg gaff-check
# ~/.hermes/config.yaml
mcp_servers:
  iarfhlaith-gaff-check:
    command: "npx"
    args: ["-y", "gaff-check"]
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "iarfhlaith-gaff-check": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "gaff-check"
      ]
    }
  }
}
# add to Vellum
assistant mcp add iarfhlaith-gaff-check -t stdio -c npx -a -y gaff-check
// mcp.json
{
  "mcpServers": {
    "iarfhlaith-gaff-check": {
      "command": "npx",
      "args": [
        "-y",
        "gaff-check"
      ]
    }
  }
}
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 Sept 26 +1

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

  • 18 Sept 26 +1

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

  • 16 Sept 26 +1

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

  • 15 Sept 26 −3
    • Stability: pass → 0.80 functional
    • Package version: 0.1.1 → 0.2.0 functional
  • 14 Sept 26 0
    • Stability: 0.97 → pass security
    • Security disclosure: unverified → fail functional
  • 13 Sept 26 +1
    • Security disclosure: fail → unverified functional
  • 11 Sept 26 +1

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

  • 10 Sept 26 −2
    • Stability: pass → 0.87 functional
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 20 Sept 2026 · Analysed npm/gaff-check@0.2.0

Provenance No attestation

The registry publishes no build provenance for this version, so there is nothing to verify.

Result No attestation
Ecosystem npm

Background: How many MCP packages publish verified provenance →

Dependencies 96 packages
Packages resolved 96
Stale 31
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 8 exposed · ~3,178 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
ber_context ~460

Get Building Energy Rating (BER) context for an area of Ireland: the distribution of BER grades (A1 best … G worst) among certified dwellings in a county or Dublin postal district, optionally narrowed to a construction era, plus current SEAI retrofit grant amounts. Use this to answer "what energy rating is typical for a house of this age around here?" and "what upgrade grants exist?" during property due diligence. Data is CSO statistics aggregated from BER certificates published since 2009 — e.g. 1978-1999 houses in Co. Galway cluster around C/D, while 2015+ builds are overwhelmingly A-rated. Areas accepted: the 26 counties, the cities (Dublin/Cork/Galway/Limerick/Waterford), or Dublin postal districts ('Dublin 9', 'D6W'). Construction periods: 1700-1977, 1978-1999, 2000-2004, 2005-2009, 2010-2014, 2015-2019, 2020-2024, 2025-2029. THIS TOOL CANNOT TELL YOU A SPECIFIC HOME'S BER — never present the area distribution as the property's rating. A home's actual BER is on its certificate: the seller/agent must provide it, or it can be looked up on SEAI's public register (link included in every response) with the BER number or MPRN. Note also the statistics' bias: only dwellings that needed a certificate (sold, rented, grant-aided, or new since 2009) are counted, so old housing stock that never transacted is under-represented and its true typical rating is likely worse than shown. Grant amounts are a static reference with a last-verified date — confirm on seai.ie before financial decisions.

NameTypeReqDescription
areastringyesCounty ('Galway', 'Co. Cork'), city ('Cork City', 'Galway City'), or Dublin postal district ('Dublin 9', 'D6W').
period_of_constructionstringOptional construction era of the property, e.g. '1978-1999'. Omit for all eras combined.

No output schema declared.

No examples provided.

flood_risk ~422

Check mapped flood context for a location in Ireland: groundwater flood probability (high/medium/low), maximum historic groundwater flooding, and observed winter 2015/2016 surface-water flooding, from Geological Survey Ireland's 1:20,000 mapping. Use this in property due diligence. For each layer you get: whether the point itself lies inside a mapped extent (at_point), how many extents fall within the search radius, and the distance in metres to the nearest one. Groundwater flooding (turloughs, high water tables) is a distinct hazard from river or coastal flooding and matters especially in karst limestone areas of the west and midlands. CRITICAL LIMITATION — this tool does NOT check river (fluvial) or coastal flood models. The OPW's national flood extent datasets are licensed CC-BY-NC-ND, which forbids serving derived query results, so results include unchecked entries for them pointing to the OPW's official viewer (floodinfo.ie) where the user can view all flood maps for the location. A property can be at serious river or coastal flood risk while showing nothing in this tool's results. Never interpret empty results as "no flood risk": mapping is not exhaustive, pluvial (rain) flooding is not mapped at all, and the fluvial/coastal layers are not queried. Absence of a mapped extent means exactly that and no more. Provide lat/lng (WGS84) or a free-text address (geocoded; resolved location echoed back). Insurance decisions use different, private data — this tool says nothing about insurability.

NameTypeReqDescription
addressstringFree-text Irish address to geocode (used only if lat/lng absent).
latnumberLatitude (WGS84). Provide with lng, or use address instead.
lngnumberLongitude (WGS84). Provide with lat, or use address instead.
radius_mintegerSearch radius in metres around the point (default 250, max 5000).

No output schema declared.

No examples provided.

planning_applications ~393

Find Irish planning applications near a location, from the National Planning Application Database (all 31 local authorities, coverage back to ~2010, updated on varying cadences). Use this for property due diligence: pending or recent developments near a home (apartment blocks, roads, masts), extensions and attic conversions on the same street (precedents for what gets approved), and refusals that hint at site constraints. Returns per application: reference number, local authority, development description, address, status, decision with dates, distance in metres from the query point, and a link to the local authority's planning file where available. Provide either lat/lng (WGS84) or a free-text address (geocoded via OpenStreetMap; the resolved location is echoed back — verify it matches before drawing conclusions). Dates are ISO YYYY-MM-DD. The 'decided'/'pending' filter is based on whether a decision date is recorded; raw status strings vary by local authority and are returned verbatim. Coordinates of some older applications are approximate, and update lag differs by authority — absence of results is not evidence that nothing is planned.

NameTypeReqDescription
addressstringFree-text Irish address to geocode (used only if lat/lng absent).
latnumberLatitude (WGS84). Provide with lng, or use address instead.
limitintegerMaximum applications to return, newest first (default 50).
lngnumberLongitude (WGS84). Provide with lat, or use address instead.
radius_mintegerSearch radius in metres around the point (default 500, max 5000).
sincestringOnly applications received on/after this date (ISO YYYY-MM-DD).
statusstring'decided' = a decision date is recorded; 'pending' = none yet; 'all' = both.

No output schema declared.

No examples provided.

radon_risk ~309

Get the EPA's radon risk classification for the area containing a location in Ireland. Radon is a naturally occurring radioactive gas and the second biggest cause of lung cancer in Ireland after smoking. Use this during property due diligence to learn the area's banding from the EPA Radon Risk Map: the result echoes the EPA's own wording ("About 1 in N homes in this area is likely to have high radon levels", where N is 5, 10 or 20 — lower N means higher risk) plus a high_radon_area flag (true for the 1-in-5 and 1-in-10 bands, the ≥10% threshold Ireland uses to designate High Radon Areas, which carry legal testing duties for workplaces). This is an area-level prediction from measurement and geological data — it is NOT a measurement of any specific home. The EPA's standing advice ships in every response: any home anywhere can have high radon regardless of banding, the only way to know is to test, and testing is cheap (~€50). Provide lat/lng (WGS84) or a free-text address (geocoded; resolved location echoed back).

NameTypeReqDescription
addressstringFree-text Irish address to geocode (used only if lat/lng absent).
latnumberLatitude (WGS84). Provide with lng, or use address instead.
lngnumberLongitude (WGS84). Provide with lat, or use address instead.

No output schema declared.

No examples provided.

recorded_crime_context ~449

Get recorded-crime context for the Garda sub-district containing an Irish location, using official CSO counts and current Garda administrative boundaries. Use this for factual questions such as "what categories of crime have been recorded in this wider Garda area?" or to supply category-specific values for a choropleth. It returns annual counts, a pooled annual average, rates per 1,000 Census 2022 residents with approximate 95% Poisson intervals, and optionally the latest four-quarter Garda Division trend. Provide WGS84 lat/lng or a free-text address. Offence groups use official broad codes 03–16; omit them to return all published local groups. This is NOT a street-level crime heatmap or a property safety assessment. CSO station data applies to the entire Garda sub-district polygon: incidents have no published coordinates and may have happened anywhere within it. Never infer a hotspot near the address, spread incidents evenly across the polygon, combine categories into a score, or label the property/area safe or unsafe. Homicide (01) and sexual offences (02) are not published at this local resolution and are explicitly reported as unchecked. Resident-based rates are weak in city centres, airports, retail and nightlife areas with large non-resident populations; enforcement activity also affects some categories. Recorded incidents use PULSE report dates, can be revised, and are not a measure of all crime experienced. Fraud has a 2023 break and a narrower public-reported series from 2024.

NameTypeReqDescription
addressstringFree-text Irish address to geocode (used only if lat/lng absent).
include_division_trendbooleanInclude the latest four quarterly values for the wider Garda Division; default true.
latnumberLatitude (WGS84). Provide with lng, or use address instead.
lngnumberLongitude (WGS84). Provide with lat, or use address instead.
offence_groupsarrayOfficial broad offence codes 03–16. Omit for all locally published groups.
yearsintegerNumber of latest complete annual periods to return; default 3, maximum 10.

No output schema declared.

No examples provided.

resolve_location ~257

Resolve a free-text Irish address or place name to geographic coordinates (WGS84 lat/lng), returning ranked candidate matches. Use this first when the user gives an address, street, townland, or place name in Ireland, to confirm the correct location before calling other gaff-check tools — every candidate echoes its full resolved name so you (and the user) can sanity-check the match. If you already have exact lat/lng coordinates, you do not need this tool. Geocoding uses OpenStreetMap Nominatim and is best-effort: rural addresses and new estates may match poorly, and Eircodes only resolve where OSM mappers happen to have added them (there is no licensed Eircode lookup — if the user has only an Eircode, ask for the address or an approximate location instead). The confidence score ranks candidates within one query; it is not an absolute probability. Coordinates are WGS84 decimal degrees.

NameTypeReqDescription
limitintegerMaximum number of candidate matches to return (1–10, default 5)
querystringyesFree-text Irish address or place name, e.g. '25 Fitzwilliam Square, Dublin 2' or 'Salthill, Galway'

No output schema declared.

No examples provided.

sold_prices ~559

Look up actual sold prices of residential properties in Ireland from the official Property Price Register (PSRA), which records declared prices from stamp-duty filings since January 2010. Use this to see what properties actually sold for near a property of interest: filter by county (required — the register is organised by county), a free-text address fragment (e.g. a street or estate name), an Eircode routing key (first 3 characters, e.g. 'D06' — only present on more recent records), a date range, and/or a price range. Returns per sale: date, declared price in EUR, address as recorded, Eircode where recorded, new vs second-hand, and flags for not-full-market-price and VAT-exclusive sales. Results are newest first. Know the data's limits: addresses are free text typed from stamp-duty returns — spelling varies, many records lack Eircodes, and address matching is substring-based, so try street name alone before street + number. There is no floor area, so price-per-square-metre cannot be derived. Prices on new builds are often VAT-exclusive (flagged), and declared-price errors exist in the register. This tool reports records, not valuations. If the user has no county, ask them (or infer it from the address) before calling.

NameTypeReqDescription
address_querystringCase-insensitive substring to match against the recorded address, e.g. 'Fitzwilliam Square' or 'Gorey Hill'.
countystringyesIrish county, e.g. 'Dublin', 'Cork' (case-insensitive). One of: Carlow, Cavan, Clare, Cork, Donegal, Dublin, Galway, Kerry, Kildare, Kilkenny, Laois, Leitrim, Limerick, Longford, Louth, Mayo, Meath,…
date_fromstringEarliest sale date, ISO YYYY-MM-DD (register starts 2010-01-01). Default: 2 years before date_to.
date_tostringLatest sale date, ISO YYYY-MM-DD. Default: today.
eircode_routing_keystring3-character Eircode routing key, e.g. 'D06'. Matches only records that include an Eircode (mostly post-2022).
limitintegerMaximum sales to return, newest first (default 50).
max_pricenumberMaximum declared price in EUR.
min_pricenumberMinimum declared price in EUR.

No output schema declared.

No examples provided.

zoning ~329

Get the generalised land-use zoning for a location in Ireland, from the Myplan.ie composite of all current local authority development plans. Use this in property due diligence to learn what the land is zoned for — residential, agricultural, open space, industrial, mixed use, etc. Zoning tells you what could be built there (or next door), whether a site has development potential, and whether a use is likely permissible. Returns the generalised zone type (standardised across authorities, e.g. 'Existing residential'), the local authority's own original zone label and objective text, the development plan name with its validity dates, and a link to plan documents where available. Provide lat/lng (WGS84) or a free-text address (geocoded; resolved location echoed back). Important: generalised zoning is a standardised simplification that complements but does NOT replace the statutory development plan — zone boundaries are generalised, and specific objectives, conditions and designations (protected structures, flood zones, SACs) live in the written plan. Verify anything decision-critical against the local authority's plan via the link. Points on unzoned land (much of rural Ireland outside town plans) return no records; that means no zoning objective is mapped, not that development is impossible.

NameTypeReqDescription
addressstringFree-text Irish address to geocode (used only if lat/lng absent).
latnumberLatitude (WGS84). Provide with lng, or use address instead.
lngnumberLongitude (WGS84). Provide with lat, or use address instead.

No output schema declared.

No examples provided.

Common questions

What is the io.github.iarfhlaith/gaff-check MCP server?

io.github.iarfhlaith/gaff-check is an MCP server listed in the public MCP registry as io.github.iarfhlaith/gaff-check. Irish property due diligence: planning, prices, flood, radon, zoning, BER and crime context. This page covers its npm package (gaff-check).

Is the io.github.iarfhlaith/gaff-check MCP server safe to use?

io.github.iarfhlaith/gaff-check scores 82 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 20 September 2026. It declares no install or post-install scripts. 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 io.github.iarfhlaith/gaff-check MCP server expose?

io.github.iarfhlaith/gaff-check exposes 8 tools: resolve_location, planning_applications, sold_prices, radon_risk, zoning, and 3 more. Their descriptions and schemas cost roughly 3,178 tokens of context every time the server is loaded.

Is the io.github.iarfhlaith/gaff-check MCP server still maintained?

io.github.iarfhlaith/gaff-check is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What licence is the io.github.iarfhlaith/gaff-check MCP server under?

io.github.iarfhlaith/gaff-check declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.