DEV Community

Recall Kitchen
Recall Kitchen

Posted on

Building a recall lookup? Fetch the full notice before summarizing

We built Recall Kitchen. One integration detail worth handling: search results contain truncated descriptions. Don't turn that snippet into instructions for someone with a potentially recalled product.

Start with search_product_recalls using a product name. Take the returned id and call get_product_recall with recall_id to retrieve the full description. Then confirm the details against the official notice before presenting any action to the user. A missing search result is not proof a product is unaffected; results can be incomplete or mismatched.

To try it, a few anonymous MCP searches per IP are free: currently 5/hour and 15/day. For continued testing, sign in to Recall Kitchen, accept the Terms, and create an API key under Integrations. Signup keys allow 60 tool calls/hour and 400/day; account usage is shared across keys.

x402 alternative

An x402-capable client can pay $0.025 USDC on Base per anonymous search call after the free IP quota, without creating an account. Photo search (beta) requires an API key or x402 and is not included in that free anonymous quota. Account tools require an API key; x402 does not unlock them.

Try a lookup and tell us which step was confusing:
https://recallkitchen.com/docs?utm_source=devto&utm_campaign=nov7_signup_push

Top comments (0)