govauctions.app
REMOTE · GOVAUCTIONS.APP
Live listings, sold prices and resale scores from GovAuctions.app, the public surplus-auction site.
Available components
Last scanned (15 hours ago)
Scores higher than 84% of remote servers
Reachable. Last reached 21 Nov 2026.
Category E-commerce
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 Security80
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability62
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 1573 tokens (~174/item across 9 items; 9 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 Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage84
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 52% 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 9 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 10 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
Checks we ran (13)
- TLS certificate
- Authorization
- HTTPS
- HSTS header
- DNSSEC
- Transport
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Does not apply to this hosted endpoint (2)
- Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
- Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
The score does not measure everything. What the score does not measure →
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.
- 11 Nov 26 +1
- Stability: 0.97 → pass security
- 10 Nov 26 −1
- Stability: pass → 0.97 functional
- 6 Nov 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 3 Nov 26 0
- Tool “get_sold_comps” rewrote its description, which is the text the model reads security
- 20 Oct 26 0
- Tool “get_price_trend” rewrote its description, which is the text the model reads security
- Tool “get_api_usage” rewrote its description, which is the text the model reads security
- Tool “get_comp_coverage” rewrote its description, which is the text the model reads security
- Tool “get_flip_score” rewrote its description, which is the text the model reads security
- Tool “get_sold_comps_batch” rewrote its description, which is the text the model reads security
- Tool “get_sold_history” rewrote its description, which is the text the model reads security
- 13 Oct 26 0
- Tool “get_sold_comps” rewrote its description, which is the text the model reads security
- 10 Oct 26 0
- Tool “get_listing” rewrote its description, which is the text the model reads security
- Tool “get_sold_comps” rewrote its description, which is the text the model reads security
- Tool “search_listings” rewrote its description, which is the text the model reads security
- Schema quality: 1176 → 1387 ▼ functional
- Tool coverage: 47% → 52% ▲ functional
- New tool “get_sold_comps_batch” functional
- “search_listings” reworded the description of “limit” cosmetic
- 28 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
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 21 Nov 2026 · Probed https://govauctions.app/api/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=govauctions.app | CN=WE1,O=Google Trust Services,C=US | 14 Oct 2026 | 12 Jan 2027 | ECDSA 256 | ECDSA-SHA256 | 6790683d30fc1dc0e1090c1a9364849 |
| SANs: govauctions.app, *.govauctions.app | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of govauctions.app. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| app. | DS published | 23684 | 8 | Verified |
| govauctions.app. | No DS | 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=(self), payment=(), usb=(), serial=(), bluetooth=(), hid=(), midi=(), idle-detection=(), display-capture=(), xr-spatial-tracking=() |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://govauctions.app/api/mcp | Verified | 200 | |
| http (plaintext) | http://govauctions.app/api/mcp | HTTPS enforced | 301 | https://govauctions.app/api/mcp |
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 →
get_api_usage API usage ~101
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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_comp_coverage Comp coverage ~62
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.
| Name | Type | Req | Description |
|---|---|---|---|
| country | string | – | – |
No output schema declared.
No examples provided.
get_flip_score Flip Score ~92
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.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | – |
No output schema declared.
No examples provided.
get_listing Get a listing ~32
Get one live GSA listing by its id (facts only). Works signed out.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | – |
No output schema declared.
No examples provided.
get_price_trend Price trend ~122
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.
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | – | – |
| country | string | – | – |
| q | string | yes | Item description, e.g. 'forklift' |
| state | string | – | Optional 2-letter state/region code. |
No output schema declared.
No examples provided.
get_sold_comps Sold-price comps ~514
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.
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | – | – |
| country | string | – | – |
| include | string | – | Set to "comps" to also return the individual sales the range was computed from (title, final price, sale month, state). Requires a key; the number returned is capped by plan. Not served for EU market… |
| limit | integer | – | How many underlying sales to return with include=comps. Capped by plan. |
| q | string | yes | Item description, e.g. '2015 Ford F-150' |
| state | string | – | Optional 2-letter state/region code for a regional range. Falls back to the national range when that state has too few sales; the response's `scope` field says which you got. |
No output schema declared.
No examples provided.
get_sold_comps_batch Sold-price comps, many at once ~160
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.
| Name | Type | Req | Description |
|---|---|---|---|
| country | string | – | Default market for every query. |
| queries | array | yes | – |
| state | string | – | Default 2-letter state/region code for every query. |
No output schema declared.
No examples provided.
get_sold_history Sold history ~138
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.
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | – | – |
| country | string | – | – |
| limit | integer | – | How many sales to return. Capped by plan. |
| q | string | yes | Item description, e.g. '2015 Ford F-150' |
| state | string | – | Optional 2-letter state/region code. |
No output schema declared.
No examples provided.
search_listings Search live GSA listings ~286
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.
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | – | – |
| country | string | – | – |
| limit | integer | – | Rows per page. Signed out, capped at 25. |
| offset | integer | – | – |
| priceMax | number | – | – |
| priceMin | number | – | – |
| q | string | – | Title keyword |
| radiusMiles | number | – | Radius from `zip`, in miles (default 100, max 500). Requires `zip`. |
| sort | string | – | Result order. Default is soonest-ending (nearest-first when `zip` is given). Use `newest` to order by the lot's own listing date, newest first - that is the ordering a recurring "what is new" check n… |
| source | string | – | – |
| state | string | – | 2-letter state code |
| zip | string | – | US 5-digit ZIP to search around. Limits results to lots within radiusMiles, orders them nearest-first, and adds distanceMiles to each. |
No output schema declared.
No examples provided.
How do I install the govauctions.app MCP server?
govauctions.app is a hosted endpoint at https://govauctions.app/api/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 · govauctions.app
claude mcp add --transport http app-govauctions-govauctions 'https://govauctions.app/api/mcp'
What is the govauctions.app MCP server?
govauctions.app is an MCP server listed in the public MCP registry as app.govauctions/govauctions. Live listings, sold prices and resale scores from GovAuctions.app, the public surplus-auction site. This page covers its hosted endpoint (https://govauctions.app/api/mcp).
Is the govauctions.app MCP server safe to use?
govauctions.app scores 84 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 govauctions.app MCP server expose?
govauctions.app exposes 9 tools: search_listings, get_listing, get_sold_comps, get_sold_comps_batch, get_flip_score, and 4 more. Their descriptions and schemas cost roughly 1,507 tokens of context every time the server is loaded.
Does the govauctions.app MCP server require authentication?
No. We connected to govauctions.app without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the govauctions.app MCP server still maintained?
govauctions.app is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What did VerifyMCP test on the govauctions.app MCP server?
VerifyMCP ran 13 checks on govauctions.app, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.