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

docker-recipes

https://docker.recipes

Registry code: 68ab04877f4626b8

api record

Docker Recipes is a catalogue of ready-to-use Docker Compose stacks. Use search_recipes to find a recipe, then get_recipe with its slug to get the full docker-compose.yml, .env template, usage notes and troubleshooting.

endpoint
https://docker.recipes/mcp
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 docker-recipes live?
Partly — its last checks failed now and then (checked 2h ago). It answered 33% of checks over the last 30 days.
Is docker-recipes free to use?
Yes — the hub reached it with no key and no payment.
What tools does docker-recipes have?
4 tools: get_recipe, list_recipes, search_recipes, list_categories.
Is docker-recipes 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
degraded
uptime, 30 days
33.3%

90 days 33.3%· all time 33.3%

latency
291ms

last good check

priced tools
0

of 4 tools

_ answered our checks, 90 days 3 checks · signed record
  • live → degraded· HTTP 404: vercel DEPLOYMENT_NOT_FOUND
  • 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 4 tools
1 open 3 never probed 1 of 4 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 33h ago

    List all recipe categories with their slug, name, description and recipe count.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "properties": {}
    }
    arguments 5 lines
  • get_recipe unknown 33h ago

    Get one recipe as Markdown: overview, docker-compose.yml, .env template, prerequisites, usage notes and troubleshooting.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "required": [
        "slug"
      ],
      "properties": {
        "slug": {
          "type": "string",
          "minLength": 1,
          "description": "Recipe slug from search_recipes, e.g. 'postgresql'"
        }
      },
      "additionalProperties": false
    }
    arguments 15 lines
  • list_recipes unknown 33h ago

    List every recipe in one category (slug, title, description, URLs).

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "required": [
        "category"
      ],
      "properties": {
        "category": {
          "enum": [
            "web-servers",
            "databases",
            "full-stacks",
            "cms",
            "monitoring",
            "devops",
            "productivity",
            "media",
            "security",
            "development",
            "ai-ml",
            "ecommerce",
            "messaging",
            "homelab",
            "storage"
          ],
          "type": "string",
          "description": "Category slug from list_categories"
        },
        "difficulty": {
          "enum": [
            "beginner",
            "intermediate",
            "advanced"
          ],
          "type": "string"
        }
      },
      "additionalProperties": false
    }
    arguments 39 lines
  • search_recipes unknown never probed

    Search Docker Compose recipes by keywords (app name, technology, use case). Returns ranked matches with slug, title, description and URLs.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "required": [
        "query"
      ],
      "properties": {
        "limit": {
          "type": "integer",
          "maximum": 50,
          "minimum": 1,
          "description": "Max results (default 10)"
        },
        "query": {
          "type": "string",
          "minLength": 1,
          "description": "Keywords, e.g. 'postgres pgadmin' or 'media server'"
        },
        "category": {
          "enum": [
            "web-servers",
            "databases",
            "full-stacks",
            "cms",
            "monitoring",
            "devops",
            "productivity",
            "media",
            "security",
            "development",
            "ai-ml",
            "ecommerce",
            "messaging",
            "homelab",
            "storage"
          ],
          "type": "string",
          "description": "Limit to one category slug"
        },
        "difficulty": {
          "enum": [
            "beginner",
            "intermediate",
            "advanced"
          ],
          "type": "string"
        }
      },
      "additionalProperties": false
    }
    arguments 50 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 68ab04877f4626b8.

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

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.