Skip to content

Brilliant Design (hosted) MCP server

design.brilliant/canvasbrilliant.designstreamable-httpv1.0.0Scanned

Design pages, screens and posts on a live, editable Brilliant canvas. No install, no account.

6 tools: 3 can delete or cancel things, 1 change things and 2 only read.

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

Tools listed without sign-in. Remote posture

With Anlyon

3 tools here can delete or cancel 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 Brilliant Design (hosted) MCP server can do

The Brilliant Design (hosted) MCP server is published by brilliant.design, a domain the MCP Registry verified. It has 6 tools. It can delete or cancel things (3 tools: edit_design, remove_background and place_image) and create or change data (1 tool: design). 2 tools only read.

1 tool reads private data (inspect_design); 3 tools bring in text other people can write (remove_background, place_image and inspect_design).

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.

Last scanned Nov 19, 2026, version 1.0.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

Deletes or cancels 3Claude Code: deny
  • edit_designUse this when the user wants to change, restyle or add to a Brilliant design opened in this conversation, such as adding a section or a screen next to it, changing the copy or the …No findings

    Why it is in this group

    • The name "edit_design" says "edit": a word for a change.
    • The server marks it destructive (destructiveHint: true).
    Description, as the server wrote it
    Use this when the user wants to change, restyle or add to a Brilliant design opened in this conversation, such as adding a section or a screen next to it, changing the copy or the colors, or making it darker. It takes the design's seed and Blueprint rows and applies them on that design's canvas: new rows add layers, and a row that leads with an id or #ref the design already has changes that layer. It returns how the rows applied, naming any row that did not apply. Its rows run up to 8,000 characters per call; a call of about 20 rows (about 1,500 characters), such as a page's frame and its first section, lands on the canvas within a few seconds. Rows take literal values (hex colors, numbers); design tokens are not available in this lane.

    Annotations the server declares

    • destructiveHint: true
    • idempotentHint: false
    • openWorldHint: false
    • readOnlyHint: false
    • title: Add rows to a Brilliant design
  • place_imageUse this when the user wants an image (one they attached, or one generated in this conversation) placed into a Brilliant design opened in this conversation: it puts the image on th…Reads text others writeNo 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 destructive (destructiveHint: true).

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    Use this when the user wants an image (one they attached, or one generated in this conversation) placed into a Brilliant design opened in this conversation: it puts the image on the canvas as an editable image layer, or as the fill of a target layer, and answers how it applied. It takes the design's seed and the image as image (the file attached or generated in the conversation), imageUrl (https) or imageBase64 (PNG, JPEG or WebP, up to 25 MB); target names an existing frame or shape by its id or #ref to fill instead.

    Annotations the server declares

    • destructiveHint: true
    • idempotentHint: false
    • openWorldHint: true
    • readOnlyHint: false
    • title: Place an image in a Brilliant design
  • remove_backgroundUse this when the user attaches or links a photo and asks to remove its background, cut out the subject or get a transparent PNG.Reads text others write1 finding

    Why it is in this group

    • The name "remove_background" says "remove": a word for removing or ending something.
    • The server marks it not destructive (destructiveHint: false), but an annotation never lowers a class.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.

    Findings

    • Warn

      The server marks "remove_background" not destructive (destructiveHint: false), and its own name, description or input give the class "destructive".

      Matched text

      annotations: {"readOnlyHint":false,"destructiveHint":false,"idempotentHint":false,"openWorldHint":true}; The name "remove_background" says "remove": a word for removing or ending something.

      What this check looks for
    Description, as the server wrote it
    Use this when the user attaches or links a photo and asks to remove its background, cut out the subject or get a transparent PNG. It returns the user's own photo with the background cut away by a matte, at its original size up to 2,048 pixels on the long edge, every subject pixel unchanged. Do not use to generate a new image. It cuts the subject out of the original photo with a matte. It takes the user's image as image (a file the user attached), imageUrl (https) or imageBase64, and returns the cutout, a share link, and Open in Brilliant.

    Annotations the server declares

    • destructiveHint: false
    • idempotentHint: false
    • openWorldHint: true
    • readOnlyHint: false
    • title: Remove a photo's background
Changes things 1Claude Code: ask
  • designUse this when the user asks to design, mock up, wireframe or lay out a user interface or a page as an editable design: a website, landing or pricing page, an app screen (login, set…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.
    Description, as the server wrote it
    Use this when the user asks to design, mock up, wireframe or lay out a user interface or a page as an editable design: a website, landing or pricing page, an app screen (login, settings, checkout), a dashboard, a slide, a social post, a poster, an invitation, a menu or a business card, or a design to edit or tweak by hand. It opens a new, empty, live Brilliant canvas in the chat; the design is built there as editable layers (frames, text, shapes, icons). Not for generating a photograph or an illustration, for photo edits (use remove_background) or for questions that need no design. Do not use to change a design already open in this conversation. Rows take literal values (hex colors, numbers); design tokens are not available in this lane.

    Annotations the server declares

    • destructiveHint: false
    • idempotentHint: false
    • openWorldHint: false
    • readOnlyHint: false
    • title: Design on a Brilliant canvas
Only reads 2Show 2 read-only tools
  • get_knowledgeUse this when writing Blueprint rows for a Brilliant design: it loads Brilliant's Blueprint and design knowledge pages by key (blueprint/core, blueprint/layout, blueprint/paint, bl…No findings

    Why it is in this group

    • The name "get_knowledge" says "get": a word for reading.
    Description, as the server wrote it
    Use this when writing Blueprint rows for a Brilliant design: it loads Brilliant's Blueprint and design knowledge pages by key (blueprint/core, blueprint/layout, blueprint/paint, blueprint/text, design/foundations). Each key pulls in its prerequisites unless includeDependencies is false; all loads the whole tree page by page within the response budget.

    Annotations the server declares

    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
    • readOnlyHint: true
    • title: Load Brilliant knowledge
  • inspect_designUse this when the user wants to see, check or talk about a Brilliant design opened in this conversation: it returns the element tree as Blueprint rows with ids (the ids rows can ta…Reads private dataReads text others writeNo findings

    Why it is in this group

    • The name "inspect_design" says "inspect": a word for reading.

    What it can reach

    • private-dataThe description's first sentence says "conversation": it reads messages.
    • untrusted-inputThe description's first sentence says "conversation": it reads messages, which other people can write.
    Description, as the server wrote it
    Use this when the user wants to see, check or talk about a Brilliant design opened in this conversation: it returns the element tree as Blueprint rows with ids (the ids rows can target), how each turn of the design ended (complete, halted, stopped at a limit, or still building) and any rows that did not apply. With wait, it holds up to 25 seconds for the design's latest turn to end; a turn still building at that point answers its progress. A design renders once the user has the canvas open in the chat.

    Annotations the server declares

    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
    • readOnlyHint: true
    • title: See a Brilliant design

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 outbound.

Reads private data1
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write3
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 19, 2026, 17:19 UTC, unchanged since Nov 19, 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
4
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
  • HighThe whole server

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

    Matched text

    https://brilliant.design/mcp: tools/list returned 6 tools to an anonymous client, including edit_design (destructive), remove_background (destructive), place_image (destructive), design (write)

    What this check looks for

Findings

Matches of fixed checks, with the text they matched.

1 warn
  • The server marks "remove_background" not destructive (destructiveHint: false), and its own name, description or input give the class "destructive".

    Matched text

    annotations: {"readOnlyHint":false,"destructiveHint":false,"idempotentHint":false,"openWorldHint":true}; The name "remove_background" says "remove": a word for removing or ending something.

    What this check looks for

History

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

No change seen yet. Its tools are rescanned every day, and a remote endpoint is looked at once a week.

Install

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

claude mcp add --transport http canvas https://brilliant.design/mcp
claude mcp add --transport http canvas https://brilliant.design/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__canvas__get_knowledge",
      "mcp__canvas__inspect_design"
    ],
    "ask": [
      "mcp__canvas__design"
    ],
    "deny": [
      "mcp__canvas__edit_design",
      "mcp__canvas__remove_background",
      "mcp__canvas__place_image"
    ]
  }
}

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 canvas. Review it before you use it.

Capability tags behind 3 rules
  • mcp__canvas__remove_background untrusted-input
  • mcp__canvas__place_image untrusted-input
  • mcp__canvas__inspect_design private-data, untrusted-input

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/design.brilliant/canvas/verify?hash=15eb47d08efdf4d9291bb90b0448c02bec57939769824bdf1e6a97d233d01e0d" | jq -e '.changed == false'

Pinned hash 15eb47d08efd, from Nov 19, 2026, 10:18 UTC.

Watch

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

https://radar.anlyon.com/servers/design.brilliant/canvas/changes.xml

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

Badge

Anlyon Radar badge for design.brilliant/canvas
[![Anlyon Radar](https://radar.anlyon.com/badge/design.brilliant/canvas.svg)](https://radar.anlyon.com/servers/design.brilliant/canvas)

Source: MCP Registry. Synced Nov 19, 2026, 10:17 UTC.

Brilliant Design (hosted) MCP server: questions and answers

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

Is the Brilliant Design (hosted) MCP server safe?

No scan can promise that. What its definitions show: 6 tools, 4 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 Brilliant Design (hosted) MCP server delete data?

Yes. 3 tools can delete, cancel or revoke something: edit_design, remove_background and place_image.

Can the Brilliant Design (hosted) 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 Brilliant Design (hosted) MCP server have?

6 tools: 3 destructive, 1 write, 2 read. edit_design, remove_background, place_image, design, get_knowledge and inspect_design.

Does the Brilliant Design (hosted) MCP server need sign-in or OAuth?

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

Does the Brilliant Design (hosted) MCP server send data to outside services?

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

Has the Brilliant Design (hosted) MCP server changed its tools?

Not since Anlyon Radar started tracking it. Last scanned Nov 19, 2026.