Director's Lookbook
REMOTE · LOOKBOOK-MCP.RIVERROADLABS.WORKERS.DEV
670+ named visual and music styles: deal a look for a feeling, get paste-ready AI prompts.
Available components
Last scanned (17 hours ago)
Scores higher than 61% of remote servers
Reachable. Last reached 23 Oct 2026.
Category Design and Media
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security63
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement. View diagnostics → Unverified
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability70
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 2813 tokens (~401/item across 7 items; 6 tools + 1 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management37
- Stability observed for 11 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 6 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 8 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 23 Oct 26 +1
- The server rewrote its instructions, which are the text every model session reads security
- Tool “find_styles” rewrote its description, which is the text the model reads security
- 21 Oct 26 0
- The server rewrote its instructions, which are the text every model session reads security
- Tool “find_styles” rewrote its description, which is the text the model reads security
- 20 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.
- 19 Oct 26 0
- The server rewrote its instructions, which are the text every model session reads security
- Tool “find_styles” rewrote its description, which is the text the model reads security
- 18 Oct 26 +1
- The server rewrote its instructions, which are the text every model session reads security
- Tool “find_styles” rewrote its description, which is the text the model reads security
- 17 Oct 26 0
- The server rewrote its instructions, which are the text every model session reads security
- Tool “find_styles” rewrote its description, which is the text the model reads security
- 16 Oct 26 +1
- The server rewrote its instructions, which are the text every model session reads security
- Tool “deal_hand” rewrote its description, which is the text the model reads security
- Tool “find_styles” rewrote its description, which is the text the model reads security
- Schema quality: 363 → 401 ▼ functional
- Server version: 1.3.0 → 1.4.0 functional
- 15 Oct 26 0
- The server rewrote its instructions, which are the text every model session reads security
- Tool “find_styles” rewrote its description, which is the text the model reads security
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 23 Oct 2026 · Probed https://lookbook-mcp.riverroadlabs.workers.dev/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=riverroadlabs.workers.dev | CN=YE1,O=Let's Encrypt,C=US | 9 Oct 2026 | 7 Jan 2027 | ECDSA 256 | ECDSA-SHA384 | 6f159d3e66e36babd698cf350b739df9ef4 |
| SANs: *.riverroadlabs.workers.dev, riverroadlabs.workers.dev | ||||||
| CN=YE1,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 5ddd70dd31f801c85c186a7a04b80afe |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of lookbook-mcp.riverroadlabs.workers.dev. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| dev. | present | 60074 | 8 | Verified |
| workers.dev. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://lookbook-mcp.riverroadlabs.workers.dev/mcp | Verified | 200 | |
| http (plaintext) | http://lookbook-mcp.riverroadlabs.workers.dev/mcp | Inconclusive | 405 |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
brief Compile a brief ~937
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.
| Name | Type | Req | Description |
|---|---|---|---|
| aspect | string | – | 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. |
| beats | array | – | 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). |
| feeling | string | – | 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. |
| hand_ids | array | yes | 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. |
| job | string | – | 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, e… |
| seconds | integer | – | 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, payo… |
| subject | string | – | 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. |
| title | string | – | 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. |
| tool | string | – | Target tool: any (plain prose), midjourney, runway or kling (camera line first, shots capped at 10 s), suno (music blocks only). |
| vocals | string | – | Optional for music: "lyrics" lifts vocal bans out of SUNO EXCLUDE so a sung track can exist; "instrumental" adds them. |
| Name | Type | Req | Description |
|---|---|---|---|
| aspect | string | – | the frame the blocks use |
| beat_plan | array | – | drama: each beat with its seconds and shot |
| blocks | object | – | block name to paste-ready text |
| end_card_from | integer | – | drama: the second the end card starts |
| error | string | – | Set instead of the fields above when the input was wrong. |
| hand | object | – | – |
| handover | array | – | – |
| ignored | string | – | suits the job does not use |
| job | string | – | the job as asked |
| job_internal | string | – | the deck term when it differs from the job asked (video = reel, photo = still) |
| job_note | string | – | a note for this job |
| lint | array | – | – |
| seconds | integer | – | drama: the running time the beats are timed to |
| shot_order | array | – | the SHOT block names in order |
| site | string | – | – |
| site_url | string | – | opens the hand on directorslookbook.app |
| substitute | string | – | set when a stand-in card covers a genre the library lacks |
| tool | string | – | the tool the blocks are spelled for |
No examples provided.
deal_hand Deal a hand ~775
Start here whenever someone asks for an image, video or music prompt, a photo or film look, or art direction from a description ("a moody product shot of perfume", "rainy cafe at night", "a Suno style for a sad song"): deal one matched card per slot for the job from their 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), the main paste-ready prompt for the job (prompt), why each card was picked, clashes, and a site_url showing the hand with pictures. Show the user the prompt and the site_url; use brief with the hand ids for every block (shot lists, palette, Suno, Midjourney spelling).
| Name | Type | Req | Description |
|---|---|---|---|
| aspect | string | – | 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 | string | – | 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 dinne… |
| hold | object | – | 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. |
| job | string | – | What the hand is for (default photo); see the job list above. |
| moods | array | – | 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. |
| seed | integer | – | Optional integer for a repeatable deal. Omit for a fresh random deal. |
| shots | integer | – | 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 d… |
| subject | string | – | 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). |
| Name | Type | Req | Description |
|---|---|---|---|
| alternatives | object | – | slot to other card ids worth a look |
| error | string | – | Set instead of the fields above when the input was wrong. |
| hand | object | – | slot to card id |
| images | object | – | slot to example image URL |
| job_used | string | – | the job the hand was dealt for |
| lint | array | – | – |
| moods_read | array | – | – |
| names | object | – | slot to card name |
| neg_moods_read | array | – | – |
| note | string | – | why each card was picked |
| prompt | object | – | the main paste-ready prompt for the job, compiled from this hand (brief gives every block) |
| shots | array | – | shot list camera ids when shots was asked |
| site | string | – | – |
| site_url | string | – | opens the hand on directorslookbook.app |
| swapped | array | – | cards swapped to clear a clash |
| warnings | array | – | holds or options that could not be honoured |
| weak | array | – | slots filled on little evidence |
No examples provided.
find_styles Find styles ~335
Search the 756 cards by feeling, mood, era, technique or style name. Use it when someone names or describes a specific look, lens, film stock, light, palette, font or music style ("what does Portra 400 look like", "ring light macro", "Wes Anderson-style symmetry" finds Planimetric Tableau), 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.
| Name | Type | Req | Description |
|---|---|---|---|
| query | string | yes | 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. |
| suit | string | – | 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. |
| top | integer | – | How many results (1 to 50, default 8). |
| Name | Type | Req | Description |
|---|---|---|---|
| count | integer | – | – |
| error | string | – | Set instead of the fields above when the input was wrong. |
| matched | integer | – | – |
| note | string | – | set when nothing matched directly |
| results | array | – | – |
| site | string | – | – |
| suggestions | array | – | did-you-mean cards when nothing matched |
No examples provided.
lint_hand Lint a hand ~148
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.
| Name | Type | Req | Description |
|---|---|---|---|
| aspect | string | – | Optional frame, e.g. "9:16". |
| hand_ids | array | yes | Card ids to check. |
| subject | string | – | Optional subject; enables the light-vs-setting check. |
| Name | Type | Req | Description |
|---|---|---|---|
| error | string | – | Set instead of the fields above when the input was wrong. |
| ok | boolean | – | – |
| problems | array | – | – |
| site | string | – | – |
No examples provided.
list_suits List suits ~41
Card counts per suit and per kind (for example camera: shot, move, lens, light). Use it to see what the lookbook covers before searching.
Input schema present but exposes no named parameters.
Structured output declared, but exposes no named fields.
No examples provided.
show_card Show a card ~115
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.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | Card id from find_styles or deal_hand, e.g. "film-gold-200", "camera-dutch", "score-bossa-nova". |
Structured output declared, but exposes no named fields.
No examples provided.
How do I install the Director's Lookbook MCP server?
Director's Lookbook is a hosted endpoint at https://lookbook-mcp.riverroadlabs.workers.dev/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · lookbook-mcp.riverroadlabs.workers.dev
claude mcp add --transport http qxxx5vyd77-byte-directors-lookbook 'https://lookbook-mcp.riverroadlabs.workers.dev/mcp'
What is the Director's Lookbook MCP server?
Director's Lookbook is an MCP server listed in the public MCP registry as io.github.qxxx5vyd77-byte/directors-lookbook. 670+ named visual and music styles: deal a look for a feeling, get paste-ready AI prompts. This page covers its hosted endpoint (https://lookbook-mcp.riverroadlabs.workers.dev/mcp).
Is the Director's Lookbook MCP server safe to use?
Director's Lookbook scores 71 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the Director's Lookbook MCP server expose?
Director's Lookbook exposes 6 tools: find_styles, deal_hand, brief, show_card, list_suits, lint_hand. Their descriptions and schemas cost roughly 2,351 tokens of context every time the server is loaded.
Does the Director's Lookbook MCP server require authentication?
No. We connected to Director's Lookbook without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Director's Lookbook MCP server still maintained?
Director's Lookbook is still listed as active in the MCP registry. We last reached this channel on 23 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.