# Estatesales Net (npm · @pipeworx/mcp-estatesales-net)

EstateSales.NET MCP — upcoming estate sales, by ZIP

- Trust score: 78/100 (medium)
- Change this week: −2
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- remote · `gateway.pipeworx.io`: 84/100, [markdown](https://verifymcp.io/servers/pipeworx-io-estatesales-net/estatesales-net-mcp.md), [page](https://verifymcp.io/servers/pipeworx-io-estatesales-net/estatesales-net-mcp)
- npm · `@pipeworx/mcp-estatesales-net`: 78/100 (this document), [markdown](https://verifymcp.io/servers/pipeworx-io-estatesales-net/pipeworx-mcp-estatesales-net.md), [page](https://verifymcp.io/servers/pipeworx-io-estatesales-net/pipeworx-mcp-estatesales-net)

## Channel facts

- Registry: `npm`
- Package: `@pipeworx/mcp-estatesales-net`
- Version: `0.2.1`
- Transport: `stdio`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-05.

- **Supply Chain Security**: 100/100
  - No malware found by supply-chain analysis.
  - No known CVEs affecting this package version or its production dependencies.
  - No install/post-install scripts declared.
  - No production dependencies, so there is no dependency health to assess.
- **Provenance & Transparency**: 71/100
  - 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.
  - Cryptographically verified build provenance (signed, bound to pipeworx-io/mcp-estatesales-net).
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 3 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 71/100
  - AI-judged instruction clarity (good).
  - 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.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 23/100
  - Stability observed for 7 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

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

### Claude

```bash
claude mcp add pipeworx-io-estatesales-net -- npx -y @pipeworx/mcp-estatesales-net
```

### Cursor

```json
{
  "mcpServers": {
    "pipeworx-io-estatesales-net": {
      "command": "npx",
      "args": [
        "-y",
        "@pipeworx/mcp-estatesales-net"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "pipeworx-io-estatesales-net": {
      "command": "npx",
      "args": [
        "-y",
        "@pipeworx/mcp-estatesales-net"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add pipeworx-io-estatesales-net -- npx -y @pipeworx/mcp-estatesales-net
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "pipeworx-io-estatesales-net": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "@pipeworx/mcp-estatesales-net"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add pipeworx-io-estatesales-net --command npx --arg -y --arg @pipeworx/mcp-estatesales-net
```

### Hermes

```yaml
mcp_servers:
  pipeworx-io-estatesales-net:
    command: "npx"
    args: ["-y", "@pipeworx/mcp-estatesales-net"]
```

### Netclaw

```json
{
  "McpServers": {
    "pipeworx-io-estatesales-net": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "@pipeworx/mcp-estatesales-net"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add pipeworx-io-estatesales-net -t stdio -c npx -a -y @pipeworx/mcp-estatesales-net
```

### Other

```json
{
  "mcpServers": {
    "pipeworx-io-estatesales-net": {
      "command": "npx",
      "args": [
        "-y",
        "@pipeworx/mcp-estatesales-net"
      ]
    }
  }
}
```

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-05 (score 78, −5)

- [security regression] Provenance: pass → unverified

### 2026-11-03 (score 83, +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.

### 2026-11-01 (score 82, +2)

- [security regression] 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.
- [functional regression] Tool coverage: 100 → unverified
- [functional regression] Capabilities: pass → unverified
- [functional improvement] Stability: unverified → 0.10
- [functional] First check of Schema quality: unverified
- [functional] Package version: 0.2.0 → 0.2.1

### 2026-10-30 (score 80, 0)

- [functional regression] Security disclosure: unverified → fail

### 2026-10-29 (score 80)

First indexed and scored.

## MCP tools (3)

### `estatesales_search` (~188 tokens)

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.

Input parameters:

- `city` (string): Optional city name, e.g. "Kansas City". Normally unnecessary — the ZIP resolves it.
- `postal_code` (string, required): 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.

### `estatesales_sale` (~118 tokens)

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.

Input parameters:

- `sale_id` (number, required): EstateSales.NET sale ID, e.g. 5065767 (the `id` from estatesales_search)

### `estatesales_companies` (~128 tokens)

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.

Input parameters:

- `city` (string): Optional city name, e.g. "Kansas City"
- `postal_code` (string, required): US ZIP code, e.g. "64111"
- `state_code` (string): Optional 2-letter state code, e.g. "MO"

## Diagnostics

Captured diagnostic sections: Provenance, Dependencies. The full working is on the page: https://verifymcp.io/servers/pipeworx-io-estatesales-net/pipeworx-mcp-estatesales-net#diagnostics

## Score history

- 2026-11-05: 78
- 2026-11-04: 83
- 2026-11-03: 83
- 2026-11-02: 82
- 2026-11-01: 82
- 2026-10-31: 80
- 2026-10-30: 80
- 2026-10-29: 80

## Common questions

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

## Links

- npm package: https://www.npmjs.com/package/@pipeworx/mcp-estatesales-net
- Socket report: https://socket.dev/npm/package/@pipeworx/mcp-estatesales-net
- Repository: https://github.com/pipeworx-io/mcp-estatesales-net
- Website: https://pipeworx.io/packs/estatesales-net
- Changelog RSS feed: https://verifymcp.io/servers/pipeworx-io-estatesales-net/pipeworx-mcp-estatesales-net.xml
- Changelog JSON feed: https://verifymcp.io/servers/pipeworx-io-estatesales-net/pipeworx-mcp-estatesales-net.json
- HTML version of this page: https://verifymcp.io/servers/pipeworx-io-estatesales-net/pipeworx-mcp-estatesales-net