Is Open Food Facts Mcp down?
Down
Yes, Open Food Facts Mcp is down.
It has not passed a check since we started checking it on 11 Oct 2026. Latest error: initialize failed: {"code":-32603,"message":"Server \"open-food-facts-mcp\" is misconfigured: its endpoint points back at the MCPize gateway (open-food-facts-mcp.mcpize.run), which would loop instead of reaching a real.
Latest check
- Last check
- 39 h ago (27 Oct 2026, 03:13 UTC)
- Response time
- Not measured
- Next check
- In about 41 h
- How often
- About every 3 days over the last 7 days
Uptime
Uptime is the share of checks that passed. We checked it about every 3 days over the last 7 days.
Outages in the last 30 days
No outages in the last 30 days. An outage starts when two checks in a row fail and ends at the next passing check.
Recent checks
| When | Result | HTTP | Time |
|---|---|---|---|
| 27 Oct 2026, 03:13 UTC | initialize failed: {"code":-32603,"message":"Server \"open-food-facts-mcp\" is misconfigured: its endpoint points back at the MCPize gateway (open-food-facts-mcp.mcpize.run), which would loop instead of reaching a real | 200 | 482 ms |
| 23 Oct 2026, 19:18 UTC | initialize failed: {"code":-32603,"message":"Server \"open-food-facts-mcp\" is misconfigured: its endpoint points back at the MCPize gateway (open-food-facts-mcp.mcpize.run), which would loop instead of reaching a real | 200 | 636 ms |
| 20 Oct 2026, 12:15 UTC | initialize failed: {"code":-32603,"message":"Server \"open-food-facts-mcp\" is misconfigured: its endpoint points back at the MCPize gateway (open-food-facts-mcp.mcpize.run), which would loop instead of reaching a real | 200 | 855 ms |
| 19 Oct 2026, 10:39 UTC | initialize failed: {"code":-32603,"message":"Server \"open-food-facts-mcp\" is misconfigured: its endpoint points back at the MCPize gateway (open-food-facts-mcp.mcpize.run), which would loop instead of reaching a real | 200 | 853 ms |
| 18 Oct 2026, 08:11 UTC | initialize failed: {"code":-32603,"message":"Server \"open-food-facts-mcp\" is misconfigured: its endpoint points back at the MCPize gateway (open-food-facts-mcp.mcpize.run), which would loop instead of reaching a real | 200 | 745 ms |
| 17 Oct 2026, 03:57 UTC | initialize failed: {"code":-32603,"message":"Server \"open-food-facts-mcp\" is misconfigured: its endpoint points back at the MCPize gateway (open-food-facts-mcp.mcpize.run), which would loop instead of reaching a real | 200 | 840 ms |
| 16 Oct 2026, 01:59 UTC | initialize failed: {"code":-32603,"message":"Server \"open-food-facts-mcp\" is misconfigured: its endpoint points back at the MCPize gateway (open-food-facts-mcp.mcpize.run), which would loop instead of reaching a real | 200 | 684 ms |
| 14 Oct 2026, 23:16 UTC | initialize failed: {"code":-32603,"message":"Server \"open-food-facts-mcp\" is misconfigured: its endpoint points back at the MCPize gateway (open-food-facts-mcp.mcpize.run), which would loop instead of reaching a real | 200 | 708 ms |
| 13 Oct 2026, 20:29 UTC | initialize failed: {"code":-32603,"message":"Server \"open-food-facts-mcp\" is misconfigured: its endpoint points back at the MCPize gateway (open-food-facts-mcp.mcpize.run), which would loop instead of reaching a real | 200 | 666 ms |
| 12 Oct 2026, 15:42 UTC | initialize failed: {"code":-32603,"message":"Server \"open-food-facts-mcp\" is misconfigured: its endpoint points back at the MCPize gateway (open-food-facts-mcp.mcpize.run), which would loop instead of reaching a real | 200 | 672 ms |
How we check
Up means the MCP handshake and the tool list worked, or the server asked for sign-in or payment.
Checks come from our server, about every 3 days for this listing over the last 7 days. A failure can also mean the service blocks our checks. Two failed checks in a row count as an outage, which ends at the next passing check.
If you think a check is wrong, contact hello@toolvet.app. More on how we check and score.