Recipe Signal

io.github.absharma9796Published by GitHub account absharma9796v1.0.0Updated Oct 24, 2026

Search and compare attributed recipe records through a public read-only remote MCP endpoint.

VerifiedStreamable HTTPWeb executableLocation & Lifestyle

Overview

AI-generated overview

A public, read-only remote MCP endpoint that lets an assistant search and compare attributed recipe records.

What you can do
Search attributed recipe records through a public remote endpoint and compare the results. The manifest lists no individual tools, so the exact search and comparison operations are not documented here. Access is read-only, so the assistant retrieves recipe information rather than creating or changing anything.
When to use it
Useful when an assistant needs to look up recipes or compare recipe records from a public source, for example while answering cooking or meal-planning questions. It is not intended for editing, saving, or managing recipe data.
Requirements
A remote MCP connection to the provider's endpoint over streamable HTTP. No packages, environment variables, headers, or authentication are declared, and no account setup is shown.
Before you install
The endpoint is described as public and read-only, and no credentials are requested. Recipe records are attributed to third parties, so attribution should be preserved when results are reused. No other risks are shown in the available information.

Installation

In SourceWeft

  1. Open Recipe Signal in the dashboard and add it to a workspace.
  2. 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.absharma9796%2Frecipe-signal/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": {
    "recipe-signal": {
      "type": "http",
      "url": "https://recipemcp.com/api/recipes"
    }
  }
}

README

This repository has no README.

Tools

0
SourceWeft has not read this server's tools yet.

Version history

1
  1. v1.0.0LatestSep 16, 2026

Score

60% 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 listedRequired15 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.

  • License10 pts

    Declare a license in the repository or the registry entry.