Comprehensive Model Context Protocol server for managing Home Assistant through AI assistants.
FindA.Sale is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
What it does
Find yard sales, garage sales, auctions, flea markets and resale shops, and search items for sale.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http finda-sale-mcp https://mcp.finda.sale/mcp
# 2 — ask your agent for something these tools do
# search_sales, get_sale, search_items and 7 more
FindA.Sale costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. Nothing here runs on your machine and nothing runs on ours: this server answers at its publisher’s own address, and what you install is the connection straight to it.
This is a public server: it answers at its publisher’s own address and this marketplace is not in the path. Claude Code registers it in one command; --scope user makes it available in every project. The transport below is http, as the publisher's own manifest declares it.
claude mcp add --scope user --transport http finda-sale-mcp https://mcp.finda.sale/mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
One config entry pointing straight at the publisher’s own address — this marketplace is not in the path, and nothing from this listing executes on your machine.
10 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| query | string | no | Keywords to match in the sale title or description, e.g. "mid-century" or "tools" |
| city | string | no | City name, e.g. "Grand Rapids" |
| zip | string | no | 5-digit US ZIP code |
| lat | number | no | Latitude for a radius search (use with lng) |
| lng | number | no | Longitude for a radius search (use with lat) |
| radiusKm | number | no | Radius in kilometers for lat/lng search (default 25) |
| startDate | string | no | Only sales starting on or after this date (YYYY-MM-DD) |
| endDate | string | no | Only sales starting on or before this date (YYYY-MM-DD) |
| saleType | array | no | 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). |
| limit | integer | no | Max results (default 20, max 50) |
| minConfidence | number | no | Minimum listing confidence 0 to 1. 0.7 = organizer-verified, 0.4 = corroborated by a third party. |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| saleId | string | yes | The FindA.Sale sale id, as returned by a search tool |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| query | string | yes | Keywords, e.g. "brass lamp" or "oak dresser" |
| category | string | no | Category name from list_categories, e.g. "Furniture" |
| city | string | no | Only items in sales in this city |
| priceMin | number | no | Minimum price in US dollars |
| priceMax | number | no | Maximum price in US dollars |
| condition | string | no | Condition filter, e.g. "NEW", "LIKE_NEW", "USED" |
| limit | integer | no | Max results (default 20, max 50) |
| sortBy | string | no | Sort order (default relevance) |
Get one publicly listed item: title, description, price, condition, photos, and the sale it belongs to (title, city, dates, link).
| Parameter | Type | Required | Notes |
|---|---|---|---|
| itemId | string | yes | The FindA.Sale item id, as returned by a search tool |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| state | string | no | State or province code, e.g. "MI" or "ON" |
| limit | integer | no | Max cities to return (default 100, max 500) |
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.
No parameter schema on file.
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.
No parameter schema on file.
List current public sales with the most shopper interest and recent activity, optionally in one city or of one sale type.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| city | string | no | City name, e.g. "Grand Rapids" |
| saleType | string | no | 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). |
| limit | integer | no | Max results (default 10, max 25) |
List public sales starting in the next few days (default 7, max 14). Good for "what sales are this weekend near X" questions.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| city | string | no | City name, e.g. "Chicago" |
| saleType | string | no | 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). |
| daysAhead | integer | no | How many days ahead to look (default 7, max 14) |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| query | string | yes | What the shopper is looking for, e.g. "Hummel figurine" or "oak dresser" |
| city | string | no | Only items in sales in this city |
| minPrice | number | no | Minimum price in US dollars |
| maxPrice | number | no | Maximum price in US dollars |
- Every tool — any call limit is its publisher’s, not ours
- No card, and mcprush charges nothing for it
- Runs at its publisher’s own address — this marketplace is not in the path
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install FindA.Sale or to call it, at any volume.
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
| Term | Level | What it prices | Points |
|---|---|---|---|
| capability-exposure | minimal | capability blast radius (minimal) — client exposure if the model is manipulated | −0 |
| coverage-honesty | manifest | inspection depth (manifest) — how much of the target the scan could see | −4 |
What the scan could actually read
A grade is only as meaningful as its coverage, so the scanner publishes its own depth before it publishes its result.
The scan read each tool’s name, description, input schema and annotations exactly as the server listed them the last time it answered us; no code was reviewed. We ask the server again about once a month, and a list that changed is graded again.
The implementation source was not read — this reflects the declared tool metadata only.
Capability — what it could do if the model were manipulated
Tags derived from each tool’s schema and the implementation, not from what the tool calls itself. minimal is the level these add up to.
| Tool | Capability tags | Why the tag was assigned |
|---|---|---|
| search_sales | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| get_sale | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| search_items | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| get_item | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| list_cities | untrusted-input | untrusted-input: keyword "browse", declares openWorldHint: true (interacts with entities outside the server) |
| list_sale_types | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| list_categories | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| get_trending_sales | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| get_sales_starting_soon | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| find_item_for_sale | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
Toxic-flow graph
The lethal trifecta, checked as a graph rather than as a checklist: untrusted input, a sensitive source and an external sink have to meet before there is a path worth worrying about.
The public result for this release does not print the flow graph, so there is nothing to show here. That is not the same as "no paths were found": what the scan did read is above, under coverage.
Supply chain and provenance
This is the first scan of this surface here, so there is nothing yet to compare it against.
Every result on this tab comes from one deterministic pass over the published package — offline, rule by rule, and auditable line by line above. Same methodology version, same bytes, same score.
Release history
This is an address its publisher runs: which release it serves is theirs to choose, so there is nothing here to pin. The history below is for reading; the current release on file is 2.0.0.
No release note was published with this version.
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Any signed-in account that does not publish FindA.Sale can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.