Estatesales Net MCP server

@pipeworx/estatesales-net

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 1576+ live data sources.

Tools

ID, type, city/state/ZIP, coordinates, distance, schedule, start/end dates.

• estatesalessearch(postalcode) — the upcoming sales nearest a ZIP: sale

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).

• estatesalessale(saleid) — one sale in full: name, description, terms,

ZIP: name, business address, phone, coordinates, listing tier.

• estatesalescompanies(postalcode) — estate-sale businesses working that

Auth

Keyless. No account, no token, no registration.

The official EstateSales.NET API is a different thing, and it is not usable here

EstateSales.NET does publish a documented beta REST 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:

GET    /api/public-sales/org/{OrgId}      your org's sales
GET    /api/public-sales/{saleId}         403 without your org's token
POST   /api/public-sales/                 create a sale
PUT    /api/public-sales/{saleId}         edit a sale
POST   /api/public-sales/{saleId}/publish
POST   /api/sale-dates/ · /api/sale-pictures/

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 PLATFORMESTATESALESKEY 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.

Addresses are embargoed by the publisher, and this pack honors that

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). estatesalessale returns the address only when the site has already published it; otherwise it returns addresspublished: false, the release time in addressvisibleafter_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.

No prices

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.

Data sources

• 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:

Shortened. The full README is on GitHub.