# Us Auctions (npm · @pipeworx/mcp-us-auctions)

US Auctions MCP — every live US auction lot in the consolidated index, government AND commercial…

- Trust score: 82/100 (high trust)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- remote · `gateway.pipeworx.io`: 63/100, [markdown](https://verifymcp.io/servers/pipeworx-io-us-auctions/us-auctions-mcp.md), [page](https://verifymcp.io/servers/pipeworx-io-us-auctions/us-auctions-mcp)
- npm · `@pipeworx/mcp-us-auctions`: 82/100 (this document), [markdown](https://verifymcp.io/servers/pipeworx-io-us-auctions/pipeworx-mcp-us-auctions.md), [page](https://verifymcp.io/servers/pipeworx-io-us-auctions/pipeworx-mcp-us-auctions)

## Channel facts

- Registry: `npm`
- Package: `@pipeworx/mcp-us-auctions`
- Version: `0.2.0`
- 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**: 97/100
  - Source repository is publicly reachable at the declared URL.
  - Cryptographically verified build provenance (signed, bound to pipeworx-io/mcp-us-auctions).
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 6 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 62/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 1590 tokens (~265/item across 6 items; 6 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 6 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 7 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 Us Auctions MCP server?

Us Auctions runs locally as an npm package, launched with npx -y @pipeworx/mcp-us-auctions. 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-us-auctions -- npx -y @pipeworx/mcp-us-auctions
```

### Cursor

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

### VS Code

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

### Codex

```bash
codex mcp add pipeworx-io-us-auctions -- npx -y @pipeworx/mcp-us-auctions
```

### opencode

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

### OpenClaw

```bash
openclaw mcp add pipeworx-io-us-auctions --command npx --arg -y --arg @pipeworx/mcp-us-auctions
```

### Hermes

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

### Netclaw

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

### Vellum

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

### Other

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

## 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 82, +1)

No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-03 (score 81, +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-10-31 (score 80, +1)

No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.

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

First indexed and scored.

## MCP tools (6)

### `us_auctions_search` (~573 tokens)

Search live US auction lots across every source Pipeworx indexes — commercial auction houses (HiBid: ~1,900 US auctioneers, industrial liquidations, estate and equipment sales) and government surplus/seized/tax-deed sales (GovDeals, AllSurplus, PublicSurplus, Bid4Assets, IRS). Filter by free-text keyword (matched on the lot title, e.g. "forklift", "excavator", "F-150"), 2-letter state, asset_type (vehicle|equipment|realestate|electronics|other), segment (commercial|government), auction_house, max_price and closing_within_hours — or search geographically with near_zip + radius_miles ("forklifts within 50 miles of 94402"), which returns lots ordered by distance. Keyword search is full-text over the lot title AND description, so "cnc lathe" finds a lot titled "Haas TL-1" whose description says CNC lathe. Returns each lot with source, title, selling house, location, current bid, close time and a link. For what things actually SOLD for, use us_auctions_sold_comps instead.

Input parameters:

- `asset_type` (string): One of: vehicle | equipment | realestate | electronics | other.
- `auction_house` (string): Selling auctioneer, matched as a substring, e.g. "Silicon Valley Disposition".
- `closing_within_hours` (number|string): Only lots closing within this many hours from now.
- `keyword` (string): Free-text matched (case-insensitive) against the lot title, e.g. "forklift", "skid steer", "mac pro".
- `limit` (number|string): Max lots (1-100, default 25).
- `max_price` (number|string): Only lots whose current bid is at or below this. Note that a lot with no bids yet has no current bid and is excluded.
- `near_zip` (string): US 5-digit ZIP to search around, e.g. "94402". Combine with radius_miles for "what is up for auction near me". Results come back ordered by distance and carry distance_miles.
- `radius_miles` (number|string): Radius around near_zip, in miles (1-500, default 50). Ignored unless near_zip is given.
- `segment` (string): Restrict to one half of the market: government | commercial. Omit for both.
- `source` (string): Restrict to one source: hibid | govdeals | allsurplus | publicsurplus | bid4assets | irs | txauction.
- `state` (string): 2-letter state code of the item location, e.g. "CA", "TX".

### `us_auctions_closing_soon` (~227 tokens)

US auction lots ordered by soonest close time — the "what can I still bid on before it ends" view across commercial and government sources alike. Optionally filter by state, asset_type, segment, auction_house or keyword. Returns lots with hours remaining, current bid, location and link.

Input parameters:

- `asset_type` (string): One of: vehicle | equipment | realestate | electronics | other.
- `auction_house` (string): Selling auctioneer, substring match.
- `keyword` (string): Free-text search over lot title and description.
- `limit` (number|string): Max lots (1-100, default 25).
- `near_zip` (string): US 5-digit ZIP to search around, e.g. "94402".
- `radius_miles` (number|string): Radius around near_zip in miles (1-500, default 50).
- `segment` (string): government | commercial. Omit for both.
- `source` (string): Restrict to one source.
- `state` (string): 2-letter state code.

### `us_auction_events` (~306 tokens)

Upcoming US auction EVENTS — the sales themselves rather than individual lots ("Synthetic Fuels Company plant liquidation, 271 lots, Aug 28, Fremont CA"). Use this to answer "what auctions are happening near me next week" or "what is this auction house selling". Filter by state, keyword (sale title), auction_house, and a closing date range. Returns each sale with its house, location, lot count, local sale date and a link. Sale dates are the auctioneer's LOCAL calendar date — upstream publishes them without a timezone, so a precise instant is not available at the sale level; individual lot close times (us_auctions_closing_soon) are exact.

Input parameters:

- `auction_house` (string): Selling auctioneer, substring match, e.g. "Silicon Valley Disposition".
- `closes_after` (string): Only sales closing on or after this date (YYYY-MM-DD). Defaults to today.
- `closes_before` (string): Only sales closing on or before this date (YYYY-MM-DD).
- `keyword` (string): Free-text matched against the sale title, e.g. "liquidation", "estate", "machine shop".
- `limit` (number|string): Max sales (1-100, default 25).
- `min_lots` (number|string): Only sales with at least this many lots — useful for filtering out one-off listings.
- `state` (string): 2-letter state code where the sale is held.

### `us_auction_houses` (~141 tokens)

Which US auction houses Pipeworx covers, and how much they currently have live — name, home state, number of open sales and total lots across them. Use to find the auctioneers active in a state or in a niche ("who runs industrial liquidations in California"), then pass the name to us_auction_events or us_auctions_search. Ranked by live lot count.

Input parameters:

- `keyword` (string): Free-text matched against the house name or its sale titles.
- `limit` (number|string): Max houses (1-100, default 25).
- `state` (string): 2-letter state code of the sale location.

### `us_auctions_sold_comps` (~239 tokens)

Historical SOLD prices for US auction items — the final hammer price of closed lots, which no upstream site keeps but Pipeworx retains across both the commercial and government halves of the market. Use to answer "what do used forklifts actually fetch at auction" or to comp an asset before bidding. Filter by keyword (title match), asset_type, state and segment. Returns count, min/median/average/max final price, and recent examples. Only lots that closed with a recorded sale price above zero are counted — a closed lot that drew no bids is not a comp.

Input parameters:

- `asset_type` (string): One of: vehicle | equipment | realestate | electronics | other.
- `keyword` (string): Free-text title match, e.g. "forklift", "f-150", "cnc lathe".
- `limit` (number|string): Max example lots to return (1-50, default 10).
- `segment` (string): government | commercial. Commercial and government prices differ materially for the same asset — split them when it matters.
- `state` (string): 2-letter state code.

### `us_auctions_coverage` (~50 tokens)

Current US auction coverage: per-source active lot counts, open sale counts, retained sold comps, and when each source last refreshed. Use to gauge breadth and freshness before relying on the data.

## Diagnostics

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

## Score history

- 2026-11-05: 82
- 2026-11-04: 81
- 2026-11-03: 81
- 2026-11-02: 80
- 2026-11-01: 80
- 2026-10-31: 80
- 2026-10-30: 79
- 2026-10-29: 79

## Common questions

### What is the Us Auctions MCP server?

Us Auctions is an MCP server listed in the public MCP registry as io.github.pipeworx-io/us-auctions. US Auctions MCP, every live US auction lot in the consolidated index, government AND commercial… This page covers its npm package (@pipeworx/mcp-us-auctions).

### Is the Us Auctions MCP server safe to use?

Us Auctions scores 82 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 Us Auctions MCP server expose?

Us Auctions exposes 6 tools: us_auctions_search, us_auctions_closing_soon, us_auction_events, us_auction_houses, us_auctions_sold_comps, us_auctions_coverage. Their descriptions and schemas cost roughly 1,536 tokens of context every time the server is loaded.

### Is the Us Auctions MCP server still maintained?

Us Auctions 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 Us Auctions MCP server under?

Us Auctions declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.

### What did VerifyMCP test on the Us Auctions MCP server?

VerifyMCP ran 16 checks on Us Auctions, covering Malware scan, Known CVEs, Install scripts, Dependency health and 12 more. Endpoint Security and Transport & Reachability do not apply to an npm package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.

## Links

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