Bigiron
NPM · @PIPEWORX/MCP-BIGIRON · 2 COMPONENTS
BigIron MCP — US ag/construction/livestock/transportation equipment auctions from bigiron.com.
Available components
Last scanned (19 hours ago)
Scores higher than 72% 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 & Transparency97
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to pipeworx-io/mcp-bigiron). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 4 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability67
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 603 tokens (~201/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 Management20
- Stability observed for 6 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.
- 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 +1
No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.
- 31 Oct 26 +15
- Malware scan: unverified → pass ▲ security
- 30 Oct 26 −14
- Malware scan: pass → unverified ▼ security
- Package version: 0.2.0 → 0.2.1 functional
- 29 Oct 26 79
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 4 Nov 2026 · Analysed npm/@pipeworx/mcp-bigiron@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-bigiron |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/pipeworx-io/mcp-bigiron/.github/workflows/publish.yml@refs/heads/main |
| Rekor log index | 3601437608 |
| Predicate type | SLSA build provenance https://slsa.dev/provenance/v1 |
| Subject digest | sha512:00acedd1b088b419f0d0c3901eba2531c9ea2d8cef9a80a9aa1cc749da703760daf503746b8427c5c23a167596c156de878fa9ed80de8a322d9b34578 |
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 →
bigiron_lot_detail ~166
Full detail for one bigiron.com lot by its URL slug: description, sale status, bid count, make/model/year, seller, location, category and (for active lots) current bid / Buy-It-Now price. Slugs come from bigiron_search or bigiron_sold_search result urls (the part after /Lots/). Bids are served through a 5-minute result cache, so the current bid can be up to five minutes old: near the close of an auction treat it as a lower bound, never as the final price. Sourced from bigiron.com/Lots/{slug}.
| Name | Type | Req | Description |
|---|---|---|---|
| slug | string | yes | BigIron lot URL slug, e.g. "2021-case-ih-2130-16-row-strip-till-planter" |
No output schema declared.
No examples provided.
bigiron_search ~189
Search active US ag/construction/livestock/transportation equipment auctions on bigiron.com — a national online timed-auction platform. Returns live listings with current bid, Buy-It-Now asking price (if offered — NOT a sold price), make/model/year, seller, location and auction close time. Bids are served through a 5-minute result cache, so the current bid can be up to five minutes old: near the close of an auction treat it as a lower bound, never as the final price. Sourced from bigiron.com/Search.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | number | – | Max lots to return, 1-20 (default 20) |
| page | number | – | Result page, starting at 1 (each page holds 20 lots) |
| query | string | yes | Search keywords, e.g. "tractor", "skid steer", "Angus bred heifers" |
No output schema declared.
No examples provided.
bigiron_sold_search ~196
Search CONFIRMED-SOLD equipment lots on bigiron.com for comps — title, make/model/year, quantity, seller, location and close date for lots that actually sold. IMPORTANT: bigiron.com does not expose the realized hammer price in this page shape (verified: 0/100 sampled sold lots carry a nonzero price field, even with 60+ bids) — final_price is always null with an explanatory note; num_bids is the closest available demand signal. Use bigiron_search for current asking prices instead. Sourced from bigiron.com/Search?filter=Sold.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | number | – | Max lots to return, 1-20 (default 20) |
| page | number | – | Result page, starting at 1 (each page holds up to 20 lots) |
| query | string | yes | Search keywords, e.g. "planter", "grain trailer", "combine tires" |
No output schema declared.
No examples provided.
How do I install the Bigiron MCP server?
Bigiron runs locally as an npm package, launched with npx -y @pipeworx/mcp-bigiron. 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-bigiron
claude mcp add pipeworx-io-bigiron -- npx -y @pipeworx/mcp-bigiron
What is the Bigiron MCP server?
Bigiron is an MCP server listed in the public MCP registry as io.github.pipeworx-io/bigiron. BigIron MCP, US ag/construction/livestock/transportation equipment auctions from bigiron.com. This page covers its npm package (@pipeworx/mcp-bigiron).
Is the Bigiron MCP server safe to use?
Bigiron scores 82 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 4 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 Bigiron MCP server expose?
Bigiron exposes 3 tools: bigiron_search, bigiron_sold_search, bigiron_lot_detail. Their descriptions and schemas cost roughly 551 tokens of context every time the server is loaded.
Is the Bigiron MCP server still maintained?
Bigiron is still listed as active in the MCP registry. We last reached this channel on 4 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 Bigiron MCP server under?
Bigiron declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.