Fazy Deals MCP
Read-only MCP server exposing Fazy's price-checked deals catalog for US shoppers. Every deal carries a verified discount percentage, current price, reference price, and merchant info. Tools: search_deals, get_deal, get_price_history, similar_deals, list_categories, catalog_slice, post_brief. Free to use, no authentication. MCP endpoint: https://fazy.com/mcp
Hosted MCP Server
npx add-mcp 'https://fazy.com/mcp'Installs into Claude Code, Codex, Cursor and more
Documentation
For developers and AI agents: a price-checked deals catalogue for US shoppers, searchable in one request. Free, no key, nothing to install, 60 requests a minute per address. Every result carries the current price, the retailer’s reference price, a verified discount, and a link that takes the shopper to the retailer.
1 · Search
curl "https://fazy.com/api/v1/deals/search?q=standing+desk&max_price=300" \
-H "X-Fazy-Agent: my-agent"
Parameters: q (required), brand, max_price (dollars), limit (≤ 50), cursor. The answer is { object: "list", data: [deal…], has_more, next_cursor, total }.
Narrow a search with type (a product type), min_price and in_stock=true. Without search words, /api/v1/deals?category=home (or brand, type, a price band) returns a slice of up to 24; every category, brand, guide and product page names its own in a <link rel="alternate" type="application/json">.
2 · One deal, its price history, and similar deals
curl "https://fazy.com/api/v1/deals/9a1e0d3c-0000-4000-8000-000000000000" \
-H "X-Fazy-Agent: my-agent"
curl "https://fazy.com/api/v1/deals/9a1e0d3c-0000-4000-8000-000000000000/price-history"
The history answers “is this a good price?” from Fazy’s own price record: the lowest price recorded, the previous price, and dated facts such as “Down $40 from $199 on 3 Sep 2026”. No fact is given for a price read more than a day ago. /similar returns deals like it.
3 · MCP
Streamable HTTP, read-only, seven tools: search_deals, get_deal, get_price_history, similar_deals, list_categories, catalog_slice (a filtered slice with price-record reliability, for writing about products) and post_brief (the day’s creative brief and house rules). Your client’s own name (clientInfo.name) attributes its clicks; X-Fazy-Agent overrides it. Add it to Cursor or any MCP client:
{
"mcpServers": {
"fazy": { "url": "https://fazy.com/mcp", "headers": { "X-Fazy-Agent": "my-agent" } }
}
}
In VS Code, .vscode/mcp.json:
{
"servers": {
"fazy": { "type": "http", "url": "https://fazy.com/mcp" }
}
}
Nothing to install. Fazy’s MCP server is hosted at https://fazy.com/mcp; every client connects to that URL. Fazy publishes no npm, PyPI or other package, so a package that claims to be Fazy’s MCP server is not ours.
curl -X POST https://fazy.com/mcp -H "content-type: application/json" \
-H "X-Fazy-Agent: my-agent" \
-d '{"jsonrpc":"2.0","id":1,"method":"tools/call","params":{"name":"search_deals","arguments":{"q":"nike running shoes","limit":5}}}'
Use Fazy in Muse
Paste this one message into Meta Muse. It builds the integration, tests it and keeps it:
Build a custom integration for Fazy's deal catalogue. MCP URL: https://fazy.com/mcp. No login needed. Test every tool and save it as a skill.
Use Fazy in ChatGPT
- Settings → Apps & Connectors → Advanced settings: turn on Developer mode.
- Create a connector. Name:
Fazy. MCP server URL:https://fazy.com/mcp. Authentication: none. - In a chat, add Fazy from the + menu and ask for a deal.
Use Fazy in Claude
- Settings → Connectors → Add custom connector.
- Name:
Fazy. Remote MCP server URL:https://fazy.com/mcp. No sign-in is needed. - In a chat, turn Fazy on from the tools menu and ask for a deal.
The one rule
Give the shopper the url field unchanged. It redirects to the retailer’s product page and attributes the click to the name you sent in X-Fazy-Agent. Do not rewrite it, do not link the retailer directly, do not cache it longer than an hour: prices move and dead deals are retired.
Reference
- OpenAPI 3.1 document — import it as a GPT Action or into any agent framework
- llms.txt
- How deals are verified
- Terms · Privacy
API version 2026-09-12. Field names are a contract; a change is a new version, never an edit.