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

directors-lookbook

https://lookbook-mcp.riverroadlabs.workers.dev

Registry code: 2531668541fb51e2

api record

Director's Lookbook: 649 named styles (cards) for creative prompts, in six suits: type (typefaces), camera (shots, moves, lenses, lighting), film (looks and mediums), color (palettes and grades), score (music styles for Suno), web (site motion). Read-only, no account.

Typical flow: deal_hand(feeling, job) picks one card per slot by keyword and lists options per slot; you are the director: check each card against the scene and swap in a better option before briefing. brief(hand_ids, job, subject, tool, aspect, seconds) turns those ids into paste-ready prompt blocks; lint_hand checks a hand you…

endpoint
https://lookbook-mcp.riverroadlabs.workers.dev/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 directors-lookbook live?
Yes — it answered the hub's last check (checked 2h ago). It answered 100% of checks over the last 30 days.
Is directors-lookbook free to use?
Yes — the hub reached it with no key and no payment.
What tools does directors-lookbook have?
6 tools: show_card, find_styles, lint_hand, brief, list_suits, deal_hand.
Is directors-lookbook 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
94ms

last good check

priced tools
0

of 6 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 6 tools
2 open 4 never probed 2 of 6 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_suits open 2h ago

    Card counts per suit and per kind (for example camera: shot, move, lens, light). Use it to see what the lookbook covers before searching.

    mcp-tool

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

    Start here for a project: deal one matched card per slot for a creative job from a plain-language feeling. photo = one image (film, camera, color, light); still = image with title type; cover = album or poster art (film, color, type); video or reel = clip or short (film, camera, color, type, score, light); lyric = lyric video (same as reel); song = music only (score); site = website (film, color, type, web); game = key art, store capsule, sprites, UI and loop music (film, color, type, score); drama = a short drama ad where the ad is the show (film, camera, color, type, score, light, and three shots: hook, twist, payoff); all = every suit. Example: {"feeling": "lonely astronaut on a desert planet at dusk", "job": "video", "shots": 3}. Same seed + same inputs = same hand; a new seed re-deals; hold keeps chosen cards ({"film": "film-gold-200"}). For job drama the hand also carries three shots (hook close-up, twist reveal, payoff wide or push) and the look is dealt from the feeling, with the subject read as the product. Returns the hand (slot to card id and name), why each card was picked, clashes, and a site_url showing the hand with pictures. Next step: brief with the hand ids.

    mcp-tool

    {
  "type": "object",
  "properties": {
    "job": {
      "enum": [
        "photo",
        "still",
        "cover",
        "video",
        "reel",
        "lyric",
        "song",
        "site",
        "game",
        "drama",
        "all"
      ],
      "type": "string",
      "default": "photo",
      "description": "What the hand is for (default photo); see the job list above."
    },
    "hold": {
      "type": "object",
      "description": "Optional cards to keep, as {slot: card id}, e.g. {\"film\": \"film-gold-200\", \"score\": \"score-bossa-nova\"}. Slots: type, camera, film, color, score, web, light.",
      "maxProperties": 7,
      "propertyNames": {
        "enum": [
          "type",
          "camera",
          "film",
          "color",
          "score",
          "web",
          "light"
        ]
      },
      "additionalProperties": {
        "type": "string",
        "maxLength": 80
      }
    },
    "seed": {
      "type": "integer",
      "maximum": 9007199254740991,
      "minimum": 0,
      "description": "Optional integer for a repeatable deal. Omit for a fresh random deal."
    },
    "moods": {
      "type": "array",
      "items": {
        "enum": [
          "cozy",
          "eerie",
          "nostalgic",
          "epic",
          "playful",
          "tense",
          "dreamy",
          "gritty",
          "elegant",
          "kinetic",
          "melancholy",
          "hopeful",
          "futuristic",
          "handmade",
          "serene",
          "bold"
        ],
        "type": "string"
      },
      "maxItems": 12,
      "description": "Optional mood chips that weigh more than words. One or more of: cozy, eerie, nostalgic, epic, playful, tense, dreamy, gritty, elegant, kinetic, melancholy, hopeful, futuristic, handmade, serene, bold."
    },
    "shots": {
      "type": "integer",
      "maximum": 6,
      "minimum": 2,
      "description": "Optional, for video, reel, lyric or all: also pick a shot list of this many camera cards (the dealt camera first, then matched shots and moves). Pass them all to brief to get one SHOT block each. A drama hand always has 3 (hook, twist, payoff)."
    },
    "aspect": {
      "type": "string",
      "pattern": "^\\d+(\\.\\d+)?:\\d+(\\.\\d+)?$",
      "maxLength": 12,
      "description": "Optional frame for the clash check, e.g. \"2.39:1\" for a film or \"9:16\" for a reel (default 9:16 for reel and lyric). Pass the same aspect to brief."
    },
    "feeling": {
      "type": "string",
      "maxLength": 300,
      "description": "The feeling or scene in plain words, e.g. \"rainy cafe at night, melancholy\". Words after \"no\"/\"not\" count against a card. For drama, the story's feeling or situation, e.g. \"a quiet breakup at a dinner table\"."
    },
    "subject": {
      "type": "string",
      "maxLength": 300,
      "description": "Optional subject, e.g. \"a jazz singer\". It is folded into the feeling so scene and person words count. For drama, the product being advertised (used for the setting check, not for picking the look)."
    }
  },
  "additionalProperties": false
}
    arguments 98 lines
  • show_card unknown never probed

    One card in full: what it is, the prompt wording ("ask"), what not to do, feels, moods, pairs, swatch hexes or font details, plus image, clip and music_sample URLs when it has them. Example: {"id": "film-gold-200"}. A wrong id returns did-you-mean suggestions.

    mcp-tool

    {
  "type": "object",
  "required": [
    "id"
  ],
  "properties": {
    "id": {
      "type": "string",
      "maxLength": 80,
      "description": "Card id from find_styles or deal_hand, e.g. \"film-gold-200\", \"camera-dutch\", \"score-bossa-nova\"."
    }
  },
  "additionalProperties": false
}
    arguments 14 lines
  • find_styles unknown never probed

    Search the 649 cards by feeling, mood, era, technique or style name. Use it to identify a named look ("Kodak Gold" finds Gold 200), to find a replacement for one card in a hand, or to browse one suit. Examples: {"query": "film noir"}, {"query": "90s camcorder"}, {"query": "cozy rainy", "suit": "color"}, {"query": "bossa nova", "suit": "score", "top": 3}. Returns ranked cards (id, suit, kind, name, what, example image). When nothing matches directly it says so and returns related styles or did-you-mean suggestions. For a full matched set of cards for a project use deal_hand instead.

    mcp-tool

    {
  "type": "object",
  "required": [
    "query"
  ],
  "properties": {
    "top": {
      "type": "integer",
      "default": 8,
      "maximum": 50,
      "minimum": 1,
      "description": "How many results (1 to 50, default 8)."
    },
    "suit": {
      "enum": [
        "type",
        "camera",
        "film",
        "color",
        "score",
        "web"
      ],
      "type": "string",
      "description": "Optional filter. type = typefaces, camera = shots, moves, lenses and lighting, film = looks and mediums, color = palettes and grades, score = music styles, web = site motion and layout."
    },
    "query": {
      "type": "string",
      "maxLength": 300,
      "minLength": 1,
      "description": "A feeling, mood, era, technique or style name, e.g. \"dreamy 70s summer\", \"anamorphic\", \"risograph\", \"lo-fi beats\". Words after \"no\"/\"not\" count against a card."
    }
  },
  "additionalProperties": false
}
    arguments 34 lines
  • lint_hand unknown never probed

    Check card ids you combined yourself for clashes before briefing: black-and-white film with a colour grade, two grades stacked, daylight with a night palette, an anamorphic lens in a vertical frame, an interior light with an outdoor subject. Example: {"hand_ids": ["film-pushed-bw-1600", "color-teal-orange"], "aspect": "9:16"}. ok: true means clean. deal_hand and brief already lint their own output.

    mcp-tool

    {
  "type": "object",
  "required": [
    "hand_ids"
  ],
  "properties": {
    "aspect": {
      "type": "string",
      "pattern": "^\\d+(\\.\\d+)?:\\d+(\\.\\d+)?$",
      "maxLength": 12,
      "description": "Optional frame, e.g. \"9:16\"."
    },
    "subject": {
      "type": "string",
      "maxLength": 300,
      "description": "Optional subject; enables the light-vs-setting check."
    },
    "hand_ids": {
      "type": "array",
      "items": {
        "type": "string",
        "maxLength": 80
      },
      "maxItems": 12,
      "minItems": 1,
      "description": "Card ids to check."
    }
  },
  "additionalProperties": false
}
    arguments 30 lines
  • brief unknown 2h ago

    Turn card ids into paste-ready prompt blocks, worded verbatim from the cards: IMAGE PROMPT, VIDEO PROMPT, PALETTE (hexes), TYPE, SUNO STYLE and SUNO EXCLUDE, SITE PROMPT, or for job game: KEY ART, CAPSULE, SPRITE/TILESET, UI MOCKUP, MUSIC; for job drama: SHOT blocks for the hook, twist and payoff plus BEATS (timing, shot, what happens, a placeholder line with its length rule), END CARD (title, promise, call to action, set in the type card), CAPTION RULES (safe band y 210 to 1345 on 1080x1920, nothing in the bottom 30%) and DON'T. Pass the ids from deal_hand (or find_styles), at most one card per suit, except camera: several camera cards make a shot list (one SHOT block each). A camera card of kind light lights every shot; a film card of kind fx adds a post effect. tool respells the blocks: midjourney (--ar, --style raw, --sref with the film card's example image), runway or kling (camera line first, 5 or 10 s clips), suno (music blocks only). seconds splits a running time over the shots, beats says what happens in each, vocals picks lyrics or instrumental. A lens card in a shot list shapes every shot. Example: {"hand_ids": ["film-gold-200", "camera-closeup", "color-golden-hour"], "job": "photo", "subject": "an older woman teaching a young man to dance", "tool": "midjourney"}. Drama example: {"hand_ids": ["type-futura", "film-vision3-500t", "color-blue-hour", "camera-closeup", "camera-pull", "camera-push"], "job": "drama", "subject": "a meal-kit app", "feeling": "a quiet breakup at a dinner table", "title": "Dinner for Two", "seconds": 30}. Also returns the don't-list, tone words, deliverables, lint warnings and a site_url.

    mcp-tool

    {
  "type": "object",
  "required": [
    "hand_ids"
  ],
  "properties": {
    "job": {
      "enum": [
        "photo",
        "still",
        "cover",
        "video",
        "reel",
        "lyric",
        "song",
        "site",
        "game",
        "drama",
        "all"
      ],
      "type": "string",
      "default": "reel",
      "description": "What the brief is for (default reel); use the job you dealt for. photo = a still image, video = reel, song = Suno blocks only, site = SITE PROMPT, game = key art set, drama = short drama ad (beats, end card, caption rules)."
    },
    "tool": {
      "enum": [
        "any",
        "midjourney",
        "runway",
        "kling",
        "suno"
      ],
      "type": "string",
      "default": "any",
      "description": "Target tool: any (plain prose), midjourney, runway or kling (camera line first, shots capped at 10 s), suno (music blocks only)."
    },
    "beats": {
      "type": "array",
      "items": {
        "type": "string",
        "maxLength": 200
      },
      "maxItems": 12,
      "description": "Optional: what happens in each shot, in order, e.g. [\"they sit in silence\", \"she slides a photo across the table\"]. Beat n goes into SHOT n (or the one VIDEO PROMPT)."
    },
    "title": {
      "type": "string",
      "maxLength": 300,
      "description": "Optional title lettering for the image or key art (set in the type card). For drama, the show or brand name on the end card."
    },
    "aspect": {
      "type": "string",
      "pattern": "^\\d+(\\.\\d+)?:\\d+(\\.\\d+)?$",
      "maxLength": 12,
      "description": "Optional aspect ratio, e.g. \"16:9\", \"9:16\", \"4:5\", \"1:1\", \"2.39:1\". Default 9:16 for reel and lyric, 16:9 for game."
    },
    "vocals": {
      "enum": [
        "lyrics",
        "instrumental"
      ],
      "type": "string",
      "description": "Optional for music: \"lyrics\" lifts vocal bans out of SUNO EXCLUDE so a sung track can exist; \"instrumental\" adds them."
    },
    "feeling": {
      "type": "string",
      "maxLength": 300,
      "description": "Drama only: the story's feeling or situation, e.g. \"a quiet breakup at a dinner table\". The hook opens on it and every shot carries it."
    },
    "seconds": {
      "type": "integer",
      "maximum": 600,
      "minimum": 1,
      "description": "Optional running time in seconds, e.g. 15 for a reel or 60 for a short: split across the SHOT blocks (or the one VIDEO PROMPT) as \"Duration: N s.\" Drama: 15 to 60, default 30, timed hook, twist, payoff."
    },
    "subject": {
      "type": "string",
      "maxLength": 300,
      "description": "Who or what is in the shot, e.g. \"a lighthouse keeper on a rocky coast\". Without it the prompts say [your subject]. For drama, the product being advertised."
    },
    "hand_ids": {
      "type": "array",
      "items": {
        "type": "string",
        "maxLength": 80
      },
      "maxItems": 12,
      "minItems": 1,
      "description": "Card ids from deal_hand or find_styles, e.g. [\"film-gold-200\", \"camera-closeup\", \"color-golden-hour\"]. One per suit, except several camera cards = a shot list."
    }
  },
  "additionalProperties": false
}
    arguments 93 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 2531668541fb51e2.

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