FindA.Sale MCP server
Commit Nov 12, 2026Lets an AI client search for yard sales, garage sales, auctions, flea markets, and specific items for sale.
Also known as deseee/findasale, findasale
- Stars
- 0
- Tools
- —
- Downloads, 30 days
- —
- Latest version
- 2.0.0
- Last commit
- Nov 12, 2026
- License
- —
What is FindA.Sale MCP?
FindA.Sale lets an AI client search for yard sales, garage sales, auctions, flea markets, and specific items for sale.
Summary generated from the project's README
About FindA.Sale MCP server
Locating yard sales, garage sales, flea markets, and specific secondhand items is what this MCP server enables for users interacting with AI clients. It provides a read-only interface to the FindA.Sale platform, allowing an AI to browse various sale types and categories or find trending events. The server functions through a stateless HTTP transport, making it accessible for clients that support the latest Model Context Protocol specifications.
Developers can use ten specific tools to interact with the data, including search_sales, search_items, get_trending_sales, and find_item_for_sale. Because the server operates anonymously, no authentication headers or API keys are required for use. The system prioritizes privacy by withholding street addresses, organizer phone numbers, and exact coordinates, instead providing rounded location data. It includes built-in rate limits of 120 requests per minute per IP to ensure stable performance.
What you can do with it
- 1Discover trending local eventsHave the AI identify which sales are currently popular or gaining traction in the region.
Written from the project's README. Every use case is checked against a quote from it.
How to install FindA.Sale MCP
Formats verified 10 Nov 2026Add to CursorAdd to GooseInstall FindA.Sale MCP in Claude Code
$ claude mcp add --transport http findasale https://mcp.finda.sale/mcpInstall FindA.Sale MCP in Cursor
~/.cursor/mcp.json
{
"mcpServers": {
"findasale": {
"url": "https://mcp.finda.sale/mcp"
}
}
}Install FindA.Sale MCP in VS Code
.vscode/mcp.json
{
"servers": {
"findasale": {
"type": "http",
"url": "https://mcp.finda.sale/mcp"
}
}
}Install FindA.Sale MCP in VS Code CLI
$ code --add-mcp '{"name":"findasale","type":"http","url":"https://mcp.finda.sale/mcp"}'Install FindA.Sale MCP in Codex
$ codex mcp add findasale --url https://mcp.finda.sale/mcpInstall FindA.Sale MCP in Codex config.toml
~/.codex/config.toml
[mcp_servers.findasale] url = "https://mcp.finda.sale/mcp"
Install FindA.Sale MCP in Gemini CLI
$ gemini mcp add -s user --transport http findasale https://mcp.finda.sale/mcpInstall FindA.Sale MCP in Gemini settings.json
~/.gemini/settings.json
{
"mcpServers": {
"findasale": {
"url": "https://mcp.finda.sale/mcp",
"type": "http"
}
}
}Configuration
BACKEND_URL
Automated checks
Ran Nov 15, 2026Full report →Not verified yet. A server needs a score of 80, no serious finding, and enough data for us to check. How checks work · What to fix for more points
- Source repository linked and reachabledeseee/findasale is public and reachablegithub.com/deseee/findasale ↗Pass
- Package names this repository as its sourceNot checked
- Build provenance (Sigstore attestation)Not checked
- Open source license (OSI)No licenseFinding
- Commit or release in the last yearLast commit or release 2026-11-12github.com/deseee/findasale ↗Pass
- OpenSSF ScorecardNot checked
- Package name not close to a popular packageNot checked
- No critical advisory in the package or its dependenciesNot checked
- No hidden instructions to the model0 tool descriptions and the README read; no override phrases, credential paths or hidden charactersPass
- Destructive tools are labelledNot checked
- Remote endpoint answers the MCP handshakeinitialize answered with protocol 2025-06-18 in 410 msPass
README
View on GitHubFindA.Sale MCP Server
Public, read-only Model Context Protocol server for finding sales and items on FindA.Sale.
Built on the official TypeScript MCP SDK v2 (@modelcontextprotocol/server 2.3.x, MCP spec 2026-07-28).
Production: https://mcp.finda.sale (Railway service findasale, project keen-wisdom, root directory packages/mcp-server, Dockerfile.production, auto-deploys on pushes to main that touch packages/mcp-server/**).
Endpoints
| Path | Purpose |
|---|---|
POST /mcp |
Streamable HTTP transport, stateless. Serves 2026-07-28 clients and 2025-era clients (stateless fallback). GET/DELETE answer 405. |
GET /sse + POST /messages?sessionId=… |
Legacy HTTP+SSE transport (deprecated in the spec, kept for existing clients) via @modelcontextprotocol/server-legacy/sse. |
POST /messages (no sessionId) |
Sessionless JSON-RPC shim kept from v1: initialize, ping, tools/list, tools/call. |
GET /mcp/server-card |
MCP Server Card (application/mcp-server-card+json). Alias: /.well-known/mcp/server-card.json. |
GET /.well-known/ai-catalog.json |
AI Catalog linking the Server Card. |
GET /.well-known/mcp.json |
Informal manifest (also mirrored at finda.sale/.well-known/mcp.json). |
GET /health |
Railway health check. |
Tools
All ten tools are read-only (readOnlyHint: true, destructiveHint: false, idempotentHint: true).
Schemas live next to each tool in src/tools/*.ts (zod v4); handlers in src/handlers.ts.
search_sales, get_sale, search_items, get_item, list_cities, list_sale_types,
list_categories, get_trending_sales, get_sales_starting_soon, find_item_for_sale.
Privacy and safety rules
- The backend is always called anonymously (no auth header is ever sent or forwarded), so its public-viewer rules apply: DRAFT/CANCELLED/deleted sales 404, early-access and Legendary items stay embargoed, street addresses are withheld.
- Every response is rebuilt from an allow-list in
src/lib/publicShape.ts. Street address, entrance pin, approach notes, organizer phone/address/user id, payment processor ids and scrape metadata are never returned. Coordinates are rounded to 2 decimals (about 1 km). - Backend errors are mapped to short generic messages.
Rate limits and caching
- Per IP: 120 MCP HTTP requests per minute (
RATE_LIMIT_MAX_REQUESTS), plus per-tool limits (10 to 40 per minute) insrc/lib/rateLimiter.ts. - Legacy SSE: at most 10 open sessions per IP and 300 total; sessions close after 1 hour.
- Backend GET responses are cached in memory (60 s for searches, 10 min for cities/categories, 30 min for sale summaries used by city-filtered item search).
Configuration
See .env.example: BACKEND_URL, PORT (3003), MCP_PUBLIC_ORIGIN, RATE_LIMIT_MAX_REQUESTS, NODE_ENV.
Local run
npm install
npm run build
BACKEND_URL=https://api.finda.sale PORT=3003 npm start
Try it with the MCP Inspector (npx @modelcontextprotocol/inspector) against http://localhost:3003/mcp.
Registry
Official MCP Registry name: sale.finda/findasale (DNS-authenticated namespace for finda.sale).
Submission steps: claude_docs/operations/mcp-registry-submission-2026-10-23.md.
FindA.Sale MCP questions
How do I add FindA.Sale MCP to Claude Code?
Run claude mcp add --transport http findasale https://mcp.finda.sale/mcp in your terminal. Add --scope user to make it available in every project.
How do I add FindA.Sale MCP to Cursor?
Open ~/.cursor/mcp.json and add the server under mcpServers, using the Cursor config shown in the install section above.
Is my personal information or location data shared?
No, the server is read-only and anonymous; street addresses, organizer contact details, and exact coordinates are withheld for privacy.
Are there any rate limits on the server?
Yes, there is a limit of 120 MCP HTTP requests per minute per IP, with additional per-tool limits ranging from 10 to 40 per minute.