Skip to content

Director's Lookbook MCP server

io.github.qxxx5vyd77-byte/directors-lookbookqxxx5vyd77-bytestreamable-httpv1.4.0Scanned

790+ named visual and music styles: deal a look for a feeling, get paste-ready AI prompts.

6 tools: 3 change things and 3 only read.

Tools: 0 delete, 0 irreversible, 3 write, 3 read.
  • Reads private data · 0
  • Reads text others write · 0
  • Can send data out · 0
  • 1 finding

Tools listed without sign-in. Remote posture

With Anlyon

3 tools here change things. Govern them.

  • Anlyon lists the tools and adopts none.
  • Each tool you adopt gets approvals and receipts.
  • Your agent never holds the key.
Govern this server →

A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.

What the Director's Lookbook MCP server can do

The Director's Lookbook MCP server is published by the GitHub account qxxx5vyd77-byte. It has 6 tools. It can create or change data (3 tools: deal_hand, brief and lint_hand), but cannot delete data. 3 tools only read.

None of its tools reads private data, brings in text other people write, or sends data out.

The fixed checks matched 1 finding (annotation-conflict). Each one comes with the text it matched.

Its remote endpoint lists its tools without sign-in, and its tools changed 2 times since Anlyon Radar first saw them.

Last scanned Nov 18, 2026, version 1.4.0.

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

6 tools

Changes things 3Claude Code: ask
  • briefTurn 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 jo…No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Compile a brief
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • deal_handStart 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 n…1 finding

    Why it is in this group

    • The description's first verb is "start": a word for a change.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    Findings

    • Warn

      The server marks "deal_hand" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

      Matched text

      annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The description's first verb is "start": a word for a change.

      What this check looks for
    Description, as the server wrote it
    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).

    Annotations the server declares

    • title: Deal a hand
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • lint_handCheck 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…No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Lint a hand
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
Only reads 3Show 3 read-only tools
  • find_stylesSearch the 790 cards by feeling, mood, era, technique or style name.No findings

    Why it is in this group

    • The name "find_styles" says "find": a word for reading.
    Description, as the server wrote it
    Search the 790 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.

    Annotations the server declares

    • title: Find styles
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • list_suitsCard counts per suit and per kind (for example camera: shot, move, lens, light).No findings

    Why it is in this group

    • The name "list_suits" says "list": a word for reading.
    Description, as the server wrote it
    Card counts per suit and per kind (for example camera: shot, move, lens, light). Use it to see what the lookbook covers before searching.

    Annotations the server declares

    • title: List suits
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • show_cardOne 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…No findings

    Why it is in this group

    • The name "show_card" says "show": a word for reading.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Show a card
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or untrusted-input or outbound.

Reads private data0
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write0
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out0
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

Tools listed without sign-in

Looked at Nov 20, 2026, 19:10 UTC, unchanged since Oct 22, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
yes
HTTP status of an anonymous initialize
200
tools/list served without credentials
yes
Tools that change things, listed without credentials
3
Protocol version
2025-06-18
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
not observed
Authorization servers
not observed
Legacy HTTP+SSE transport
no
Dynamic client registration
not observed
Client ID metadata documents
not observed
  • WarnThe whole server

    The endpoint served tools/list without credentials, and the list has 3 tools that change things (3 write). Whether a call also works without credentials was not tested: tools are never called.

    Matched text

    https://lookbook-mcp.riverroadlabs.workers.dev/mcp: tools/list returned 6 tools to an anonymous client, including deal_hand (write), brief (write), lint_hand (write)

    What this check looks for

Findings

Matches of fixed checks, with the text they matched.

1 warn
  • The server marks "deal_hand" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

    Matched text

    annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The description's first verb is "start": a word for a change.

    What this check looks for

History

Changes to its tool definitions and to its remote endpoint, newest first.

  1. Tools1 changed.~1 changedView diff
  2. Tools2 changed.~2 changedView diff
    • Changed:briefChanges thingsinputSchema
    • Changed:find_stylesOnly readsdescription

Install

Pinned to version 1.4.0. Values in angle brackets are yours to fill in.

claude mcp add --transport http directors-lookbook https://lookbook-mcp.riverroadlabs.workers.dev/mcp
claude mcp add --transport http directors-lookbook https://lookbook-mcp.riverroadlabs.workers.dev/mcp

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__directors-lookbook__find_styles",
      "mcp__directors-lookbook__show_card",
      "mcp__directors-lookbook__list_suits"
    ],
    "ask": [
      "mcp__directors-lookbook__deal_hand",
      "mcp__directors-lookbook__brief",
      "mcp__directors-lookbook__lint_hand"
    ],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as directors-lookbook. Review it before you use it.

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://radar.anlyon.com/api/v1/servers/io.github.qxxx5vyd77-byte/directors-lookbook/verify?hash=d0d6179c2284001aabda66557b56b46c33886f65adfcb466fd131b016e2829a7" | jq -e '.changed == false'

Pinned hash d0d6179c2284, from Nov 18, 2026, 02:18 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/io.github.qxxx5vyd77-byte/directors-lookbook/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for io.github.qxxx5vyd77-byte/directors-lookbook
[![Anlyon Radar](https://radar.anlyon.com/badge/io.github.qxxx5vyd77-byte/directors-lookbook.svg)](https://radar.anlyon.com/servers/io.github.qxxx5vyd77-byte/directors-lookbook)

Source: MCP Registry. Synced Nov 18, 2026, 02:18 UTC.

Director's Lookbook MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the Director's Lookbook MCP server safe?

No scan can promise that. What its definitions show: 6 tools, 3 of which can change, send or delete something, and 1 finding from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.

Can the Director's Lookbook MCP server delete data?

No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.

Can the Director's Lookbook MCP server do things that cannot be undone?

No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.

What tools does the Director's Lookbook MCP server have?

6 tools: 3 write, 3 read. deal_hand, brief, lint_hand, find_styles, show_card and list_suits.

Does the Director's Lookbook MCP server need sign-in or OAuth?

Its remote endpoint listed its tools to an anonymous client, without sign-in.

Does the Director's Lookbook MCP server send data to outside services?

None of its tools sends, posts or publishes, or takes a recipient, channel or URL.

Has the Director's Lookbook MCP server changed its tools?

Yes, 2 times since Anlyon Radar started tracking it, most recently on Nov 18, 2026. Every change is on this page and in its Atom feed.