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.

BidProwl

REMOTE · BIDPROWL.COM

US government surplus auctions: search live lots by ZIP radius, sold prices and Flip Scores.

Available components

+4 this week 67 Trust /100

Last scanned (5 hours ago)

Scores higher than 57% of remote servers

Reachable. Last reached 18 Oct 2026.

Category E-commerce

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →

Endpoint Security63
Transport & Reachability100
Schema Quality & AI Usability64
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 706 tokens (~100/item across 7 items; 7 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management27
  • Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage82
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 45% of tool parameters carry a description.Partial
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 7 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 8 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a current MCP spec version (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.

  • 17 Oct 26 +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.

  • 15 Oct 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.

  • 13 Oct 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.

  • 12 Oct 26 +1
    • Stability: unverified → 0.07 ▲ functional
  • 10 Oct 26 63

    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 18 Oct 2026 · Probed https://bidprowl.com/api/v1/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=bidprowl.com CN=YE2,O=Let's Encrypt,C=US 3 Oct 2026 1 Jan 2027 ECDSA 256 ECDSA-SHA384 53d842728854a53ca8d367005366d4923bb
SANs: *.bidprowl.com, bidprowl.com
CN=YE2,O=Let's Encrypt,C=US (CA) CN=Root YE,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 ECDSA 384 ECDSA-SHA384 4df3b15dd6c0784c507cd37b58e6f115
CN=Root YE,O=ISRG,C=US (CA) CN=ISRG Root X2,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 ECDSA-SHA384 872165fc34b6e5fba8add5b3705fb53a
CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 SHA256-RSA 6c8f1dc727c7117f7baf853ac980f9cd

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of bidprowl.com. — Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
com. present 19718 13 Verified
bidprowl.com. absent Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200
Header Value
strict-transport-security max-age=63072000; includeSubDomains; preload
x-content-type-options nosniff
x-frame-options DENY
referrer-policy strict-origin-when-cross-origin
permissions-policy camera=(), microphone=(), geolocation=()

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://bidprowl.com/api/v1/mcp Verified 200
http (plaintext) http://bidprowl.com/api/v1/mcp HTTPS enforced 301 https://bidprowl.com/api/v1/mcp
MCP tools · 7 exposed · ~595 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
flip_score ~34

BidProwl's deal score for a live listing, with its condition-adjusted tier.

NameTypeReqDescription
idstringyes–

No output schema declared.

No examples provided.

get_api_usage ~49

This API key's plan, monthly call limit, calls used, calls remaining and when the quota resets (first of next month, UTC). Free to call: it does not count against the quota.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

get_listing ~29

Fetch a single listing by its BidProwl id or slug.

NameTypeReqDescription
idstringyes–

No output schema declared.

No examples provided.

get_sold_history ~151

The actual sold lots behind a comps number, newest close first: title, final price (cents), close date, state, source, BidProwl link. Pass one of category, item (tracked item slug) or q (free text, matched like a listing title), plus optional state. Paginate with cursor.

NameTypeReqDescription
categorystring––
cursorstring–next_cursor from the previous call
itemstring–Pro: tracked item slug, e.g. forklift
limitinteger–Default 25
qstring–Pro: free text, e.g. 2015 ford f150
statestring––

No output schema declared.

No examples provided.

search_listings ~138

Search 90,000+ live US government surplus auction listings from 26 official sources. Supports keyword, category, state, ZIP-radius, and price filters.

NameTypeReqDescription
categorystring––
limitinteger–Results per page, default 25
pageinteger––
price_max_usdnumber––
querystring–Keyword search, e.g. 'forklift'
radius_milesinteger––
sortstring––
statestring–2-letter US state code
zipstring–Center a radius search on this ZIP

No output schema declared.

No examples provided.

sold_comps ~78

Sold-price stats from 250,000+ closed government auctions, nearly all from the last 12 months. Category+state aggregates, or exact percentile comps for a live listing via listing_id.

NameTypeReqDescription
categorystring––
listing_idstring–Pro: exact comps for this live listing
statestring––

No output schema declared.

No examples provided.

sold_comps_batch ~116

Up to 25 sold_comps lookups in one call (100 on Pro+), each costing one API call. Each query is a listing id, a tracked item slug ("forklift"), a category ("vehicles"), or text naming a tracked item ("2015 Ford F150"). Item-level and per-listing answers need Pro or Pro+; categories work on every plan. Amounts are in cents.

NameTypeReqDescription
queriesarrayyes–
statestring–Default 2-letter state for item and category queries

No output schema declared.

No examples provided.

Install

How do I install the BidProwl MCP server?

BidProwl is a hosted endpoint at https://bidprowl.com/api/v1/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

remote · bidprowl.com

# add to Claude Code
claude mcp add --transport http com-bidprowl-bidprowl 'https://bidprowl.com/api/v1/mcp'
Common questions

What is the BidProwl MCP server?

BidProwl is an MCP server listed in the public MCP registry as com.bidprowl/bidprowl. US government surplus auctions: search live lots by ZIP radius, sold prices and Flip Scores. This page covers its hosted endpoint (https://bidprowl.com/api/v1/mcp).

Is the BidProwl MCP server safe to use?

BidProwl scores 67 out of 100 on VerifyMCP. 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 BidProwl MCP server expose?

BidProwl exposes 7 tools: search_listings, get_listing, sold_comps, flip_score, get_api_usage, and 2 more. Their descriptions and schemas cost roughly 595 tokens of context every time the server is loaded.

Does the BidProwl MCP server require authentication?

No. We connected to BidProwl without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the BidProwl MCP server still maintained?

BidProwl is still listed as active in the MCP registry. We last reached this channel on 18 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.