FakeOut Kitchen Recipe Intelligence

io.github.PhotoRomanoPublished by GitHub account PhotoRomanov1.0.0Updated Oct 24, 2026

470+ clean-eating copycat restaurant recipes with dietary filtering and ingredient substitutions.

VerifiedStreamable HTTPWeb executableLocation & Lifestyle

Overview

AI-generated overview

A remote MCP server giving assistants access to a collection of 470+ clean-eating copycat restaurant recipes with dietary filtering and ingredient substitutions

What you can do
Look up copycat restaurant recipes from a catalog of more than 470 clean-eating versions, with dietary filtering and ingredient substitutions. The manifest lists no individual tools, so the exact operations are not documented; the description points to recipe search and adaptation rather than cooking or shopping actions.
When to use it
Useful when someone wants lighter or diet-adjusted versions of restaurant dishes and wants an assistant to find suitable recipes or suggest substitutions that fit dietary needs.
Requirements
A remote endpoint at mcp-recipe.fakeoutkitchen.com over streamable HTTP, with no local package. A required API key sent in the X-API-Key header; the manifest says to request one by email.
Before you install
Access requires an API key in the X-API-Key header, and the manifest says to request it by email, so a personal email address is shared with the provider. Recipe queries go to a third-party service. No tools are listed, so what the server can read or change is unverified.

Installation

In SourceWeft

  1. Open FakeOut Kitchen Recipe Intelligence in the dashboard and add it to a workspace.
  2. Connect X-API-Key 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/io.github.PhotoRomano%2Fmcp-recipe/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.

{
  "mcpServers": {
    "fakeout-kitchen-recipe-intelligence": {
      "type": "http",
      "url": "https://mcp-recipe.fakeoutkitchen.com/mcp",
      "headers": {
        "X-API-Key": "<YOUR_API_KEY>"
      }
    }
  }
}

Tools

0
This server asks for a credential such as an API key, so SourceWeft could not read its tools without one and has not indexed them.

Version history

1
  1. v1.0.0LatestSep 16, 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.