The same check as an MCP tool over Streamable HTTP
Two read-only tools: check_recall(title, model), and get_recall(recallNumber), which gives one recall's CPSC text. Stateless: each request stands alone. Send JSON-RPC 2.0, with Accept application/json, text/event-stream. It shares the limit of /api/check.
Request Body
application/json
Always "2.0".
The request's number, sent back with its answer.
An MCP method, such as tools/list or tools/call.
The method's arguments, such as a tool's name and its arguments.
Response Body
application/json
application/json
curl -X POST "https://example.com/api/mcp" \ -H "Content-Type: application/json" \ -d '{ "jsonrpc": "2.0", "method": "tools/list" }'{}Not offered. Every answer comes back on its own POST. GET
The server is stateless and opens no event stream, so a GET is refused with 405.
The newest day of recalls in the latest Recall Replay, against the demo shop GET
Read from the latest stored Recall Replay run, so it costs no new check. Only the demo shop is public.