Gradients Studio
REMOTE · WWW.GRADIENTS.STUDIO
Gradient backgrounds with real grain, pixel and dither finishes. Free previews, no key needed.
Available components
Last scanned (21 hours ago)
Scores higher than 86% of remote servers
Reachable. Last reached 21 Nov 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 Security83
- 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. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC is configured correctly; the domain's records validate against the full chain to the root. View diagnostics → Pass
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability55
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 1665 tokens (~555/item across 3 items; 3 tools + 0 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 Management100
- No destabilizing schema changes in the last 30 days.Pass
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 3 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 3 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
Checks we ran (13)
- TLS certificate
- Authorization
- HTTPS
- HSTS header
- DNSSEC
- Transport
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Does not apply to this hosted endpoint (2)
- Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
- Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
The score does not measure everything. What the score does not measure →
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.
- 18 Nov 26 0
- Stability: 0.97 → pass security
- 17 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 15 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.
- 13 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.
- 11 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 73 to 77. That category is still filling its 30-day observation window: 22 days of observed history at the previous scan, 23 at this one. The score rises as the window fills, whether or not the server changes.
- 9 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 67 to 70. That category is still filling its 30-day observation window: 20 days of observed history at the previous scan, 21 at this one. The score rises as the window fills, whether or not the server changes.
- 6 Nov 26 +1
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 4 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 50 to 53. That category is still filling its 30-day observation window: 15 days of observed history at the previous scan, 16 at this one. The score rises as the window fills, whether or not the server changes.
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 21 Nov 2026 · Probed https://www.gradients.studio/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=www.gradients.studio | CN=YR1,O=Let's Encrypt,C=US | 21 Oct 2026 | 19 Jan 2027 | RSA 2048 | SHA256-RSA | 50567d15812413bb73281ab556b0954f059 |
| SANs: www.gradients.studio | ||||||
| CN=YR1,O=Let's Encrypt,C=US (CA) | CN=Root YR,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | RSA 2048 | SHA256-RSA | a20253f15f2691c05dc1ce13b9bcca4e |
| CN=Root YR,O=ISRG,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | RSA 4096 | SHA256-RSA | f24b6d17f9d9ad7cb1c9fea78782699f |
Background: What to check on a remote MCP endpoint →
DNSSEC secure
Validation of www.gradients.studio. — Secure
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| studio. | DS published | 35741 | 8 | Verified |
| gradients.studio. | DS published | 54651 | 13 | Verified |
| www.gradients.studio. | Verified address RRset verified with the apex keys |
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 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=63072000 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://www.gradients.studio/mcp | Verified | 200 | |
| http (plaintext) | http://www.gradients.studio/mcp | HTTPS enforced | 308 | https://www.gradients.studio/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 →
list_palettes List palettes and starting points ~93
Palettes to start from: the studio's sixteen, the ones behind product sites people admire (Linear, Stripe, Raycast, …), the account's saved palettes (with an API key), and six tuned starting points for common jobs (website hero, launch post, deck slide, product screenshot, integrations grid, App Store shot) with their full settings. Pass any of these to render_gradient. No key needed.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| aspectRatios | array | yes | – |
| inspiredBy | array | yes | – |
| saved | array | yes | – |
| startingPoints | array | yes | – |
| studio | array | yes | – |
No examples provided.
render_gradient Render a gradient background ~1,386
Render a gradient background image (website hero, OG image, launch post, slide, wallpaper) with Gradients Studio's renderer: blobs, stripes or clouds, real grain, pixel and dither finishes, shape overlays. Workflow: start from suggest_settings or list_palettes, call this WITHOUT `size` for a free 960px preview (returned inline, no API key needed), adjust the `settings` you get back, and pass `size` (exact pixels, e.g. [1200, 630] for an OG image, [2560, 1440] for a hero) once the person is happy. A sized export needs an API key; it uses one of the account's monthly exports (5 free, unlimited on Pro) and returns a URL that is valid for 24 hours; asking for the same export again within that time returns the same URL for free. Every result includes `settings` (send them back to iterate) and `studioUrl` (open it to take over in the browser). Use `overlaySvg` with the raw text of a logo SVG to draw it as concentric outlines over the gradient. For the soft mesh look keep blur at 700–900 and contrast at 130; saturated mid-tone colors render best, muddy ones come out dull.
| Name | Type | Req | Description |
|---|---|---|---|
| aspectRatio | string | – | Frame shape for a preview, e.g. '16:9' hero, '1.91:1' OG image, '4:5' LinkedIn post, '9:16' story. Ignored when size is given. |
| backgroundColor | string | yes | Base color as #RRGGBB. Dark values give the premium look; light ones give pastels. |
| blur | number | – | Softness of the color fields in export pixels, 0–1000. Keep 700–900 for the soft mesh look; below 500 the blobs show hard edges. |
| colors | array | yes | 1–8 gradient colors as #RRGGBB. Three or four is typical. Use saturated mid-tones; muddy or near-grey colors come out dull. |
| contrast | number | – | Contrast 50–200 (%). 100 is flat; 130 is the studio default and what makes colors read. Don't lower it for 'subtle', lower grain instead. |
| coverage | number | – | Clouds only: how much of the frame the clouds fill, 0–2. |
| detail | number | – | Clouds only: fine structure, 0–2. |
| ditherChars | string | – | Dither only: characters to draw instead of the built-in symbols, e.g. '01' or '+-'. Up to 16. |
| ditherGlyphsOnly | boolean | – | Dither only: true draws only the characters over the smooth gradient (no cell quantizing). |
| effect | string | – | Finish over the gradient: 'none', 'pixel' (dot matrix) or 'dither' (palette-quantized cells and glyphs). Pixel and dither preview free and export on Pro. |
| effectOpacity | number | – | 0–1 blend of the finish over the smooth gradient; 1 replaces it, 0.5 shows both. |
| effectSize | number | – | Finish cell size in export pixels, 8–64. 24 default; 40+ reads as deliberate at feed size. |
| effectStrength | number | – | Finish density 0–2 (dot size for pixel, glyph density for dither). |
| fiberDensity | number | – | Stripes only: how many fibers, 0–2 (1 = designed look). |
| format | string | – | Export file format. JPEG is ~8x smaller; grain makes PNGs large. |
| grain | number | – | Film-grain strength 0–0.8. 0.2 is subtle, 0.3+ is visibly textured. Grain also hides banding. |
| overlay | string | – | 'none' or 'shapes' for concentric outlines of one shape radiating from a point. |
| overlayCenter | array | – | Ring origin as [x, y] fractions of the frame, e.g. [0.88, 0.18] for top-right; omit for a seeded point. |
| overlayClip | boolean | – | Clip instead of rings: the whole gradient is drawn inside the overlay shape, on overlayClipBackground |
| overlayClipBackground | string | – | Hex color around a clipped shape (off-white by default) |
| overlayOpacity | number | – | Overlay outline opacity 0–1. 0.15–0.4 stays a texture; higher becomes a graphic. |
| overlayPath | object | – | Set by the server from overlaySvg; do not pass directly. |
| overlayShape | string | – | Overlay shape: circle, square, rounded, squircle, diamond, triangle, hexagon, star, flower, seal, heart, or 'custom' with overlaySvg. |
| overlaySize | number | – | Base shape size in export pixels, 100–3000. |
| overlaySpacing | number | – | Gap between rings in export pixels, 10–200. |
| overlayStroke | number | – | Ring stroke width in export pixels, 1–20. |
| overlaySvg | string | – | Raw text of an SVG (a logo) to draw as concentric outlines; sets overlay to shapes/custom. Up to 64 KB. |
| placement | string | – | Where color points sit: 'center' for a calm middle, 'random' for an off-center composition. |
| saturation | number | – | Saturation 50–200 (%). 100 is neutral; 110–120 keeps the palette alive against grain and dither, which both mute it. |
| seed | integer | – | Composition seed (integer). Reuse it to keep the layout while changing colors or finish; omit for a random one. |
| sheen | number | – | Stripes only: highlight along the fibers, 0–2. 0.2 is the default. |
| size | array | – | Exact export size in pixels [width, height], each 64–3840, e.g. [1200, 630]. Omit for a free 960px preview (no key needed); giving a size needs an API key and uses one monthly export. |
| softness | number | – | Clouds only: edge softness, 0–2. |
| style | string | – | 'blobs' (soft overlapping fields), 'stripes' (flowing silk fibers), 'clouds' (billowing volumes) or 'rays' (soft god rays fanning from above). |
| waviness | number | – | Stripes only: how much the fibers bend, 0–2. |
| Name | Type | Req | Description |
|---|---|---|---|
| aspectRatio | string | yes | – |
| expiresAt | string | – | – |
| exportSize | array | – | – |
| exportUrl | string | – | Download URL of the sized export, valid 24 hours |
| note | string | – | – |
| quota | object | – | – |
| settings | object | yes | The resolved settings; send them back to iterate |
| studioUrl | string | yes | Opens the studio with these settings, for a person to take over |
No examples provided.
suggest_settings Suggest settings from a brief ~186
Turn a plain-language brief ('dark, premium, fintech hero, a bit retro') into two or three starting settings for render_gradient. Understands jobs (hero, launch post, slide, screenshot, integrations, app store), moods and colors, product names (Linear, Stripe, Raycast…), styles (blobs, stripes, clouds) and finishes (retro/pixel, print/dither, terminal/glyph dither, film/grain, smooth). You are the taste layer: preview the candidates and adjust. No key needed.
| Name | Type | Req | Description |
|---|---|---|---|
| aspectRatio | string | – | Frame shape to suggest for; otherwise inferred from the job (hero → 16:9, post → 4:5, …). |
| brief | string | yes | What the background is for and how it should feel, in plain words: job, mood, colors, a product it should resemble, a finish. |
| Name | Type | Req | Description |
|---|---|---|---|
| matched | number | yes | How many of the brief's cues were recognised; 0 means generic fallbacks |
| suggestions | array | yes | – |
No examples provided.
How do I install the Gradients Studio MCP server?
Gradients Studio is a hosted endpoint at https://www.gradients.studio/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 · www.gradients.studio
claude mcp add --transport http studio-gradients-mcp 'https://www.gradients.studio/mcp'
What is the Gradients Studio MCP server?
Gradients Studio is an MCP server listed in the public MCP registry as studio.gradients/mcp. Gradient backgrounds with real grain, pixel and dither finishes. Free previews, no key needed. This page covers its hosted endpoint (https://www.gradients.studio/mcp).
Is the Gradients Studio MCP server safe to use?
Gradients Studio scores 85 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 Gradients Studio MCP server expose?
Gradients Studio exposes 3 tools: render_gradient, list_palettes, suggest_settings. Their descriptions and schemas cost roughly 1,665 tokens of context every time the server is loaded.
Does the Gradients Studio MCP server require authentication?
No. We connected to Gradients Studio without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Gradients Studio MCP server still maintained?
Gradients Studio is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What did VerifyMCP test on the Gradients Studio MCP server?
VerifyMCP ran 13 checks on Gradients Studio, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.