The full upstream README, mirrored here for reference. Install config, tool schemas, adoption signals, and an original overview live on the Estatesales Net listing page.
Upcoming estate sales, moving sales and estate auctions near a US ZIP code, from EstateSales.NET — the largest US estate-sale listing site — plus the companies that run them.
Part of Pipeworx — an MCP gateway connecting AI agents to 1683+ live data sources.
estatesales_search(postal_code) — the upcoming sales nearest a ZIP: sale
ID, type, city/state/ZIP, coordinates, distance, schedule, start/end dates.estatesales_sale(sale_id) — one sale in full: name, description, terms,
every scheduled date, coordinates, picture count, and the company running it
with phone and page. Street address only once the site has released it (see
below).estatesales_companies(postal_code) — estate-sale businesses working that
ZIP: name, business address, phone, coordinates, listing tier.Keyless. No account, no token, no registration.
EstateSales.NET does publish a documented beta REST API
(https://github.com/vintage-software/EstateSales.NET-Api), and the obvious
reading is that this pack should use it. It should not. That API is
seller-side only — every endpoint is scoped to your own OrgId:
It is how an estate-sale company lists its own sales. There is no search
endpoint in it at all, its keys are issued from an estate-sale company account
(/account/company/api-keys), and a key would only ever return our own empty
org. It cannot answer a buyer's question, so no PLATFORM_ESTATESALES_KEY
exists and none would help.
What this pack reads instead is the site's own public buyer-facing data — the structured JSON the website itself renders from, no credentials involved.
An estate sale is usually held at a private home, so EstateSales.NET withholds
the street address until shortly before the sale (showAddress,
utcShowAddressAfter, showAddressType). estatesales_sale returns the
address only when the site has already published it; otherwise it returns
address_published: false, the release time in address_visible_after_utc,
and a note. Coordinates and city/ZIP are always present, since the site
publishes those from the start.
Do not route around this. The embargo is the publisher's decision about someone's home, not a technical quirk.
EstateSales.NET lists upcoming sales. It publishes no hammer prices and no
realized-sale data, so nothing here is a comp. Every response says so in a
price_data field.
https://www.estatesales.net/{ST}/{City}/{ZIP} — city sale listing.https://www.estatesales.net/{ST}/{City}/{ZIP}/{saleId} — sale detail.https://www.estatesales.net/companies/{ST}/{City}/{ZIP} — company listing.Things worth not rediscovering:
script
tag with id="estatesales-net-state" and type="application/json", holding
{"NGRX_STATE": …} — Angular transfer state. Sales are at
feature.cityViewState.filteredSales, a sale at
feature.traditionalSaleViewState.entitiesById[saleId], companies at
feature.companiesCityViewState.companies. Anchor on the script tag's id:
matching type="application/json" alone also hits the analytics blocks./XX/x/64111 redirects to
/MO/Kansas-City/64111, and /XX/x/00000/{saleId} redirects to the sale's
real path. Never hand-build the city slug.filteredSaleCount and totalSaleCount report the real depth (e.g. 64111:
20 listed, 61 filtered, 97 total). There is no page parameter — the site
loads the rest client-side. Report the counts rather than implying 20 is all.{"_type":"DateTime","_value":"…"}; this pack
unwraps them to ISO strings.GET /api/sales/{id} is public and keyless, but returns only
bookkeeping (org id, type, timestamps) — no address, dates, description or
pictures. The page state has all of those, which is why the pack uses it.
GET /api/public-sales/{id} (the official API's path) is 403 without a
seller token./api/sales?postalCodeNumber=… answers HTTP 400
"Permissions denied on filter" — the filter is not public. That error means
the endpoint exists, not that the site is down.Add to your MCP client (Claude Desktop, Cursor, Windsurf, etc.):
tools/list at https://gateway.pipeworx.io/estatesales-net/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 1683+ 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/estatesales_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