Skip to content

Sleek MCP server

design.sleek/sleeksleek.designstreamable-httpv1.0.1Scanned

Design your mobile app UI with AI, then have your coding agent build the real app from it.

15 tools: 3 can delete or cancel things, 2 change things and 10 only read.

Tools: 3 delete, 0 irreversible, 2 write, 10 read.
  • Reads private data · 0
  • Reads text others write · 5
  • 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 Sleek MCP server can do

The Sleek MCP server is published by sleek.design, a domain the MCP Registry verified. It has 15 tools. It can delete or cancel things (3 tools: delete_project, design and cancel_design_run) and create or change data (2 tools: create_project and open_sleek). 10 tools only read.

5 tools bring in text other people can write (get_project, list_components, get_component and 2 more).

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 once since Anlyon Radar first saw them.

Last scanned Nov 11, 2026, version 1.0.1.

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.

15 tools

Deletes or cancels 3Claude Code: deny
  • cancel_design_runAsk a design run to stop, for example when the brief was wrong.No findings

    Why it is in this group

    • The name "cancel_design_run" says "cancel": a word for removing or ending something.
    • The server marks it destructive (destructiveHint: true).
    Description, as the server wrote it
    Ask a design run to stop, for example when the brief was wrong. Returns the run as it stands right after the request. A queued run comes back 'failed' with error code 'cancelled' and never starts. A running run comes back still 'running' and stops at its next step. A run cut short settles as 'failed' with error code 'cancelled', or 'execution_failed' if saving its changes failed. It keeps any screens and theme changes it saved, listed in data.result.operations, and uses credits only when that list is not empty. A run that finishes before it stops settles as 'completed'. A run that had already settled comes back unchanged. The project stays locked until the run settles, so poll get_design_run before starting another run. A run that stopped responding settles as 'failed' with error code 'execution_timeout' 15 minutes after creation.

    Annotations the server declares

    • readOnlyHint: false
    • destructiveHint: true
    • idempotentHint: true
    • openWorldHint: false
  • delete_projectPermanently delete a project and all its screens.No findings

    Why it is in this group

    • The name "delete_project" says "delete": a word for removing or ending something.
    • The description says "Permanently delete".
    • The server marks it destructive (destructiveHint: true).
    Description, as the server wrote it
    Permanently delete a project and all its screens. Designs cannot be recovered. Call only after your user confirms the exact project by name. Never delete projects to tidy up on your own initiative.

    Annotations the server declares

    • readOnlyHint: false
    • destructiveHint: true
    • idempotentHint: true
    • openWorldHint: false
  • designRun Sleek's design agent to create or edit screens from a plain-language brief.Reads text others writeNo findings

    Why it is in this group

    • The description's first verb is "run": a word for a change.
    • 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
    Run Sleek's design agent to create or edit screens from a plain-language brief. Send the whole request as ONE message, such as 'a food delivery app with onboarding, restaurants, dish detail, cart, tracking, and profile'. The agent plans the screens together, so separate calls produce mismatched screens. A run uses workspace credits only when it completes or saves changes. By default this waits for the run to finish. If it returns 'queued' or 'running', poll get_design_run. Only one run can be active per project. On CONFLICT, poll get_design_run until the run settles, then retry. cancel_design_run stops it sooner. If a failed run has data.error.url, relay data.error.message to your user with that link. They have to act before you retry. On completion, call show_project with data.runId to show your user what the run made, inline. Use screenshot only where your client cannot show apps. Then share projectUrl with your user.

    Annotations the server declares

    • readOnlyHint: false
    • destructiveHint: true
    • idempotentHint: false
    • openWorldHint: true
Changes things 2Claude Code: ask
  • create_projectCreate an empty project.No findings

    Why it is in this group

    • The name "create_project" says "create": a word for a change.
    Description, as the server wrote it
    Create an empty project. Returns it in data, plus projectUrl. Pass data.id as projectId to design, then call show_project once the run completes. Creating a project is instant and uses no credits. Only design runs do. Share projectUrl so your user can watch and edit the designs.

    Annotations the server declares

    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: false
    • openWorldHint: false
  • open_sleekCalled by ChatGPT's sidebar and Sleek's widget to show the workspace's newest projects, each with a cover.1 finding

    Why it is in this group

    • The name "open_sleek" says "open": 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 "open_sleek" 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 name "open_sleek" says "open": a word for a change.

      What this check looks for
    Description, as the server wrote it
    Called by ChatGPT's sidebar and Sleek's widget to show the workspace's newest projects, each with a cover. To list projects yourself, use list_projects.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
Only reads 10Show 10 read-only tools
  • get_componentFetch a screen's generated HTML.Reads text others writeNo findings

    Why it is in this group

    • The name "get_component" says "get": a word for reading.

    What it can reach

    • untrusted-inputThe description's first sentence says "fetch" and "html": it reads web pages, which anyone can write.
    Description, as the server wrote it
    Fetch a screen's generated HTML. Returns the screen in data, with the HTML at data.versions[].code. versions holds only the version the screen currently shows. Use allVersions for the full history, which can be large. The returned screenId is the value design takes. Use this for a build handoff, not to check whether a design run worked.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • get_design_runPoll a run that design returned as 'queued' or 'running'.No findings

    Why it is in this group

    • The name "get_design_run" says "get": a word for reading.
    Description, as the server wrote it
    Poll a run that design returned as 'queued' or 'running'. Wait a few seconds between polls. On 'completed', data.result.operations lists the saved screens and theme changes. Call show_project with this runId to show your user what the run made, inline. Use screenshot only where your client cannot show apps. Then share projectUrl. On 'failed', relay data.error.message to your user, with data.error.url if present. A failed run, including a cancelled one, keeps what it saved in that same list and uses credits only when the list is not empty. Check it before resending the brief.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • get_projectFetch a project and its projectUrl.Reads text others writeNo findings

    Why it is in this group

    • The name "get_project" says "get": a word for reading.

    What it can reach

    • untrusted-inputThe description's first sentence says "fetch" and "url": it reads web pages, which anyone can write.
    Description, as the server wrote it
    Fetch a project and its projectUrl. Use it to confirm the project exists and share the URL with your user. Use list_components to see its screens.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • get_project_viewCalled by Sleek's screen viewer to load a project's screens, in canvas order, with their images and the viewer's text.No findings

    Why it is in this group

    • The name "get_project_view" says "get": a word for reading.
    Description, as the server wrote it
    Called by Sleek's screen viewer to load a project's screens, in canvas order, with their images and the viewer's text. To read screens yourself, use list_components.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • list_componentsList a project's screen names and active version numbers without generated HTML.Reads text others writeNo findings

    Why it is in this group

    • The name "list_components" says "list": a word for reading.

    What it can reach

    • untrusted-inputThe description's first sentence says "list" and "html": it reads web pages, which anyone can write.
    Description, as the server wrote it
    List a project's screen names and active version numbers without generated HTML. Pass each item's screenId to design. Pass its id as componentId to get_component or in componentIds to screenshot. Use get_component only when you need a screen's code.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • list_projectsList the workspace's projects, newest first.No findings

    Why it is in this group

    • The name "list_projects" says "list": a word for reading.
    Description, as the server wrote it
    List the workspace's projects, newest first. Each project holds one app's screens, theme, and design chat. Check here before create_project to avoid duplicates.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • list_referencesList curated app styles and their preview images.No findings

    Why it is in this group

    • The name "list_references" says "list": a word for reading.
    Description, as the server wrote it
    List curated app styles and their preview images. When your user asks for a look such as Airbnb, brutalist, or dark fintech, pass the closest reference's id as referenceId to design. Without a reference, the agent picks a style.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • screenshotRender up to four project screens side by side as one inline image, for clients that cannot show apps.No findings

    Why it is in this group

    • The name "screenshot" says "screenshot": a word for reading.
    Description, as the server wrote it
    Render up to four project screens side by side as one inline image, for clients that cannot show apps. Where your client can, call show_project instead. Returns the image, PNG unless format asks for WebP, and a one-line text note. Rendering uses no credits. Send projectUrl with the image so your user can open and edit the designs.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • search_mentionsFind the workspace's projects by name for an @ mention, newest first.Reads text others writeNo findings

    Why it is in this group

    • The name "search_mentions" says "search": a word for reading.

    What it can reach

    • untrusted-inputThe name "search_mentions" says "search" and "mention": it reads comments, which other people can write.
    • untrusted-inputThe description's first sentence says "find" and "mention": it reads comments, which other people can write.
    Description, as the server wrote it
    Find the workspace's projects by name for an @ mention, newest first. Each item is a resource link whose name is the projectId and whose uri is the projectUrl. To browse every project, use list_projects.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • show_projectShows your user a project's screens inline, in canvas order.No findings

    Why it is in this group

    • The name "show_project" says "show": a word for reading.
    Description, as the server wrote it
    Shows your user a project's screens inline, in canvas order. They can enlarge a screen, add screens to this chat, and open the project in Sleek. After a design run completes, call it with that runId to show what the run made. Where the client cannot show apps, this returns the screen names only; use screenshot to see the screens. Returns the screen names and ids, the same ones design takes as screenId.

    Annotations the server declares

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

Reads private data0
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write5
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, 18:51 UTC, unchanged since Oct 29, 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
5
Protocol version
2025-06-18
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
https://sleek.design/.well-known/oauth-protected-resource/api/mcp
Authorization servers
https://ggrhecslgdflloszjkwl.supabase.co/auth/v1
Legacy HTTP+SSE transport
no
Dynamic client registration
yes
Client ID metadata documents
no
  • HighThe whole server

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

    Matched text

    https://sleek.design/api/mcp: tools/list returned 15 tools to an anonymous client, including delete_project (destructive), design (destructive), cancel_design_run (destructive), create_project (write), open_sleek (write)

    What this check looks for

Posture changes

  1. Oct 29, 2026
    • Tools that change things, listed without credentials: 4 to 5

Findings

Matches of fixed checks, with the text they matched.

1 warn
  • The server marks "open_sleek" 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 name "open_sleek" says "open": a word for a change.

    What this check looks for

History

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

  1. PostureRemote posture changed. Tools that change things, listed without credentials: 4 -> 5.View diff
    • Tools that change things, listed without credentials: 4 to 5
  2. Tools3 added, 4 changed.+3 added~4 changedView diff

Install

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

claude mcp add --transport http sleek https://sleek.design/api/mcp
claude mcp add --transport http sleek https://sleek.design/api/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__sleek__list_projects",
      "mcp__sleek__get_project",
      "mcp__sleek__list_components",
      "mcp__sleek__get_component",
      "mcp__sleek__list_references",
      "mcp__sleek__get_design_run",
      "mcp__sleek__screenshot",
      "mcp__sleek__show_project",
      "mcp__sleek__search_mentions",
      "mcp__sleek__get_project_view"
    ],
    "ask": [
      "mcp__sleek__create_project",
      "mcp__sleek__open_sleek"
    ],
    "deny": [
      "mcp__sleek__delete_project",
      "mcp__sleek__design",
      "mcp__sleek__cancel_design_run"
    ]
  }
}

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

Capability tags behind 5 rules
  • mcp__sleek__get_project untrusted-input
  • mcp__sleek__list_components untrusted-input
  • mcp__sleek__get_component untrusted-input
  • mcp__sleek__design untrusted-input
  • mcp__sleek__search_mentions 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.sleek/sleek/verify?hash=c528400a0204c91c89c785c0f89bb14e4fffd08c287b6a418cd9fb6eefd955b6" | jq -e '.changed == false'

Pinned hash c528400a0204, from Nov 11, 2026, 07:17 UTC.

Watch

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

https://radar.anlyon.com/servers/design.sleek/sleek/changes.xml

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

Badge

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

Source: MCP Registry · repository. Synced Oct 21, 2026, 18:11 UTC.

Sleek MCP server: questions and answers

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

Is the Sleek MCP server safe?

No scan can promise that. What its definitions show: 15 tools, 5 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 Sleek MCP server delete data?

Yes. 3 tools can delete, cancel or revoke something: delete_project, design and cancel_design_run.

Can the Sleek 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 Sleek MCP server have?

15 tools: 3 destructive, 2 write, 10 read. delete_project, design, cancel_design_run, create_project, open_sleek, list_projects, get_project, list_components and 7 more.

Does the Sleek MCP server need sign-in or OAuth?

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

Does the Sleek MCP server send data to outside services?

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

Has the Sleek MCP server changed its tools?

Yes, once since Anlyon Radar started tracking it, most recently on Oct 29, 2026. Every change is on this page and in its Atom feed.