The full upstream README, mirrored here for reference. Install config, tool schemas, adoption signals, and an original overview live on the Xome listing page.
US residential foreclosure/bank-owned (REO)/short-sale auction calendar and property facts from xome.com.
Part of Pipeworx — an MCP gateway connecting AI agents to 1684+ live data sources.
| Tool | What it returns |
|---|---|
xome_search | Browse listings by state (+ optional county): property facts (beds/baths/sqft/year built/lot size/occupancy), sale type, auction_status/bid_deadline. Not the bid/sale price — see xome_property_detail. |
xome_property_detail | Full detail for one listing: property facts, the exact sale event (date + courthouse venue address), sale terms, and the bid/sale price with an explicit status label. |
The dollar amount is not in the page's schema.org markup (Offer.price
is absent even on a confirmed-sold listing — verified: a "Sold to Bank"
listing's Offer shows only availability: "https://schema.org/SoldOut",
no price). It lives instead in the same page's Next.js App Router RSC flight
payload (self.__next_f.push([1, "..."]) chunks) as an embedded
"auctionInfo":{...} object carrying bidAmount, bidType and
liveEventStatus. This pack extracts it (regex + brace-matching on the
concatenated, unescaped flight chunks) rather than shipping calendar-only.
Every price is labeled by its actual state — never presented as a bare number a caller could mistake for something it isn't:
liveEventStatus | Meaning | bidType | Is it a real price? |
|---|---|---|---|
Marketing | Auction hasn't started | Est. Opening Bid / Starting Bid | No — an estimate (often $0/unset) or a minimum, never a bid |
Post Auction | Bidding closed, outcome undecided | High Bid Received | No — the top bid, not a completed sale |
Sold to Bank / any Sold* | Sale complete | Sale Price | Yes — the real realized price. "Sold to Bank" means the foreclosing lender took the property back (a common, real outcome when no third-party bid clears the lender's credit bid) — still a completed sale with a real price. |
None. Keyless, no login required to browse listings.
xome.com/sitemap/auctions/sitemap-auctionrecords0.xml.gz — bulk discovery
of individual listing URLs.xome.com/auctions/{state}[/{county}] — paginated listing pages; the
ItemList application/ld+json block carries full property facts for
every row with no extra request per item.xome.com/auctions/{listing-slug} — one listing's RealEstateListing /
SingleFamilyResidence+Product / Offer / SaleEvent JSON-LD graph,
plus the embedded auctionInfo RSC data for price.Disallows account/dashboard paths, /api/, /signalr/ and a few report
endpoints — none of which this pack touches; everything here comes from the
plain public listing HTML already served to any visitor. Per Bruce's
2026-09-01 ruling, public unauthenticated content is buildable regardless of
robots; this pack still deliberately stays off every disallowed path since
the same data is already present on the page it fetches.
Add to your MCP client (Claude Desktop, Cursor, Windsurf, etc.):
tools/list at https://gateway.pipeworx.io/xome/mcp returns the tools in the table
above plus the shared Pipeworx meta-tools — ask_pipeworx,
discover_tools, search_within, remember/recall and the rest of the
gateway-wide set. So the tool count you see is larger than this table: a
single-pack endpoint currently lists roughly 30 shared tools alongside the
pack's own. The connection's initialize response states its exact scope, and
is the authoritative answer for a given day.
This is deliberate, not multiplexing by accident. The meta-tools are what let a
scoped connection answer a question this pack does not cover — via
ask_pipeworx, which routes across the whole catalog — without you adding a
second MCP server. There is currently no way to mount a pack endpoint without
them; if the extra schemas cost you more context than the routing is worth,
connect to the full gateway once rather than to several pack endpoints.
Or connect to the full Pipeworx gateway to get every pack's tools listed directly, instead of just this one's:
Both URLs reach the same gateway and the same 1684+ data sources. The
only difference is which pack's tools are listed directly; ask_pipeworx
reaches all of them from either one.
No account needed for the first calls. Inspect any tool: GET https://gateway.pipeworx.io/v1/tools/xome_search. Find one: POST https://gateway.pipeworx.io/v1/tools/search_packs with {"query":"..."}.
This package also runs as a local stdio MCP server — no Pipeworx account, no gateway round-trip:
Or run it directly to confirm it starts:
It speaks MCP over stdin/stdout and answers initialize/tools/list/tools/call
for only this pack's tools — none of the shared meta-tools the gateway
connection above adds. Same source, same tools, no ask_pipeworx routing.
Instead of calling tools directly, you can ask questions in plain English — this works on the pack endpoint above as well as on the full gateway:
The gateway picks the right tool and fills the arguments automatically.
MIT