Gaff Check vs Onehome MCP
A side-by-side look at the Gaff Check and Onehome MCP MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Gaff Check for real estate work as a local process; choose Onehome MCP for real estate as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Gaff Check when
- You need dedicated capabilities in the Real Estate domain.
- You prefer a local stdio subprocess transport.
- You want tools like
resolve_location, planning_applications, sold_prices.
Choose Onehome MCP when
- You need dedicated capabilities in the Real Estate domain.
- You prefer a local stdio subprocess transport.
- You have the keys it needs:
ONEHOME_TOKEN, ONEHOME_MAGIC_LINK. - You want tools like
onehome_get_user, onehome_get_groups, onehome_get_session_context.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Real Estate | Real Estate |
| Quality signal | 61/100 · Good | 63/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | Not declared | Not declared |
| Pricing | Not declared | Not declared |
| Required env vars | None listed | ONEHOME_TOKENONEHOME_MAGIC_LINK |
| Verified owner | Community listing | Community listing |
| GitHub stars | 8 | 1 |
| Directory activity | 1 views 0 installs 0 upvotes | 1 views 0 installs 0 upvotes |
| Tools | 8 | 21 |
| Full listing | View Gaff Check | View Onehome MCP |
Tools & capabilities
Gaff Check tools 8
resolve_locationResolve 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.planning_applicationsFind 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.sold_pricesLook 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.radon_riskGet 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).zoningGet 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.flood_riskCheck 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.ber_contextGet 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.recorded_crime_contextGet 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.
Onehome MCP tools 21
onehome_get_userReturns the OneHome user profile + the consumer-share groups attached. Share member e-mails and the agent's e-mail/phones are omitted unless `include_contacts: true`. For full agent / registered users, queries the GraphQL `user` endpoint. For magic-link consumer-share sessions (where `user { }` is access-denied), falls back to the data captured during the `checkToken` exchange — email, contact id, group/savedSearch ids, and the agent who shared with you.onehome_get_groupsList the OneHome groups your agent has shared with you. Share member e-mails and the agent's e-mail/phones are omitted unless `include_contacts: true`. For full agent / registered users, returns the GraphQL `user.groups` list. For magic-link consumer-share sessions (a single shared group), synthesizes a one-entry list from the `checkToken` session context.onehome_get_session_contextReturns one entry per registered session — its `session_id`, auth_mode, token expiry, and session scope (group_id / saved_search_id / agent_id / contact_id / mls_id) the MCP bootstrapped from each checkToken exchange. `active_session_id` flags which session answers by default; per-listing routing uses the active session when its `mls_id` matches the listing's `~MLS` suffix, else the one session that matches (several matches error — pick one with `onehome_set_active_session`). Tools default unspecified `group_id` / `saved_search_id` arguments from the active session's context, so this is the easiest way to see what they'll default to. Single-session use (the common case) returns a one-entry `sessions[]`.onehome_get_saved_searchFetch the agent-curated saved search by its id (UUID). Returns the search's name, filter criteria (`filters[]`), polygon, listing count, and the full list of OSK listing ids that compose the consumer share (`listing_ids`). Pass `include_listing_ids: false` to suppress the listing-id array if you only need the metadata. This is the canonical consumer-readable endpoint; the by-groupId variant is agent-only. `saved_search_id` defaults to the MCP's session context when omitted.onehome_get_saved_search_with_listingsCombo tool: the "show me my saved homes" flow in a single round trip. Internally runs `GetSavedSearchBySearchId` to fetch the saved search (name, filters, polygon, listingIds) and then `GetSavedListings` to inflate those listingIds into full property records — the same two-call sequence as calling `onehome_get_saved_search` followed by `onehome_search_properties(saved_search_id=...)`, but exposed as one tool so the magic-link-to-listings consumer flow is a single MCP call. Returns `{ saved_search, listings, count, page_info }`. Both `saved_search_id` and `group_id` default to the magic-link session context. Sort defaults to `property.MajorChangeTimestamp DESC` (Newest). Listings are returned via the GraphQL listing-card projection (`buildGetSavedListings`), which does NOT include `PublicRemarks` — so there is no raw `description` to opt back into here. Use `onehome_get_property(listing_id)` per row when you need the full description for a specific listing.onehome_search_propertiesFetch listings inside a OneHome consumer-share. Two modes: - With `saved_search_id`: fetch the agent-curated collection (the standard 'Homes at <name>' view). The MCP first resolves the saved search's listingIds and then inflates them via listingsBySavedSearchId — this is the only mode that works for non-agent consumer accounts. - With just `group_id` and no `saved_search_id`: try the raw `listings(groupId, browseParameter)` endpoint. If page 0 comes back empty with no reported results (the access-restricted shape consumer-shares hit) AND the session context has a `savedSearchId` for that same group, the tool falls back to the saved-search path and marks the response `fell_back_to_saved_search: true`. If there's no fallback target it raises a clear error rather than silently returning empty. An empty later page (paging past the end) is returned as an empty page, never swapped for the saved-search collection. Both args default from the MCP's bootstrapped session context (the magic-link checkToken response) when neither is passed explicitly. Sort is `MajorChangeTimestamp DESC` ('Newest') unless overridden. `include_dislikes: false` by default — flip it on to include listings you've thumbs-downed in OneHome. Listings here are returned via the GraphQL listing-card projection, which does NOT include `PublicRemarks` — so there is no `description` field on search results and no `include_description` flag to opt into one. Each listing carries the structured `extracted_features` object instead. Use `onehome_get_property(listing_id)` per row when you need the full description for a specific listing.onehome_search_suggestionsCross-feed suggestion search by address, MLS number, or partial query. Bypasses the group/saved-search structure and hits the global suggestion endpoint — useful for "find an address" or "look up by MLS number". Returns id, address parts, beds/baths, list price, thumbnail per match. Inflate any result with `onehome_get_property`. Optional `group_id` scopes suggestions to one OneHome market.onehome_get_propertyFetch full details for a single OneHome listing by id or portal URL. Returns address, list / close / previous price, $/sqft, beds/baths/sqft, lot size (raw `lot_size` {area, units} plus the derived `lot_size_acres` — null, never 0, for condos / lotless listings), year built, lat/lng, status, HOA fee, annual tax, virtual-tour URL, the primary photo, and an `extracted_features` block (lake_front, hot_tub, basement, furnished, dock, community) keyword-parsed from the description. The raw `description` (PublicRemarks) is omitted by default — pass `include_description: true` to keep it; in most cases the extracted features cover what callers need. OneHome scopes every listing to a group/market — `group_id` defaults to the magic-link session context; pass it explicitly only if you need to query a different group.onehome_get_property_photosFetch the full media gallery for a OneHome listing. Returns one entry per image with Thumbnail / Medium / Large CDN URLs, dimensions, the listing-room description (LongDescription), and display order. Pass either `listing_id` or a portal URL.onehome_compare_propertiesFetch 2 or more OneHome listings and align their facts side-by-side. Each target may supply `listing_id` (preferred) or `url` (a portal URL). Returns the full per-property record (with `extracted_features` populated) per row. Per-target errors are captured per-row — one bad target will not fail the whole call. Calls are concurrent. The raw `description` is omitted from each row by default (`include_description: true` to keep it). The redundant `summary` table is also opt-in via `include_summary: true` — by default only `rows[]` is returned, which already carries every fact.onehome_bulk_getFetch up to 200 OneHome listings in a single call. Returns one structured row per input id (no side-by-side summary table — use `onehome_compare_properties` for that). Each row is either `{ listing_id, status: "ok", property }` on success or `{ listing_id, status, error_kind, retryable, error }` on failure (`status` = `error_kind`: `timeout` / `bridge_down` / `pending` are retryable, `protocol` / `other` are real misses) — one bad id never fails the whole call. Calls fan out concurrently against `ListingById`, capped at 6 in flight to avoid swamping the bridge; transient timeouts are retried once per row before being captured as an error. The whole call is bounded by an overall deadline: any row still unsettled comes back `status: "pending"` with a top-level `pending` count — re-run just those ids. The envelope reports `count` / `ok` / `errored`. `extracted_features` is populated per row automatically. The raw `description` (PublicRemarks) is omitted by default — pass `include_description: true` to keep it. `group_id` defaults to the magic-link session context.onehome_get_schoolsFetch the Local-Logic school data for a coordinate — separate primary and high-school lists, each entry with name, attributes (types/grades/programs/levels), and proximity (walking distance + straight-line distance). Returns an `error` field with HTTP details if the consumer session does not have access (the schools endpoint is sometimes agent-only). lat/lng usually come from `onehome_get_property` (`latitude` / `longitude`).- +9 more on the listing page
Ready-to-paste client configs
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
Gaff Check
{
"mcpServers": {
"gaff-check": {
"command": "npx",
"args": [
"-y",
"gaff-check"
]
}
}
}
Onehome MCP
{
"mcpServers": {
"onehome-mcp": {
"command": "npx",
"args": [
"-y",
"onehome-mcp"
],
"env": {
"ONEHOME_TOKEN": "YOUR_ONEHOME_TOKEN_HERE",
"ONEHOME_MAGIC_LINK": "YOUR_ONEHOME_MAGIC_LINK_HERE"
}
}
}
}
Frequently asked questions
Gaff Check is categorized under Real Estate and uses a local stdio subprocess. Onehome MCP belongs to Real Estate and uses a local stdio subprocess. Pick Gaff Check for real estate work and Onehome MCP for real estate.
Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.
Gaff Check has no declared pricing — check the project's own site. Onehome MCP has no declared pricing — check the project's own site. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add gaff-check and onehome-mcp as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Gaff Check has a quality signal of 61/100 (Good) with 1 views, 0 installs and 8 GitHub stars. Onehome MCP has 63/100 (Good) with 1 views, 0 installs and 1 GitHub stars.