# Zaps (remote · api.zaps.design)

Photos and a brief in, finished social-media designs out. First design free, no account.

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

## Components

- remote · `api.zaps.design`: 79/100 (this document), [markdown](https://verifymcp.io/servers/design-zaps-zaps/api.md), [page](https://verifymcp.io/servers/design-zaps-zaps/api)

## Channel facts

- Endpoint: `https://api.zaps.design/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.1.0`

## 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-10-24.

- **Endpoint Security**: 74/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one.
  - 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**: 78/100
  - 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 1135 tokens (~227/item across 5 items; 4 tools + 1 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**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **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 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a current MCP spec version (2026-07-28).
  - Supports UI / widget rendering.

## Install

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

Zaps is a hosted endpoint at https://api.zaps.design/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 design-zaps-zaps 'https://api.zaps.design/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "design-zaps-zaps": {
      "url": "https://api.zaps.design/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "design-zaps-zaps": {
      "type": "http",
      "url": "https://api.zaps.design/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.design-zaps-zaps]
url = "https://api.zaps.design/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "design-zaps-zaps": {
      "type": "remote",
      "url": "https://api.zaps.design/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add design-zaps-zaps --url 'https://api.zaps.design/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  design-zaps-zaps:
    url: "https://api.zaps.design/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "design-zaps-zaps": {
      "Transport": "http",
      "Url": "https://api.zaps.design/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add design-zaps-zaps -t streamable-http -u 'https://api.zaps.design/mcp'
```

### Other

```json
{
  "mcpServers": {
    "design-zaps-zaps": {
      "type": "http",
      "url": "https://api.zaps.design/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-10-23 (score 79, +1)

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

### 2026-10-21 (score 78, +1)

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

### 2026-10-19 (score 77, +1)

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

### 2026-10-17 (score 76, +1)

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

### 2026-10-15 (score 75, +1)

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

### 2026-10-14 (score 74, 0)

- [security] Resource “zaps-designs” now points somewhere else: ui://widget/zaps-designs-v1.html → ui://widget/zaps-designs-v6.html

### 2026-10-13 (score 74, +1)

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

### 2026-10-10 (score 73)

First indexed and scored.

## MCP tools (4)

### `search_templates` (~193 tokens)

Search Zaps templates

Find design templates. YOU write the query, and its wording decides the match: the catalogue describes each template as Title Case phrases separated by commas, and a query in that same register scores about 0.11 higher than the same intent written as a sentence. Write five or six phrases covering the occasion, the subject and the mood — "Coffee Shop, Cafe Vibes, Grand Opening, Latte Art, Cafe Aesthetic" rather than "grand opening of a neighbourhood coffee shop". A single word is worst of all. Returns templates with an id to fill and a link a person can open to keep editing.

Input parameters:

- `limit` (integer): How many templates to return. Default 5.
- `query` (string, required): Title Case phrases separated by commas, the way the catalogue describes itself. Five or six covering occasion, subject and mood.
- `segment` (string): Optional shape filter, e.g. story or carousel.

Output parameters:

- `templates` (array)

### `upload_images` (~186 tokens)

Get upload links for local photos

Call this FIRST when the photos are on the caller's machine rather than already on the web — our renderer fetches over the network and cannot read a local path. Simplest way: read each file and pass it in `files` as base64; the reply gives you a publicUrl per photo to hand straight to create_designs, with nothing else to run. If you would rather upload the bytes yourself, pass `count` instead and you get presigned links to PUT to. Costs nothing either way.

Input parameters:

- `count` (integer): Only when uploading the bytes yourself: how many links to mint.
- `files` (array): The photos themselves, base64 encoded. We store them and hand back a url each. Use this unless you have a reason not to.
- `mimeType` (string): The images' media type, e.g. image/png or image/jpeg.

Output parameters:

- `howTo` (string)
- `imageUrls` (array)
- `slots` (array)

### `create_designs` (~396 tokens)

Turn your photos into finished designs

The whole job in one call: give it a SEARCH QUERY you have written, your photo URLs and the words you want on the design, and it finds templates that fit, renders each with your photos and your copy, and returns several finished designs to choose between. Use this when someone wants options — it is search and render together, so there is no need to call search_templates and fill_template yourself. Templates that hold every photo you supplied are preferred, so pass all of them. Photos attached in the conversation go in `photos`; photos already on the web go in `images`. Each returned design spends one agentic token.

Input parameters:

- `brief` (string, required): The SEARCH QUERY for the template catalogue — you write it, we do not build it from anything else. Title Case phrases separated by commas, the way the catalogue describes itself: "Birthday Party, Fri…
- `count` (integer): How many finished designs to return. Default 5, at most 10.
- `images` (array): Publicly reachable image URLs, in placement order.
- `photos` (array): Photos the person attached in this conversation, in placement order. Use this OR images, not both.
- `segment` (string): Optional shape filter, e.g. story or carousel.
- `text` (array): The words to put ON the designs — headline first, then any supporting lines. WRITE THESE YOURSELF from the brief: a template ships with the designer's placeholder copy, and leaving it means a coffee…

Output parameters:

- `entitlement` (string)
- `matchedBy` (string)
- `note` (string)
- `options` (array)
- `remaining` (integer)
- `requested` (integer)
- `upsell` (string)

### `fill_template` (~147 tokens)

Render a template with your photos

Render a finished image: give it a template id from search_templates and the photo URLs to place, and it returns the rendered design. Photos are placed into the template's image slots in the order given, so pass them in the order you want them to appear. Photos attached in the conversation go in `photos`; photos already on the web go in `images`. Each render spends one agentic token.

Input parameters:

- `coverId` (string, required): Template id, from a search_templates result.
- `images` (array): Publicly reachable image URLs, in placement order.
- `photos` (array): Photos the person attached in this conversation, in placement order. Use this OR images, not both.

Output parameters:

- `entitlement` (string)
- `matchedBy` (string)
- `note` (string)
- `options` (array)
- `remaining` (integer)
- `requested` (integer)
- `upsell` (string)

## Diagnostics

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

## Score history

- 2026-10-24: 79
- 2026-10-23: 79
- 2026-10-22: 78
- 2026-10-21: 78
- 2026-10-20: 77
- 2026-10-19: 77
- 2026-10-18: 76
- 2026-10-17: 76
- 2026-10-16: 75
- 2026-10-15: 75
- 2026-10-14: 74
- 2026-10-13: 74
- 2026-10-12: 73
- 2026-10-10: 73

## Common questions

### What is the Zaps MCP server?

Zaps is an MCP server listed in the public MCP registry as design.zaps/zaps. Photos and a brief in, finished social-media designs out. First design free, no account. This page covers its hosted endpoint (https://api.zaps.design/mcp).

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

Zaps scores 79 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 Zaps MCP server expose?

Zaps exposes 4 tools: search_templates, upload_images, create_designs, fill_template. Their descriptions and schemas cost roughly 922 tokens of context every time the server is loaded.

### Does the Zaps MCP server require authentication?

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

### Is the Zaps MCP server still maintained?

Zaps is still listed as active in the MCP registry. We last reached this channel on 24 October 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://api.zaps.design/mcp
- Repository: https://github.com/turnip-agentic/zaps-agent
- Website: https://zaps.design/
- Changelog RSS feed: https://verifymcp.io/servers/design-zaps-zaps/api.xml
- Changelog JSON feed: https://verifymcp.io/servers/design-zaps-zaps/api.json
- HTML version of this page: https://verifymcp.io/servers/design-zaps-zaps/api