Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Troostwijk

NPM · @PIPEWORX/MCP-TROOSTWIJK · 2 COMPONENTS

Troostwijk Auctions MCP — European industrial + insolvency liquidation auction lots…

+3 this week 82 Trust /100

Last scanned (1 hour ago)

Scores higher than 72% of npm servers

Category E-commerce

Trust breakdown (7 categories)

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-troostwijk). View diagnostics → Pass
  • Clear OSI-approved license (MIT).Pass
  • Actively maintained (last published 7 days ago).Pass
  • Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability65
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 873 tokens (~218/item across 4 items; 4 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 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 5 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
Changelog

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 +3
    • Stability: unverified → 0.23 ▲ functional
  • 30 Oct 26 0
    • Security disclosure: unverified → fail ▼ functional
  • 29 Oct 26 79

    First indexed and scored.

Diagnostics

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-troostwijk@0.2.0

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-troostwijk
Certificate issuer https://token.actions.githubusercontent.com
Certificate SAN https://github.com/pipeworx-io/mcp-troostwijk/.github/workflows/publish.yml@refs/heads/main
Rekor log index 3560569149
Predicate type SLSA build provenance https://slsa.dev/provenance/v1
Subject digest sha512:7513c8bd25f0de2a95269801e272a7a149bb1db122c21137aea12ba6413bbf24b7e6f1772d85477e2be329b83605a73b67dea3707023cefe5046d9bd9

Background: How many MCP packages publish verified provenance →

Dependencies 0 packages
Packages resolved 0
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 4 exposed · ~818 tokens

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 →

Tool Tokens
troostwijk_categories ~74

List Troostwijk Auctions' category tree (industrial equipment, vehicles, real estate, construction, metalworking, woodworking, transport and more) with the category_path each one needs for troostwijk_search_lots / troostwijk_sold_comps. Sourced from troostwijkauctions.com's own navigation menu.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

troostwijk_lot_detail ~221

Full detail for one Troostwijk lot within its auction: auction description, current/final bid, sale outcome, bid count, location. auction_slug comes from a search/sold-comps result url (the part after /en/a/); pass display_id to pick a specific lot out of a multi-lot auction (omit for a single-lot auction). 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 troostwijkauctions.com/en/a/{auction_slug}.

NameTypeReqDescription
auction_slugstringyesAuction URL slug, e.g. "afhaalveiling-pvc-laminaat-en-parket-vloeren-A1-46249"
display_idstring–Optional specific lot display id within a multi-lot auction, e.g. "A1-46249-6" (from a search result's display_id field)

No output schema declared.

No examples provided.

troostwijk_search_lots ~253

Browse CURRENTLY-OPEN lots in one Troostwijk Auctions category — European industrial equipment, vehicles, real estate and bankruptcy/insolvency liquidations across NL/DE/BE/UK/PL/RO/IT and more. Returns live current bid, bid count, location and close time per lot. Get category_path from troostwijk_categories first. 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 troostwijkauctions.com/en/c/{category_path}.

NameTypeReqDescription
category_pathstringyesCategory path from troostwijk_categories, e.g. "agricultural/tractors/087e1bb8-5fb8-4e98-b5d8-1a0133422ae0"
countrystring–Optional ISO 3166-1 alpha-2 country code to filter by lot location, e.g. "nl", "de", "be"
pagenumber–Result page, starting at 1 (each page holds up to 48 lots)

No output schema declared.

No examples provided.

troostwijk_sold_comps ~270

Realized sale-price comps from Troostwijk Auctions' recently-closed auctions. VERIFIED: closed lots with saleTerm CLOSED_RESERVE_PRICE_ALLOCATED or GUARANTEED_SALE_CLOSED carry a real hammer price in current_bid, and this tool returns ONLY those (outcome:"sold") — reserve-not-met, declined and still-pending lots are filtered out, never reported as a price. Scans recently-closed auctions (bounded by max_auctions) and optionally filters by a keyword in the lot title and/or country. Sourced from troostwijkauctions.com/en/auctions?auctionBiddingStatuses=BIDDING_CLOSED plus each matching auction's lot list.

NameTypeReqDescription
countrystring–Optional ISO 3166-1 alpha-2 country code to filter closed auctions by location, e.g. "nl", "de", "be"
max_auctionsnumber–How many recently-closed auctions to scan for sold lots, 1-10 (default 5). Higher finds more matches but costs more upstream requests per call.
querystring–Optional keyword to match against lot titles, e.g. "generator", "tractor" (case-insensitive substring; seller-written titles may be in the source country's language)

No output schema declared.

No examples provided.

Install

How do I install the Troostwijk MCP server?

Troostwijk runs locally as an npm package, launched with npx -y @pipeworx/mcp-troostwijk. 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-troostwijk

# add to Claude Code
claude mcp add pipeworx-io-troostwijk -- npx -y @pipeworx/mcp-troostwijk
Common questions

What is the Troostwijk MCP server?

Troostwijk is an MCP server listed in the public MCP registry as io.github.pipeworx-io/troostwijk. Troostwijk Auctions MCP, European industrial + insolvency liquidation auction lots… This page covers its npm package (@pipeworx/mcp-troostwijk).

Is the Troostwijk MCP server safe to use?

Troostwijk 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 Troostwijk MCP server expose?

Troostwijk exposes 4 tools: troostwijk_categories, troostwijk_search_lots, troostwijk_lot_detail, troostwijk_sold_comps. Their descriptions and schemas cost roughly 818 tokens of context every time the server is loaded.

Is the Troostwijk MCP server still maintained?

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

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