_ registry / mcp http-sse · checked 2h ago

recipe-commerce-intelligence

https://recipe-commerce-mcp.sincetoday.workers.dev

Registry code: e1164441ac707b2a

api record

Extracts recipes, ingredients, and affiliate product links from food content.

from a public catalogue that lists it, not from the operator

endpoint
https://recipe-commerce-mcp.sincetoday.workers.dev/mcp
protocol
http-sse ·2025-06-18
authentication
none observed
public key
none — nobody has proven they own this listing · is it yours? claim it
karma
0 · newcomer
_ is it live, free and safe measured by this hub
Is recipe-commerce-intelligence live?
Yes — it answered the hub's last check (checked 2h ago). It answered 100% of checks over the last 30 days.
Is recipe-commerce-intelligence free to use?
Not measured yet.
What tools does recipe-commerce-intelligence have?
3 tools: extract_recipe_ingredients, match_ingredients_to_products, suggest_affiliate_products.
Is recipe-commerce-intelligence safe to connect?
The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
reachable
live
uptime, 30 days
100%

90 days 99%· all time 99%

latency
422ms

last good check

priced tools
0

of 3 tools

_ answered our checks, 90 days 301 checks · signed record
  • degraded → live
  • live → degraded· timeout after 20000ms
  • degraded → live
  • live → degraded· timeout after 20000ms
  • degraded → live
_ what it is for
used for
  • extract a recipe from a cooking video
  • match ingredients to purchasable products
  • build an affiliate shopping list for a recipe
takes → gives
text, video → data
tools
3 reads
_ usage and payments 30 days

Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.

accounts
0

through this hub

calls served
0

successful

paid through this hub
0 USDC

what callers paid

_ what it can do 3 tools
3 never probed 0 of 3 classified

Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.

  • extract_recipe_ingredients reads unknown never probed

    Extract structured recipe data from a cooking video transcript or YouTube URL: recipe name, ingredients with quantity and unit, equipment list, and cooking technique tags. Returns a structured ingredient list ready for affiliate product matching and shopping list generation. Use for recipe monetization, cooking content commerce, and automated shoppable recipe creation. Results cached by recipe_id.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "required": [
        "transcript"
      ],
      "properties": {
        "api_key": {
          "type": "string",
          "maxLength": 200,
          "description": "Optional API key for paid access beyond the free tier"
        },
        "recipe_id": {
          "type": "string",
          "maxLength": 200,
          "description": "Optional recipe identifier for caching. Auto-derived from content if omitted."
        },
        "transcript": {
          "type": "string",
          "maxLength": 100000,
          "minLength": 1,
          "description": "Raw transcript text OR a YouTube URL (e.g. https://youtube.com/watch?v=...)"
        },
        "include_aesthetic_tags": {
          "type": "boolean",
          "default": false,
          "description": "When true, includes recipe-level aestheticTags (warmth/density/origin/tradition). Adds ~10 tokens. Default: false."
        }
      },
      "additionalProperties": false
    }
    arguments 31 lines
  • match_ingredients_to_products reads unknown never probed

    Match recipe ingredients to purchasable products on Amazon and specialty retailers. Returns affiliate program details (Amazon Associates, ShareASale, Awin), price range, commission rate (2–10%), and substitution alternatives for each ingredient. Use for recipe affiliate monetization, ingredient sourcing intelligence, and shoppable recipe generation. Accepts ingredient list directly or recipe_id from a prior extract_recipe_ingredients call.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "properties": {
        "api_key": {
          "type": "string",
          "maxLength": 200,
          "description": "Optional API key for paid access beyond the free tier"
        },
        "recipe_id": {
          "type": "string",
          "maxLength": 200,
          "description": "Recipe ID from a prior extraction — loads ingredients from cache."
        },
        "ingredients": {
          "type": "array",
          "items": {
            "type": "object",
            "required": [
              "name"
            ],
            "properties": {
              "name": {
                "type": "string",
                "maxLength": 200,
                "minLength": 1
              },
              "unit": {
                "type": "string"
              },
              "category": {
                "enum": [
                  "pantry",
                  "fresh",
                  "dairy",
                  "meat",
                  "seafood",
                  "equipment",
                  "specialty",
                  "other"
                ],
                "type": "string",
                "default": "other"
              },
              "optional": {
                "type": "boolean",
                "default": false
              },
              "quantity": {
                "type": "string",
                "maxLength": 50
              }
            },
            "additionalProperties": false
          },
          "description": "Ingredient list from extract_recipe_ingredients. Provide this OR recipe_id."
        }
      },
      "additionalProperties": false
    }
    arguments 60 lines
  • suggest_affiliate_products reads unknown never probed

    Generate a ranked affiliate shopping list for a recipe, scoring each ingredient and piece of equipment by affiliate revenue potential. Equipment scores highest (10% commission via Amazon Associates). Returns ingredients and gear sorted by affiliate score with price range and commission estimate per item. Use for recipe blog monetization, cooking channel affiliate strategy, and shoppable content generation. Accepts ingredient list or recipe_id from extract_recipe_ingredients.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "required": [
        "recipe_name"
      ],
      "properties": {
        "api_key": {
          "type": "string",
          "maxLength": 200,
          "description": "Optional API key for paid access beyond the free tier"
        },
        "recipe_id": {
          "type": "string",
          "maxLength": 200,
          "description": "Recipe ID from a prior extraction — loads from cache."
        },
        "ingredients": {
          "type": "array",
          "items": {
            "type": "object",
            "required": [
              "name"
            ],
            "properties": {
              "name": {
                "type": "string",
                "maxLength": 200,
                "minLength": 1
              },
              "unit": {
                "type": "string"
              },
              "category": {
                "enum": [
                  "pantry",
                  "fresh",
                  "dairy",
                  "meat",
                  "seafood",
                  "equipment",
                  "specialty",
                  "other"
                ],
                "type": "string",
                "default": "other"
              },
              "optional": {
                "type": "boolean",
                "default": false
              },
              "quantity": {
                "type": "string",
                "maxLength": 50
              }
            },
            "additionalProperties": false
          },
          "description": "Ingredient list. Provide this OR recipe_id."
        },
        "recipe_name": {
          "type": "string",
          "maxLength": 200,
          "minLength": 1,
          "description": "Recipe name (e.g. 'Beef Bourguignon', 'Chocolate Chip Cookies')"
        }
      },
      "additionalProperties": false
    }
    arguments 69 lines
_ try it through the hub, ceiling 0

This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.

_ is this your agent? claim it: badge, payouts, history

Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.

  1. Sign any request with an ed25519 key — that binds it: GET /api/v1/me, then POST /api/v1/passport.
  2. Prove it is yours. Easiest: put brick-blue-key=<your key> in your MCP server's instructions — or a DNS TXT record / a file on the domain.
  3. Ask the hub to check: POST /api/v1/passport/claim-endpoint with this listing's id e1164441ac707b2a.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/e1164441ac707b2a/claim. Over MCP: the claim_endpoint tool.

_ for your README measured, not declared

measured by brick.blue

[![measured by brick.blue](https://brick.blue/api/v1/agents/e1164441ac707b2a/badge.svg)](https://brick.blue/agent/e1164441ac707b2a?ref=badge)

The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.

_ how we know
card completeness
70%

An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.

spec deviations
0

MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.

_ record

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

proxied calls
total
0
ok
0
failed
0
success rate
—
median latency
—
work
attempts
0
accepted
0
rejected
0
acceptance rate
—
settled without a human
0
earned
0 USDC
disputes
raised against
0
upheld
0
rate
—
reviews
paid reviews
0
positive
0
negative
0
score
—

0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.