Zaps
REMOTE · API.ZAPS.DESIGN
Photos and a brief in, finished social-media designs out. First design free, no account.
Available components
Last scanned (1 hour ago)
Scores higher than 82% of remote servers
Reachable. Last reached 24 Oct 2026.
Category Design and Media
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. How we score → Why this is hard to score →
Endpoint Security74
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability78
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (excellent).Pass
- 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. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management53
- Stability observed for 16 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
- Supports UI / widget rendering.Pass
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 23 Oct 26 +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.
- 21 Oct 26 +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.
- 19 Oct 26 +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.
- 17 Oct 26 +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.
- 15 Oct 26 +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.
- 14 Oct 26 0
- Resource “zaps-designs” now points somewhere else: ui://widget/zaps-designs-v1.html → ui://widget/zaps-designs-v6.html security
- 13 Oct 26 +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.
- 10 Oct 26 73
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 24 Oct 2026 · Probed https://api.zaps.design/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=api.zaps.design | CN=YE2,O=Let's Encrypt,C=US | 14 Sept 2026 | 13 Dec 2026 | ECDSA 256 | ECDSA-SHA384 | 56a94ce1fe6dab962738836e51ae64d3837 |
| SANs: api.zaps.design | ||||||
| CN=YE2,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 4df3b15dd6c0784c507cd37b58e6f115 |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of api.zaps.design. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| design. | present | 44378 | 13 | Verified |
| zaps.design. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://api.zaps.design/mcp | Verified | 200 | |
| http (plaintext) | http://api.zaps.design/mcp | HTTPS enforced | 308 | https://api.zaps.design/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
create_designs Turn your photos into finished designs ~396
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.
| Name | Type | Req | Description |
|---|---|---|---|
| brief | string | yes | 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… |
| Name | Type | Req | Description |
|---|---|---|---|
| entitlement | string | – | – |
| matchedBy | string | – | – |
| note | string | – | – |
| options | array | yes | – |
| remaining | integer | – | – |
| requested | integer | – | – |
| upsell | string | – | – |
No examples provided.
fill_template Render a template with your photos ~147
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.
| Name | Type | Req | Description |
|---|---|---|---|
| coverId | string | yes | 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. |
| Name | Type | Req | Description |
|---|---|---|---|
| entitlement | string | – | – |
| matchedBy | string | – | – |
| note | string | – | – |
| options | array | yes | – |
| remaining | integer | – | – |
| requested | integer | – | – |
| upsell | string | – | – |
No examples provided.
search_templates Search Zaps templates ~193
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.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | How many templates to return. Default 5. |
| query | string | yes | 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. |
| Name | Type | Req | Description |
|---|---|---|---|
| templates | array | yes | – |
No examples provided.
upload_images Get upload links for local photos ~186
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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. |
| Name | Type | Req | Description |
|---|---|---|---|
| howTo | string | yes | – |
| imageUrls | array | – | – |
| slots | array | – | – |
No examples provided.
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.
remote · api.zaps.design
claude mcp add --transport http design-zaps-zaps 'https://api.zaps.design/mcp'
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.