# Claycut (remote · claycut.dev)

Custom transparent PNG icons in your project's style, added by your coding agent. Free starter set.

- Trust score: 68/100 (medium)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- remote · `claycut.dev`: 68/100 (this document), [markdown](https://verifymcp.io/servers/vincentzhang15-claycut/claycut.md), [page](https://verifymcp.io/servers/vincentzhang15-claycut/claycut)

## Channel facts

- Endpoint: `https://claycut.dev/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.2.4`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-05.

- **Endpoint Security**: 57/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation not fully verified: no authorisation is required to call this server, and 4 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.
  - HTTPS is enforced; there's no plaintext access path.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 67/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 899 tokens (~224/item across 4 items; 4 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 53/100
  - Stability observed for 16 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 96/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 88% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 60/100
  - Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28.

## Install

### How do I install the Claycut MCP server?

Claycut is a hosted endpoint at https://claycut.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.

### Claude

```bash
claude mcp add --transport http vincentzhang15-claycut 'https://claycut.dev/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "vincentzhang15-claycut": {
      "url": "https://claycut.dev/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "vincentzhang15-claycut": {
      "type": "http",
      "url": "https://claycut.dev/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.vincentzhang15-claycut]
url = "https://claycut.dev/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "vincentzhang15-claycut": {
      "type": "remote",
      "url": "https://claycut.dev/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add vincentzhang15-claycut --url 'https://claycut.dev/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  vincentzhang15-claycut:
    url: "https://claycut.dev/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "vincentzhang15-claycut": {
      "Transport": "http",
      "Url": "https://claycut.dev/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add vincentzhang15-claycut -t streamable-http -u 'https://claycut.dev/mcp'
```

### Other

```json
{
  "mcpServers": {
    "vincentzhang15-claycut": {
      "type": "http",
      "url": "https://claycut.dev/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-03 (score 68, +1)

No change was recorded against any check on this day. Stability & Change Management went from 43 to 47. That category is still filling its 30-day observation window: 13 days of observed history at the previous scan, 14 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-01 (score 67, +1)

No change was recorded against any check on this day. Stability & Change Management went from 37 to 40. That category is still filling its 30-day observation window: 11 days of observed history at the previous scan, 12 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-30 (score 66, +1)

No change was recorded against any check on this day. Stability & Change Management went from 30 to 33. That category is still filling its 30-day observation window: 9 days of observed history at the previous scan, 10 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-28 (score 65, +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.

### 2026-10-26 (score 64, +1)

No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-24 (score 63, +1)

No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-22 (score 62, +1)

No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-21 (score 61, 0)

- [functional improvement] Stability: unverified → 0.03

## MCP tools (4)

### `find_free_icon` (~117 tokens)

Find a free, ready-made transparent PNG icon from the Claycut catalogue. No API key needed. The free set only comes in the clay, editorial and plush house styles, so use it when the project's CLAYCUT.md style is one of those (or the user has no key); otherwise it won't match the project. Returns download URLs for matches, or the full list of available words.

Input parameters:

- `concept` (string, required): The subject, e.g. "wallet", "rocket", "inbox"
- `style` (string)

### `generate_app_icon` (~485 tokens)

Generate a custom transparent PNG app icon or UI illustration of any subject, in the project's own style. Needs a paid Claycut key. Returns a download URL for the finished asset.

Every icon in a project follows one style guide, CLAYCUT.md at the repo root. Before the first call:
1\. If CLAYCUT.md exists, use its style line exactly as written (don't reword it) and skip to step 5.
2\. Otherwise read the project's design system: design docs, Tailwind config, CSS variables and theme tokens, brand colours, fonts, existing icons and illustrations. If there is none, work out what the project is for and who uses it (README, package.json, landing copy, routes) and invent a style that suits it.
3\. Write the style line (at most 300 characters): rendering technique, material, shape language, palette as colour names, lighting, level of detail. It must describe a single solid object that a background remover can cut out: no scenes, no near-white or glassy subjects, no hairline-only line art, no text. Don't mention subject, background or composition; Claycut adds those. Only use a house style (clay, editorial, plush) if it genuinely fits the project, never as a fallback.
4\. Create CLAYCUT.md with: a '## Style line' section holding the exact line, why it fits (palette, material, tone and the files it came from), and an '## Icons' list. Generate one representative icon, show it to the user and adjust the line until they approve it.
5\. Call with style "custom" and style_description set to that line (or the house style name if CLAYCUT.md names one), then add each icon to the '## Icons' list as concept -> file path. Check that list before generating (and find_my_icon for icons this account made in other projects), and reuse one that already exists.

Input parameters:

- `concept` (string, required): The subject, e.g. "wallet", "rocket", "inbox"
- `style` (string): Use "custom" with the style line from CLAYCUT.md; a house style name only if CLAYCUT.md says so.
- `style_description` (string): The exact style line from CLAYCUT.md. Required when style is custom.

### `find_my_icon` (~95 tokens)

Find icons this Claycut account already generated or edited, so you can reuse one instead of paying for a new generation. Needs a Claycut key; free. Check here before generate_app_icon. Returns concept, style, date and download URL for matches, or the account's recent icons if nothing matches.

Input parameters:

- `concept` (string): Word to search past concepts for, e.g. "wallet"; omit to list recent icons

### `edit_app_icon` (~202 tokens)

Change one thing about an icon that is almost right, keeping everything else as it is. Needs a paid Claycut key and costs one icon. Returns a download URL for the edited transparent PNG.

Use it instead of generate_app_icon when the user likes an icon but wants a detail fixed: a new generation redraws the whole object and loses what they liked. Pass the icon's URL (a Claycut asset URL, or any public PNG) and a short instruction. Up to three changes per call; describe the end state to draw ("the grey plate behind the star becomes clear violet crystal"), not what to remove. Name what must not change if it's at risk. Always edit the original, not a previous edit, and add the result to the '## Icons' list in CLAYCUT.md.

Input parameters:

- `image_url` (string, required): Public URL of the PNG to edit
- `instruction` (string, required): What to change, as the end state to draw

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/vincentzhang15-claycut/claycut#diagnostics

## Score history

- 2026-11-05: 68
- 2026-11-04: 68
- 2026-11-03: 68
- 2026-11-02: 67
- 2026-11-01: 67
- 2026-10-31: 66
- 2026-10-30: 66
- 2026-10-29: 65
- 2026-10-28: 65
- 2026-10-27: 64
- 2026-10-26: 64
- 2026-10-25: 63
- 2026-10-24: 63
- 2026-10-23: 62
- 2026-10-22: 62
- 2026-10-21: 61
- 2026-10-20: 61

## Common questions

### What is the Claycut MCP server?

Claycut is an MCP server listed in the public MCP registry as io.github.vincentzhang15/claycut. Custom transparent PNG icons in your project's style, added by your coding agent. Free starter set. This page covers its hosted endpoint (https://claycut.dev/mcp).

### Is the Claycut MCP server safe to use?

Claycut scores 68 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 Claycut MCP server expose?

Claycut exposes 4 tools: find_free_icon, generate_app_icon, find_my_icon, edit_app_icon. Their descriptions and schemas cost roughly 899 tokens of context every time the server is loaded.

### Does the Claycut MCP server require authentication?

No. We connected to Claycut without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the Claycut MCP server still maintained?

Claycut is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://claycut.dev/mcp
- Website: https://claycut.dev/
- Changelog RSS feed: https://verifymcp.io/servers/vincentzhang15-claycut/claycut.xml
- Changelog JSON feed: https://verifymcp.io/servers/vincentzhang15-claycut/claycut.json
- HTML version of this page: https://verifymcp.io/servers/vincentzhang15-claycut/claycut