BackResto Partner API

com.backrestoPublished by backresto.comOfficial publisherv0.1.0Updated Oct 24, 2026

Read-only HACCP records of a restaurant: deliveries, temperatures, cleaning, traceability.

VerifiedStreamable HTTPWeb executableBusiness & Commerce

Overview

AI-generated overview

Lets an assistant read a restaurant's HACCP food-safety records, including deliveries, temperatures, cleaning and traceability.

What you can do
BackResto Partner API is a remote MCP server that exposes read-only HACCP records of a restaurant. According to the registry description, it covers deliveries, temperatures, cleaning and traceability. No individual tools are listed in the manifest, so the exact operations are not documented here.
When to use it
Worth adding when an assistant needs to look up a restaurant's food-safety documentation, for example to review delivery, temperature, cleaning or traceability records. It is not intended for writing or changing records.
Requirements
A remote streamable HTTP endpoint at api.backresto.com. It requires an Authorization header carrying a Partner API key in the form Bearer brp_ . ; keys are issued by hand, and a request form is linked from the provider's developer documentation. No packages or environment variables are declared.
Before you install
The Authorization header carries a Partner API key, which is a secret and should be handled as one. The description says the records are read-only, so no writing, sending or deleting of data is indicated. The server is remote, so requests and any data returned pass to the provider's service.

Installation

In SourceWeft

  1. Open BackResto Partner API in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/com.backresto%2Fpartner-api/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "backresto-partner-api": {
      "type": "http",
      "url": "https://api.backresto.com/mcp"
    }
  }
}

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

1
  1. v0.1.0LatestSep 26, 2026

Score

67% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.