govauctions.app MCP server

• get_api_usageFree

  This key's usage for the current month: total calls and the separate valuation allowance (which comps, sold history, trend and flip-score draw down), plus the reset date. Call it to pace a long run instead of hitting a 429 mid-task. Every other signed-in tool result already carries the same numbers in `_meta.usage`, so this is rarely needed. Free: it does not count against either allowance. Requires sign-in or an API key.

• get_comp_coverageFree

  How much sold-price data we hold per category for a market, and which categories can never be priced. Check this before building on the comps tools — it is the honest answer about what we cannot do. Works signed out.

• get_flip_scoreFree

  GovAuctions Flip Score resale signal for one live lot, from any source, in any market with sold-price comps (valued against that market's comp archive): estimated value, effective bid, discount, and the link to the lot on its source site. Pass the lot id as it appears in a govauctions.app lot URL. Requires sign-in or an API key.

• get_listingFree

  Get one live GSA listing by its id (facts only). Works signed out.

• get_price_trendFree

  Month-by-month median sale price for an item, plus the first-to-last change — 'is this category softening?'. Computed from the same comps as get_sold_comps, so it never contradicts that range. Returns an empty series when too few months clear the sample threshold. Requires sign-in or an API key.

• get_sold_compsFree

  Sold-price comps for a described item, computed across the full government-surplus market in any market listed in `country`. Signed out: coverage (how many comparable sales, confidence, a coarse price band) plus `categoryStats`, the 25th/median/75th percentile of every sale in the item's category (in `state` when it has enough sales). Signed in or with an API key: the 25th/median/75th percentile for this item itself. `liveListingsUrl` links to the live auctions for the same item. A miss says which kind it is: reason `insufficient_comps` (too few comparable sales yet) is worth retrying, reason `category_not_priceable` (real-estate) never is — that category cannot be priced from a title. A catch-all `category` such as `miscellaneous` is not refused: it is dropped and the item is priced on its title alone, with `requestedCategory` and `categoryDropped` echoed back — check the resolved `category` and `confidence` before trusting the range. `pricedAs`, when present, is what was actually priced: a spelling fix, or the listing title with its lot count, lot number or serial removed. When the `category` you sent holds nothing like the item and another category clearly does, the range comes from that one, with `requestedCategory` and `categoryOverridden` echoed back. A miss can still carry `categoryStats` when the item's category is clear, and `retryHint` when the query was a long listing title: retry with just the brand and model.

• get_sold_comps_batchFree

  get_sold_comps for a list of items in one call. Each query is either a string ('2015 Ford F-150') or an object with its own q/category/country/state. Each item costs one valuation lookup, exactly as if sent alone; an item that comes back without a range is not charged. If the monthly allowance runs out part-way, the items already priced are returned and `batch.truncated` names the rest. Batch size is capped by plan (10 on the free allowance). Requires sign-in or an API key.

• get_sold_historyFree

  The individual archived sales behind an item: title, final price, sale month and state, plus the range they produce. Use when you want the evidence rather than just the number. Query-anchored — describe an item; there is no way to list the archive. Requires sign-in or an API key.

• search_listingsFree

  Search live GSA federal-surplus auction listings (facts only — no images). Filter by state, category, keyword, price, or distance from a US ZIP code. Works signed out (up to 25 rows per page). Raw listings cover sanctioned federal sources; sold-price comps span the full market.

• –Code scanremote-only server, no package to scann/a
• Live reliabilityremote reachable in 1746ms20/20
• Tool poisoning9 tool descriptions checked15/15
• Auth qualityopen endpoint, read-only tools10/15
• Maintenancelast push 27 days ago15/15
• Maintainer identityendpoint served from the registry-verified namespace domain8/10

Safety score

91/100

higher than 85% of 48,255 servers

Tools

9

the typical server has 7

Tools that change things

0%

typical: 0%. Fewer write tools means less an agent can break

Uptime

100%

of our recent checks; the typical remote server answers 100%

Response time

289 ms

faster than 49% of 30,031 servers

govauctions.app: common questions

Is govauctions.app MCP server safe?

Yes, by our scan: it is graded A (91/100). Read the govauctions.app safety report

How do I install govauctions.app?

It runs remotely at govauctions.app. Add it to Claude Code, Cursor, VS Code or Claude Desktop with the snippets above, or call it through the mcp.market gateway without installing anything.

Does govauctions.app need an API key?

Not as far as the registry entry and our scan can tell: no credentials are declared or required.

Is govauctions.app maintained?

The last commit was 28 days ago (2026-10-07). The latest release is v1.0.3.

Is govauctions.app up?

100% of our last 28 checks got an answer. We check remote servers about four times a day.

How does govauctions.app compare with other MCP servers?

safety score 91/100 (higher than 85% of 48,255 servers); tools 9 (the typical server has 7); tools that change things 0% (typical: 0%. Fewer write tools means less an agent can break). Full comparison.