BackResto Partner API
warningsapi.backresto.com
Read-only HACCP records of a restaurant: deliveries, temperatures, cleaning, traceability.
https://api.backresto.com/mcpWebsiteOAuthlast checked 26 Sep 2026spoke MCP on 1 of 1 check (30 days)initialize in 448 msWill my client connect?
Decided from what the probe found at the endpoint, and from what each client's own documentation says it can complete. Every row carries the day that documentation was read.
✕Claude CodeNot supported
The authorization server advertises no S256 challenge method, which MCP's authorization spec requires — no compliant client has a method in common with it.
Claude Code docs · read on 2026-08-30
✕Claude (claude.ai & Desktop)Not supported
The authorization server advertises no S256 challenge method, which MCP's authorization spec requires — no compliant client has a method in common with it.
Claude (claude.ai & Desktop) docs · read on 2026-08-30
✕ChatGPTNot supported
The authorization server advertises no S256 challenge method, which MCP's authorization spec requires — no compliant client has a method in common with it.
ChatGPT docs · read on 2026-08-30
✕CursorNot supported
The authorization server advertises no S256 challenge method, which MCP's authorization spec requires — no compliant client has a method in common with it.
Cursor docs · read on 2026-08-30
✕VS Code (Copilot)Not supported
The authorization server advertises no S256 challenge method, which MCP's authorization spec requires — no compliant client has a method in common with it.
VS Code (Copilot) docs · read on 2026-08-30
How to authenticate
Checked against the endpoint by our probe on 26 Sep 2026. These are the capabilities the server advertises, not a prediction about any particular client.
| Scheme | OAuth |
|---|---|
| Issuer | https://api.backresto.com |
| Dynamic client registration | ✕Not advertised A client that cannot register itself needs credentials issued out of band before it can begin the flow. |
| Client ID Metadata Document | ✕Not advertised |
| PKCE | ✕None advertised MCP requires S256; a client that implements only that has no method in common with this server. |
| Grant types | client_credentials |
| Scopes | restaurants:read, users:read, areas:read, equipment:read, sensors:read, temperature-records:read, temperature-readings:read, suppliers:read, products:read, preparations:read, cleaning-tasks:read, cleaning-task-records:read, cleaning-task-pictures:read, cooling:read, freezing:read, reheating:read, transport:read, fryer-equipment:read, fryer-checks:read, cooking-equipment:read, cooking-temperature-records:read, surface-analyses:read, traceability-labels:read, drive-files:read, deliveries:read, delivery-images:read |
| Protected-resource metadata | ✓Published (RFC 9728) |
| Anonymous access | Refused — credentials required |
| Documentation | https://developers.backresto.com/en/docs |
What the probe found
A cross-origin preflight came back without Access-Control-Allow-Origin, so the endpoint is reachable from native clients only — code running in a web page is stopped by the browser before a request is ever sent.
Contract history
No contract recorded yet — the server has not answered an anonymous connection.
Run this server? A verified owner can publish snapshots with their own credentials, and the contract history starts here, marked owner-reported.
mcpi-cli publish https://api.backresto.com/mcpGet alerted when this contract changes
Depend on this server? Leave an email. No contract is on record here yet, so alerts can only start once one is published — and alerts are being built; signing up is what tells us to hurry.
Prefer a feed reader? This page's contract changes are also an Atom feed.
Own this server?
Sign in to claim this listing by proving control of its host.
Status badge
Status for a README, from the last probe — cached an hour, so up to seven hours behind the endpoint. Links back to this page.
[](https://mcpi.app/servers/backresto-partner-api)