FindA.Sale
REMOTE · MCP.FINDA.SALE · 2 COMPONENTS
Find yard sales, garage sales, auctions, flea markets and resale shops, and search items for sale.
Available components
Last scanned (1 hour ago)
Scores higher than 64% of remote servers
Unreachable for 2 days in a row. Last reached 3 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 Security11
- TLS not yet verified: we couldn't open a connection to check the certificate. View diagnostics → Unverified
- Authorisation not yet verified: we couldn't confirm whether this endpoint requires it. View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS not yet verified: we couldn't read the response headers to check for it. View diagnostics → Unverified
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability0
- Transport check failed: declared streamable-http, but we couldn't connect to verify it. See how to fix → View diagnostics → Fail
Schema Quality & AI Usability0
- Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.Unverified
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
- Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Tool Safety0
- Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Capabilities0
- Capabilities not yet verified: we couldn't read the endpoint's capabilities.Unverified
Unverified: 5 categories
Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.
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.
- 4 Nov 26 0
- Endpoint reachability: reachable → unreachable ▼ security
- HSTS header: fail → unverified ▼ security
- Stability: 0.33 → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- TLS certificate: pass → unverified ▼ security
- Authorization: partial → unverified ▼ security
- Transport: pass → fail ▼ security
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- First check of Schema quality: unverified functional
- 1 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.
- 30 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.
- 28 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.
- 26 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.
- 25 Oct 26 0
- Stability: unverified → 0.03 ▲ functional
- 24 Oct 26 71
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 5 Nov 2026 · Probed https://mcp.finda.sale/mcp
TLS unreached
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of mcp.finda.sale. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| sale. | present | 58006 | 8 | Verified |
| finda.sale. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Inconclusive
We could not reach the endpoint well enough to judge its authorisation posture.
| Result | Inconclusive |
|---|
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://mcp.finda.sale/mcp | Unreachable | ||
| http (plaintext) | http://mcp.finda.sale/mcp | HTTPS enforced |
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 →
find_item_for_sale Find Item For Sale ~119
Find a specific thing someone wants to buy (furniture, a collectible, a tool) across current public sales, optionally in one city and price range. Returns up to 10 matches with links to cite.
| Name | Type | Req | Description |
|---|---|---|---|
| city | string | – | Only items in sales in this city |
| maxPrice | number | – | Maximum price in US dollars |
| minPrice | number | – | Minimum price in US dollars |
| query | string | yes | What the shopper is looking for, e.g. "Hummel figurine" or "oak dresser" |
No output schema declared.
No examples provided.
get_item Get Item Details ~61
Get one publicly listed item: title, description, price, condition, photos, and the sale it belongs to (title, city, dates, link).
| Name | Type | Req | Description |
|---|---|---|---|
| itemId | string | yes | The FindA.Sale item id, as returned by a search tool |
No output schema declared.
No examples provided.
get_sale Get Sale Details ~81
Get one public sale: dates, city, approximate location, description, photos, organizer name and rating, and up to 25 available items. Street addresses are never included; the sale page shows them to signed-in shoppers from the day before the sale.
| Name | Type | Req | Description |
|---|---|---|---|
| saleId | string | yes | The FindA.Sale sale id, as returned by a search tool |
No output schema declared.
No examples provided.
get_sales_starting_soon Get Sales Starting Soon ~137
List public sales starting in the next few days (default 7, max 14). Good for "what sales are this weekend near X" questions.
| Name | Type | Req | Description |
|---|---|---|---|
| city | string | – | City name, e.g. "Chicago" |
| daysAhead | integer | – | How many days ahead to look (default 7, max 14) |
| saleType | string | – | Sale type code: ESTATE (whole-house sale), YARD (yard or garage sale), AUCTION, FLEA_MARKET, RETAIL (shop or storefront, incl. consignment), DORM_DASH (dorm move-out). |
No output schema declared.
No examples provided.
get_trending_sales Get Trending Sales ~123
List current public sales with the most shopper interest and recent activity, optionally in one city or of one sale type.
| Name | Type | Req | Description |
|---|---|---|---|
| city | string | – | City name, e.g. "Grand Rapids" |
| limit | integer | – | Max results (default 10, max 25) |
| saleType | string | – | Sale type code: ESTATE (whole-house sale), YARD (yard or garage sale), AUCTION, FLEA_MARKET, RETAIL (shop or storefront, incl. consignment), DORM_DASH (dorm move-out). |
No output schema declared.
No examples provided.
list_categories List Categories ~36
List item categories that currently have items for sale, with item counts. Use a name from this list as the category filter in search_items.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_cities List Cities ~84
List cities with current public sales on FindA.Sale, busiest first, with active sale counts and a browse link for each city. Filter by state to narrow the list.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Max cities to return (default 100, max 500) |
| state | string | – | State or province code, e.g. "MI" or "ON" |
No output schema declared.
No examples provided.
list_sale_types List Sale Types ~45
List the sale type codes FindA.Sale uses (yard sale, whole-house sale, auction, flea market, shop, dorm move-out) with a short description of each.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
search_items Search Items ~185
Search items listed for sale across current public FindA.Sale sales by keyword, with optional category, condition, price range and city filters. Returns item title, price, condition, photos and links to the item and its sale.
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | – | Category name from list_categories, e.g. "Furniture" |
| city | string | – | Only items in sales in this city |
| condition | string | – | Condition filter, e.g. "NEW", "LIKE_NEW", "USED" |
| limit | integer | – | Max results (default 20, max 50) |
| priceMax | number | – | Maximum price in US dollars |
| priceMin | number | – | Minimum price in US dollars |
| query | string | yes | Keywords, e.g. "brass lamp" or "oak dresser" |
| sortBy | string | – | Sort order (default relevance) |
No output schema declared.
No examples provided.
search_sales Search Sales ~324
Find current public sales (yard and garage sales, whole-house sales, auctions, flea markets, shops) by keyword, city, ZIP, map point, date range or sale type. Returns sale summaries with approximate location and a link to each sale page. Street addresses are never included.
| Name | Type | Req | Description |
|---|---|---|---|
| city | string | – | City name, e.g. "Grand Rapids" |
| endDate | string | – | Only sales starting on or before this date (YYYY-MM-DD) |
| lat | number | – | Latitude for a radius search (use with lng) |
| limit | integer | – | Max results (default 20, max 50) |
| lng | number | – | Longitude for a radius search (use with lat) |
| minConfidence | number | – | Minimum listing confidence 0 to 1. 0.7 = organizer-verified, 0.4 = corroborated by a third party. |
| query | string | – | Keywords to match in the sale title or description, e.g. "mid-century" or "tools" |
| radiusKm | number | – | Radius in kilometers for lat/lng search (default 25) |
| saleType | array | – | Sale type code: ESTATE (whole-house sale), YARD (yard or garage sale), AUCTION, FLEA_MARKET, RETAIL (shop or storefront, incl. consignment), DORM_DASH (dorm move-out). |
| startDate | string | – | Only sales starting on or after this date (YYYY-MM-DD) |
| zip | string | – | 5-digit US ZIP code |
No output schema declared.
No examples provided.
How do I install the FindA.Sale MCP server?
FindA.Sale is a hosted endpoint at https://mcp.finda.sale/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 · mcp.finda.sale
claude mcp add --transport http sale-finda-findasale 'https://mcp.finda.sale/mcp'
What is the FindA.Sale MCP server?
FindA.Sale is an MCP server listed in the public MCP registry as sale.finda/findasale. Find yard sales, garage sales, auctions, flea markets and resale shops, and search items for sale. This page covers its hosted endpoint (https://mcp.finda.sale/mcp).
Is the FindA.Sale MCP server safe to use?
FindA.Sale scores 75 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 FindA.Sale MCP server expose?
FindA.Sale exposes 10 tools: search_sales, get_sale, search_items, get_item, list_cities, and 5 more. Their descriptions and schemas cost roughly 1,195 tokens of context every time the server is loaded.
Does the FindA.Sale MCP server require authentication?
Its publisher declares no required credentials for FindA.Sale. We have not been able to confirm that against the live endpoint, and a server can require authorisation without declaring it here.
Is the FindA.Sale MCP server still maintained?
FindA.Sale is still listed in the MCP registry, though our most recent checks did not reach this channel. We last reached this channel on 3 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.