Propraven vs Homes MCP
A side-by-side look at the Propraven and Homes MCP MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Propraven for real estate work as a local process; choose Homes 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 Propraven when
- You need dedicated capabilities in the Real Estate domain.
- You prefer a local stdio subprocess transport.
- You have the keys it needs:
PROPRAVEN_API_KEY. - You want tools like
parcel_lookup, parcel_search, parcel_compare.
Choose Homes MCP when
- You need dedicated capabilities in the Real Estate domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: other.
- You want tools like
homes_search_properties, homes_get_property, homes_calculate_mortgage.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Real Estate | Real Estate |
| Quality signal | 60/100 · Good | 63/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | Not declared | other |
| Pricing | Not declared | Free |
| Required env vars | PROPRAVEN_API_KEY | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 0 | 0 |
| Directory activity | 1 views 0 installs 0 upvotes | 2 views 0 installs 0 upvotes |
| Tools | 8 | 21 |
| Full listing | View Propraven | View Homes MCP |
Tools & capabilities
Propraven tools 8
parcel_lookupResolve a single US parcel by identifier (canonical state_fips:county_fips:parcel_id, PropRaven UUID, street address, or APN). An ID returns the canonical PropRaven parcel card (GET /api/v1/parcels/{id}): identity, current owner, valuation, geography and source provenance. An address or APN runs the text search and returns up to 5 candidates — re-call with the chosen candidate's `lookup_id` to get the card. Use when the user names one specific property. Do NOT use when ranking multiple parcels (use parcel_compare) or when filtering by criteria (use parcel_search). Example: `parcel_lookup({ query: "37:119:12104406" })` or `parcel_lookup({ query: "2232 Wilmore Dr, Charlotte, NC 28203" })`. Free read — never purchases anything.parcel_searchText search over US parcels (GET /api/v1/search/full): pass `q` as a city, owner name, address fragment or APN, optionally narrowed by `field`, `state` and `city`. Returns `{ results, total, totalCapped, page, pages, hasMore, nextCursor }` (default 50 per page, max 200); each result carries parcel_id, apn, county_fips, state_fips, site_address, city, zip5, owner_name, total_value, latitude, longitude (in search rows `parcel_id` is the PropRaven UUID and `county_fips` is 5-digit), plus `lookup_id`, added by this server — pass it to parcel_lookup / parcel_compare. Page with `cursor` (the previous response's `nextCursor`) rather than `page`; `total` is a floor when `totalCapped` is true. Use when the user wants properties matching a name, place or address fragment. Do NOT use when looking up a single known property (use parcel_lookup) or ranking a known set (use parcel_compare). Free read — never purchases anything.parcel_compareFetch 2–25 parcels side by side so they can be ranked against criteria. For each parcel it reads the free parcel card (GET /api/v1/parcels/{id}: identity, owner, valuation, building, lot) and, unless include_risks=false, the hazard block (GET /api/v1/parcels/{id}/risks), and returns a normalized `summary` plus the raw `card` / `risks`. The calling agent does the per-criterion scoring and final ranking. NEVER buys the paid parcel report or any other paid product. Use when the user has identified candidate properties (often from parcel_search) and wants them ranked. Do NOT use to discover new candidates (use parcel_search) or for a single property (use parcel_lookup + hazard_score). For deed or permit timelines call sales_history / permits_history per parcel. The `criteria` argument is returned verbatim so the agent can pin its scoring to the user's intent.owner_pierceList the parcels titled under an owner-of-record name (GET /api/v1/owners/{name}/portfolio). Returns the matched owner name, a portfolio `summary` (count, total_value, total_acreage, by_state, truncated) and the `properties` list (parcel_id, county_fips, state_fips, address, assessed values, last sale, match_basis, match_confidence). This matches owner-name SPELLINGS — it is NOT a verified corporate, parent-subsidiary or beneficial-ownership link. Use when the user names a person, LLC, trust, or company and wants to see what is titled under that name. Do NOT use when starting from a parcel (use parcel_lookup, which returns owner inline). `ticker` is best-effort: it runs an owner-name search (GET /api/v1/owners/search) for the ticker text and uses the top match, returning the candidates under `resolution` — verify them, or call again with `name`. `state` filters the returned properties client-side (the summary stays portfolio-wide). Free read — never purchases anything.hazard_scoreHazard profile for a parcel (GET /api/v1/parcels/{id}/risks): flood (FEMA zone + SFHA flag), wildfire, seismic, windstorm, air quality and crime blocks, plus withhold_gate / identity_gate provenance. Use when the user asks about a property's risk profile — insurance pricing, underwriting, or due diligence. Do NOT use to compare multiple parcels (use parcel_compare, which includes each parcel's hazards). Every requested key is present: the value, or null when PropRaven does not hold it. Coverage varies by hazard. Free read — never purchases anything (this is not the paid risk-score product).valuation_estimateValue fields for a parcel from its free card (GET /api/v1/parcels/{id}): market_value, avm_value with avm_confidence / avm_method, total / land / improvement assessed value, tax, last sale price and date, price_per_sqft. Numbers are normalized to JSON numbers (null = not held). Use when the user asks for a property's value, market estimate, AVM, or wants to compare assessed vs market. Do NOT use as a substitute for an appraisal — this is a modeled estimate. Historical AVM (as_of) is not supported; the tool returns the current snapshot. Free read — never purchases anything.permits_historyTimeline of building / construction / demolition permits filed against a parcel (GET /api/v1/parcels/{id}/permits). Each permit includes permit_number, permit_type, permit_status, description, work_class, issued_date, completed_date, estimated_cost, contractor_name (where disclosed). Use when the user asks about construction activity, recent renovations, planned work, or wants to detect a property that's actively changing. Do NOT use to find properties WITH recent permits across a market. At most 100 permits are returned (newest first). `permit_count` is the parcel's TRUE count when `permit_count_basis` is "exact"; "capped" means it is the size of the 100-row window (a floor); `truncated: true` means the parcel has more permits than returned. `since` / `types` filter the returned window only (`returned_count` is after filtering). Coverage varies by county. Free read — never purchases anything.sales_historyDeed / transaction timeline for a parcel (GET /api/v1/parcels/{id}/deeds): recorded sales and transfers with recording and sale dates, sale price (where disclosed), grantor (seller), grantee (buyer), deed/document type and book/page. Use when the user asks about a property's transaction history, flip activity, or holding period. Do NOT use to find properties with recent sales market-wide, or to estimate current market value (use valuation_estimate). Note: 13 states do not disclose sale prices on deeds (KS, MS, TX, UT, WY, etc.). `event_count` is the number of events returned. `status` says where they came from: per_deed (deed rows), rollup_events (dated rollup entries), summary_only (no events served, but `known_deed_count` deeds are known — see known_deed_count_basis), or none. UCC liens are NOT available here (they are only in the paid parcel report, which this server never buys). Free read — never purchases anything.
Homes MCP tools 21
homes_search_propertiesSearch homes.com listings by free-text location (city, ZIP, neighborhood). Optionally filter by property_type (single_family/condo/townhouse/land/mobile/multi_family), listing_type (for_sale/sold/for_rent/open_houses/new_construction), and sort (newest). Slugifies the location into homes.com's URL routing (e.g. 'Atlanta, GA' + condo + for_sale → /atlanta-ga/condos-for-sale/). Parses the embedded Schema.org JSON-LD to return each listing's address, price, beds/baths, sqft, primary photo, listing agent + brokerage, and the homes.com property URL. `location` is required and must contain Latin letters or digits — a blank or unsluggable location (e.g. only punctuation or non-Latin script) is rejected with an error rather than returning an empty result. KNOWN CAP: homes.com server-renders ~40 listings per page; the response carries `truncated: true` + `total_estimated` when the market has more. To enumerate a busy market, price-band or sub-area your search until each segment fits under the cap. Read-only; safe to call repeatedly.homes_get_propertyFetch a property's full homes.com record. Pass `url` — the full property detail URL (e.g. from a homes_search_properties result's `url` field). Parses the page's Schema.org JSON-LD plus DOM-side sections to return address, lat/lng, beds/baths, sqft, year built, price, status, listing agent + brokerage, highlights, estimated monthly payment, total views, Matterport tour URL, floorplan URLs, schools, HOA fee, lot_size_sqft plus the derived lot_size_acres (round(lot_size_sqft / 43560, 2); both null — never 0 — for condos and listings with no lot), parking, heating/cooling, MLS ID/source, and date posted/modified. Also returns `extracted_features` (lake_front, hot_tub, basement, furnished, dock, community) derived server-side from the listing description so callers don't have to keyword-parse marketing prose. Pass `include_price_history: true` to inline the same data `homes_get_property_history` returns (`listing_events`, `ownership_events`, `lien_events`, `events_normalized`) under `price_history`. Pass `include_tax_history: true` to inline `homes_get_tax_history` records under `tax_history`. Both are off by default; opting in costs nothing extra over the dedicated tools (same page fetch). The raw `description` is omitted by default; pass `include_description: true` to opt back in. `listing_agent` carries name / job title / profile url only; pass `include_agent_contact: true` for the agent's telephone and email. Read-only; safe to call repeatedly.homes_calculate_mortgageLocal-only mortgage payment calculator. Returns a full PITI breakdown (principal + interest, property tax, insurance, HOA, PMI) and total interest over the life of the loan. No network call — fully deterministic, safe to use for scenario comparison without burning a fetch. Provide either `down_payment` OR `down_payment_percent`; defaults to 20%. Property tax can be given as `property_tax_annual` or `property_tax_rate` (% of home price). PMI applies automatically when LTV > 80% and `pmi_rate` is provided.homes_compare_propertiesFetch 2 or more homes.com properties and align their facts side-by-side. Each target supplies a `url` — the full homes.com property URL (e.g. from a homes_search_properties result's `url` field). Returns the full per-property record (with server-side `extracted_features`, `hoa_monthly_usd`, `days_on_market`, `price_drop_*`, `lot_size_sqft` + the derived `lot_size_acres`, and `portal_url_hyperlink`). Per-target errors are captured per-row — one bad target will not fail the whole call: a failed row carries `status` = `error_kind` (`timeout` / `bridge_down` / `protocol` / `other`) plus `retryable` and `error`, and the envelope reports `count` / `ok` / `errored`. Calls are concurrent and bounded by an overall deadline: any row still unsettled comes back `status: "pending"` (retryable) with a top-level `pending` count — re-run just those targets. The raw `description` is omitted by default; pass `include_description: true` to keep the marketing prose. `listing_agent` omits the agent's telephone/email unless `include_agent_contact: true`. The cross-row `summary` table duplicates per-property fields (~30% of response weight); it is OPT-IN via `include_summary: true`.homes_calculate_affordabilitySolve for the maximum home price you can afford under the standard 28/36 DTI rule. Inputs: monthly income, recurring monthly debts (car loans, student loans, etc.), down payment, interest rate, and optional property-tax rate / insurance / HOA / loan term. Output: max home price, the binding constraint (front-end vs back-end), and the full PITI breakdown at that price. Same math across the realty MCP cohort (@chrischall/realty-core). No network — pure local math.homes_get_property_photosThe full photo gallery for a homes.com listing. homes.com's JSON-LD only exposes one primary image, so this tool scrapes every <img> tag on the property detail page and filters to the homes.com CDN. Pass `url` — the full homes.com property URL or path (e.g. from a homes_search_properties result's `url` field). Returns `{ property_id, url, count, photos: [{ url, position, alt? }] }`. Read-only; safe to call repeatedly.homes_healthcheckRound-trips a small public www.homes.com URL (/robots.txt) through ContextMint Bridge (your signed-in browser tab) and returns diagnostics: the bridge's role (host/peer/null), port, version, the extension link (linked / pair pending / not attached / never answered), the elapsed round-trip time, and a plain-English hint distinguishing 'bridge never came up' from 'extension not connected' from 'this browser can't serve a capability' from 'real www.homes.com-side problem'. Read-only, no auth required. Call this when a real tool fails and you want to know which hop broke.homes_get_property_historyDEPRECATED — prefer `homes_get_history` (combined timelines + tax) or `homes_get_property({ url, include_price_history: true })`. Same data, fewer round trips. Will be removed in a future major version. Three timelines for a homes.com property in one call: `listing_events`, `ownership_events`, `lien_events`. Also returns `events_normalized` mapped onto the cross-MCP enum. Each `events_normalized` row is `{ date, type, price?, price_change_pct?, list_to_sale_pct? }` — `price_change_pct` only on `PriceChange` rows; every other row carries homes.com's "List to Sale" figure as `list_to_sale_pct` (e.g. the sale-to-list ratio on a `Sold` row), never as a price change.homes_get_tax_historyDEPRECATED — prefer `homes_get_history` (combined timelines + tax) or `homes_get_property({ url, include_tax_history: true })`. Same data, fewer round trips; note that `homes_get_history` returns the tax array as `tax_records` (not `records`). Will be removed in a future major version. Year-by-year property-tax records: tax paid, total assessed value, land/improvement split.homes_get_historyCombined history endpoint — replaces `homes_get_property_history` + `homes_get_tax_history` with a single fetch. Returns `{ property_id, url, listing_events, ownership_events, lien_events, events_normalized, tax_records }`. Pass `url` — the full property detail URL. Series are `[]` when the listing doesn't carry that section. Cross-MCP-normalized `events_normalized` carries the same enum across siblings (Listed/PriceChange/Pending/Contingent/Sold/Withdrawn/Relisted/Delisted). Each `events_normalized` row is `{ date, type, price?, price_change_pct?, list_to_sale_pct? }` — `price_change_pct` only on `PriceChange` rows; every other row carries homes.com's "List to Sale" figure as `list_to_sale_pct` (e.g. the sale-to-list ratio on a `Sold` row), never as a price change. Read-only; safe to call repeatedly.homes_get_nearby_listingsScrape the nearby-links section of a homes.com detail page (the tabbed list of `<ul id="nb-Property">` near the bottom of the page) and return the nearby active listings. Pass `url` (the property whose neighborhood to inspect). By default returns the For Sale tab; pass `include_rentals: true` to also include the Rentals tab. Optional `limit` caps the count. Returns `{ property_id, url, count, listings: [{ property_id, url, address?, tab }] }`. Note: the nearby section is a curated cross-link list, not a comparable-sales set — only URL + address are exposed (no price/beds/baths/sqft/photo). To enrich a row, call `homes_get_property` on its url. Read-only; safe to call repeatedly.homes_get_market_reportFetch homes.com's recently-sold listings for a city/ZIP/neighborhood and derive a market summary: count, median sale price, and average $/sqft across the sample. Pass `location` — free-text (e.g. 'Brooklyn, NY', '30311'). `location` is required and must contain Latin letters or digits — a blank or unsluggable location (e.g. only punctuation or non-Latin script) is rejected with an error rather than returning an empty result. Returns `{ region, slug, sold_summary, sample_sold }`. Note: homes.com's sold page typically returns ~40 recent listings — this is a sample-based summary, not an exhaustive market index. Read-only.- +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.
Propraven
{
"mcpServers": {
"propraven": {
"command": "npx",
"args": [
"-y",
"@propraven/mcp"
],
"env": {
"PROPRAVEN_API_KEY": "YOUR_PROPRAVEN_API_KEY_HERE"
}
}
}
}
Homes MCP
{
"mcpServers": {
"homes-mcp": {
"command": "npx",
"args": [
"-y",
"homes-mcp"
]
}
}
}
Frequently asked questions
Propraven is categorized under Real Estate and uses a local stdio subprocess. Homes MCP belongs to Real Estate and uses a local stdio subprocess. Pick Propraven for real estate work and Homes 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.
Propraven has no declared pricing — check the project's own site. Homes MCP is listed as free. Auth: other. 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 propraven and homes-mcp as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Propraven has a quality signal of 60/100 (Good) with 1 views, 0 installs and 0 GitHub stars. Homes MCP has 63/100 (Good) with 2 views, 0 installs and 0 GitHub stars.