_ registry / mcp streamable-http · checked 1h ago

recipe-for-agents

https://recipeforagents.com

Registry code: 684841a8b84c9e3d

api record

Recipe for Agents answers 'which tool gets my agent this web data, and how do I wire it up?'. It does not run scrapers or return scraped records: it returns the Apify Actor to use, its MCP URL, example input, output fields and price, n8n workflows and setup steps, each with a link to the page on recipeforagents.com. Typical flow: search_tools (or find_recipe for an automation into Sheets/Slack/Notion/HubSpot/email) -> get_tool or get_recipe for the details -> build_mcp_config to add the chosen Actors to the user's MCP client. Running an Actor needs the user's own Apify account (OAuth sign-in…

endpoint
https://recipeforagents.com/mcp-server
protocol
streamable-http ·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-for-agents live?
Yes — it answered the hub's last check (checked 1h ago). It answered 100% of checks over the last 30 days.
Is recipe-for-agents free to use?
Yes — the hub reached it with no key and no payment.
What tools does recipe-for-agents have?
8 tools: build_mcp_config, search_tools, get_tool, find_recipe, get_recipe, troubleshoot, list_categories, list_websites.
Is recipe-for-agents 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 100%· all time 100%

latency
179ms

last good check

priced tools
0

of 8 tools

_ answered our checks, 90 days 1 checks · signed record
  • unknown → live
_ 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 8 tools
2 open 6 never probed 2 of 8 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.

  • list_categories open 1h ago

    The catalogue's categories (leads, social, video, products, property, jobs, search, travel, developer utilities) with Actor counts and the main websites in each.

    mcp-tool

    {
  "type": "object",
  "properties": {},
  "additionalProperties": false
}
    arguments 5 lines
  • list_websites open 1h ago

    Websites the catalogue covers, with the number of Actors for each, its page and one MCP URL bundling its main Actors. Filter by part of the name or by category.

    mcp-tool

    {
  "type": "object",
  "properties": {
    "limit": {
      "type": "integer",
      "default": 50,
      "maximum": 200,
      "minimum": 1
    },
    "query": {
      "type": "string",
      "maxLength": 80,
      "description": "Part of a website name, e.g. 'google'."
    },
    "category": {
      "enum": [
        "leads",
        "social",
        "video",
        "products",
        "property",
        "jobs",
        "search",
        "travel",
        "dev"
      ],
      "type": "string"
    }
  },
  "additionalProperties": false
}
    arguments 31 lines
  • build_mcp_config unknown 1h ago

    Ready-to-paste config that adds chosen Actors (or a website's bundle) to an MCP client through Apify's hosted MCP server: Claude Code, Claude Desktop, Cursor, VS Code, ChatGPT, Codex CLI, Gemini CLI or n8n AI Agent, with steps.

    mcp-tool

    {
  "type": "object",
  "properties": {
    "actors": {
      "type": "array",
      "items": {
        "type": "string"
      },
      "maxItems": 10,
      "description": "Actor ids (owner/name) to include."
    },
    "client": {
      "enum": [
        "all",
        "claude-code",
        "claude-desktop",
        "cursor",
        "vscode",
        "chatgpt",
        "codex",
        "gemini-cli",
        "n8n-agent"
      ],
      "type": "string",
      "default": "all"
    },
    "website": {
      "type": "string",
      "maxLength": 80,
      "description": "Or: a website whose main Actors to bundle, e.g. 'TikTok'."
    },
    "server_name": {
      "type": "string",
      "maxLength": 60,
      "description": "Optional server name in the config."
    }
  },
  "additionalProperties": false
}
    arguments 39 lines
  • search_tools unknown never probed

    Find Apify Actors (ready-made scrapers and data tools) an agent can call for a kind of web data, e.g. 'LinkedIn company headcount', 'Amazon prices', 'Google Maps leads with email'. Returns the best matches with website, price, output fields, required input, page and scoped MCP URL. Filter by website or category.

    mcp-tool

    {
  "type": "object",
  "properties": {
    "limit": {
      "type": "integer",
      "default": 8,
      "maximum": 25,
      "minimum": 1
    },
    "query": {
      "type": "string",
      "maxLength": 200,
      "description": "The data you need, in plain words (website, records, fields)."
    },
    "website": {
      "type": "string",
      "maxLength": 80,
      "description": "Only Actors for this website, e.g. 'LinkedIn', 'Zillow'. Also returns that website's bundled MCP URL."
    },
    "category": {
      "enum": [
        "leads",
        "social",
        "video",
        "products",
        "property",
        "jobs",
        "search",
        "travel",
        "dev"
      ],
      "type": "string",
      "description": "Only this category (keys from list_categories)."
    }
  },
  "additionalProperties": false
}
    arguments 37 lines
  • get_tool unknown never probed

    Everything published about one catalogue Actor: description, price, required and example input, output fields, MCP URL, configs for Claude Code/Cursor/VS Code/Codex, n8n workflow, SKILL.md and schema files, matching recipes.

    mcp-tool

    {
  "type": "object",
  "required": [
    "id"
  ],
  "properties": {
    "id": {
      "type": "string",
      "maxLength": 300,
      "description": "Actor id owner/name (from search_tools), or its recipeforagents.com or Apify Store URL."
    }
  },
  "additionalProperties": false
}
    arguments 14 lines
  • find_recipe unknown never probed

    Find step-by-step n8n recipes that move live web data into a destination (Google Sheets, Slack, Notion, HubSpot, email, Discord, webhook, Qdrant) for a task such as 'new Zillow listings to Slack', plus matching use cases and agent skills. Suggests Actors when no recipe fits.

    mcp-tool

    {
  "type": "object",
  "required": [
    "task"
  ],
  "properties": {
    "task": {
      "type": "string",
      "maxLength": 300,
      "description": "What should happen, e.g. 'daily Google Maps leads into a spreadsheet'."
    },
    "limit": {
      "type": "integer",
      "default": 5,
      "maximum": 10,
      "minimum": 1
    },
    "destination": {
      "type": "string",
      "maxLength": 40,
      "description": "Optional: where the data should go (Google Sheets, Slack, Notion, HubSpot, Email, Discord, Webhook, Qdrant)."
    }
  },
  "additionalProperties": false
}
    arguments 25 lines
  • get_recipe unknown never probed

    One recipe in full: what it does, the Actor and input it sends, schedule, de-duplication, setup steps, known limits and, with include_workflow=true, the importable n8n workflow JSON (built-in nodes only).

    mcp-tool

    {
  "type": "object",
  "required": [
    "slug"
  ],
  "properties": {
    "slug": {
      "type": "string",
      "maxLength": 300,
      "description": "Recipe slug from find_recipe, or the recipe page URL."
    },
    "include_workflow": {
      "type": "boolean",
      "default": false,
      "description": "Include the n8n workflow JSON (several KB)."
    }
  },
  "additionalProperties": false
}
    arguments 19 lines
  • troubleshoot unknown never probed

    Sourced fixes for errors when connecting Apify Actors to Claude, Cursor, VS Code, ChatGPT, Codex, Gemini CLI or n8n (401 unauthorized, 408 timeouts, 429, SSE endpoint gone, tools missing, result too large...).

    mcp-tool

    {
  "type": "object",
  "required": [
    "problem"
  ],
  "properties": {
    "limit": {
      "type": "integer",
      "default": 3,
      "maximum": 6,
      "minimum": 1
    },
    "client": {
      "type": "string",
      "maxLength": 40,
      "description": "Optional: the client, e.g. 'Cursor'."
    },
    "problem": {
      "type": "string",
      "maxLength": 300,
      "description": "The error message or symptom."
    }
  },
  "additionalProperties": false
}
    arguments 25 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 684841a8b84c9e3d.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/684841a8b84c9e3d/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/684841a8b84c9e3d/badge.svg)](https://brick.blue/agent/684841a8b84c9e3d?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
100%

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.