Estatesales Net
NPM · @PIPEWORX/MCP-ESTATESALES-NET · 2 COMPONENTS
EstateSales.NET MCP — upcoming estate sales, by ZIP
Available components
Last scanned (4 hours ago)
Scores higher than 58% of npm servers
Category E-commerce
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security100
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- No production dependencies, so there is no dependency health to assess. View diagnostics → Pass
Provenance & Transparency71
- Repository presence not verified: we could not reach the forge to check. This is a gap on our side, not a finding about the repository. View diagnostics → Unverified
- Cryptographically verified build provenance (signed, bound to pipeworx-io/mcp-estatesales-net). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 3 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability71
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 489 tokens (~163/item across 3 items; 3 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management23
- Stability observed for 7 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 5 Nov 26 −5
- Provenance: pass → unverified ▼ security
- 3 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.
- 1 Nov 26 +2
- Tool safety: pass → unverified ▼ security
- Stability: Stability not yet verified: we do not have a sandbox capture of the MCP schema this version of the package serves yet. security
- Tool coverage: 100 → unverified ▼ functional
- Capabilities: pass → unverified ▼ functional
- Stability: unverified → 0.10 ▲ functional
- First check of Schema quality: unverified functional
- Package version: 0.2.0 → 0.2.1 functional
- 30 Oct 26 0
- Security disclosure: unverified → fail ▼ functional
- 29 Oct 26 80
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 5 Nov 2026 · Analysed npm/@pipeworx/mcp-estatesales-net@0.2.1
Provenance Verified
A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.
| Result | Verified |
|---|---|
| Ecosystem | npm |
| Reason | Verified |
| Discovered via | Registry attestation endpoint |
| Source repo | pipeworx-io/mcp-estatesales-net |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/pipeworx-io/mcp-estatesales-net/.github/workflows/publish.yml@refs/heads/main |
| Rekor log index | 3635927901 |
| Predicate type | SLSA build provenance https://slsa.dev/provenance/v1 |
| Subject digest | sha512:62398cd8908575d4779ca47aec33c7fab0a852d6b9f5ba5183d41a7463d8f96e4623cc788112af46ae004167300839d90154cd67b4370162b46f85411 |
Background: How many MCP packages publish verified provenance →
Dependencies 0 packages
| Packages resolved | 0 |
|---|---|
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
estatesales_companies ~128
Estate-sale companies operating near a US ZIP code, as listed on EstateSales.NET: company name, business address, phone, coordinates and their EstateSales.NET page. Answers "who runs estate sales in this area" — for hiring one, or for tracing which company is behind a sale found via estatesales_search.
| Name | Type | Req | Description |
|---|---|---|---|
| city | string | – | Optional city name, e.g. "Kansas City" |
| postal_code | string | yes | US ZIP code, e.g. "64111" |
| state_code | string | – | Optional 2-letter state code, e.g. "MO" |
No output schema declared.
No examples provided.
estatesales_sale ~118
One EstateSales.NET sale in full, by sale ID: name, description, terms, sale type, every scheduled date/time, coordinates, picture count, and the company or seller running it with their phone and page. The street address is included only once EstateSales.NET has published it — estate sales are usually at a private home and the site holds the address back until shortly before the sale.
| Name | Type | Req | Description |
|---|---|---|---|
| sale_id | number | yes | EstateSales.NET sale ID, e.g. 5065767 (the `id` from estatesales_search) |
No output schema declared.
No examples provided.
estatesales_search ~188
Upcoming estate sales, moving sales and estate auctions near a US ZIP code, from EstateSales.NET — the largest US estate-sale listing site. Returns each sale's ID, city/state/ZIP, coordinates, distance from the ZIP, sale type (on-site estate sale, moved offsite, online auction), start and end dates, and whether it runs today or tomorrow. These are UPCOMING sale listings, not sold prices — EstateSales.NET publishes no hammer prices.
| Name | Type | Req | Description |
|---|---|---|---|
| city | string | – | Optional city name, e.g. "Kansas City". Normally unnecessary — the ZIP resolves it. |
| postal_code | string | yes | US ZIP code, e.g. "64111". The site resolves it to its city page. |
| state_code | string | – | Optional 2-letter state code, e.g. "MO". Only needed to disambiguate; the ZIP alone normally resolves. |
No output schema declared.
No examples provided.
How do I install the Estatesales Net MCP server?
Estatesales Net runs locally as an npm package, launched with npx -y @pipeworx/mcp-estatesales-net. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · @pipeworx/mcp-estatesales-net
claude mcp add pipeworx-io-estatesales-net -- npx -y @pipeworx/mcp-estatesales-net
What is the Estatesales Net MCP server?
Estatesales Net is an MCP server listed in the public MCP registry as io.github.pipeworx-io/estatesales-net. EstateSales.NET MCP, upcoming estate sales, by ZIP. This page covers its npm package (@pipeworx/mcp-estatesales-net).
Is the Estatesales Net MCP server safe to use?
Estatesales Net scores 78 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 November 2026. It declares no install or post-install scripts. Its build provenance is signed and verified. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the Estatesales Net MCP server expose?
Estatesales Net exposes 3 tools: estatesales_search, estatesales_sale, estatesales_companies. Their descriptions and schemas cost roughly 434 tokens of context every time the server is loaded.
Is the Estatesales Net MCP server still maintained?
Estatesales Net is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the Estatesales Net MCP server under?
Estatesales Net declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.