Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

app.creatica/backgrounds

REMOTE · API.CREATICA.APP · 2 COMPONENTS

Deterministic procedural SVG/PNG backgrounds: 58 generators, curated palettes, brand kits.

−61 this week 23 Trust /100

Last scanned (19 hours ago)

Scores higher than 7% of remote servers

Reachable. Last reached 21 Nov 2026.

Category Design and Media

Trust breakdown (7 categories)

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 Security57
Transport & Reachability0
Schema Quality & AI Usability0
  • Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.Unverified
Stability & Change Management0
  • Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
  • Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Tool Safety0
  • Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Capabilities0
  • Capabilities not yet verified: we couldn't read the endpoint's capabilities.Unverified

Unverified: 5 categories

Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.

What we tested

Checks we ran (5)

  • TLS certificate
  • HTTPS
  • HSTS header
  • DNSSEC
  • Transport

Checks we could not complete (6)

These are gaps on our side, not findings about this hosted endpoint. We only credit what we can confirm, so a category made up entirely of them scores 0.

  • Authorization in Endpoint SecurityAuthorisation not yet verified: we couldn't confirm whether this endpoint requires it.
  • Schema quality in Schema Quality & AI Usability (scores 0 for this)Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.
  • Stability in Stability & Change Management (scores 0 for this)Stability not yet verified: not enough scan history yet (needs a 30-day window).
  • Tool coverage in Tool Coverage (scores 0 for this)Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.
  • Tool safety in Tool Safety (scores 0 for this)Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.
  • Capabilities in Capabilities (scores 0 for this)Capabilities not yet verified: we couldn't read the endpoint's capabilities.

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 →

Changelog

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.

  • 15 Nov 26 −61
    • Endpoint reachability: reachable → not serving MCP ▼ security
    • Authorization: partial → unverified ▼ security
    • Tool safety: pass → unverified ▼ security
    • Stability: pass → unverified ▼ security
    • Transport: pass → fail ▼ security
    • Capabilities: pass → unverified ▼ functional
    • Tool coverage: 100 → unverified ▼ functional
  • 13 Nov 26 +61
    • Authorization: unverified → partial ▲ security
    • Injection markers: unverified → pass ▲ security
    • Stability: unverified → pass ▲ security
    • Transport: fail → pass ▲ security
    • Endpoint reachability: not serving MCP → reachable ▲ functional
    • Tool coverage: unverified → 100 ▲ functional
    • MCP protocol: unverified → pass ▲ functional
  • 6 Nov 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 26 Oct 26 −63
    • Endpoint reachability: reachable → not serving MCP ▼ security
    • Tool safety: pass → unverified ▼ security
    • Stability: pass → unverified ▼ security
    • Authorization: partial → unverified ▼ security
    • HSTS header: pass → fail ▼ security
    • Transport: pass → fail ▼ security
    • Capabilities: pass → unverified ▼ functional
    • Tool coverage: 100 → unverified ▼ functional
    • First check of Schema quality: unverified functional
  • 9 Oct 26 0
    • Stability: 0.93 → pass security
  • 28 Sept 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 25 Sept 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 7 Sept 26 0
    • Stability: unverified → 0.03 ▲ functional
Diagnostics

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://api.creatica.app/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=creatica.app CN=YE1,O=Let's Encrypt,C=US 25 Oct 2026 23 Jan 2027 ECDSA 256 ECDSA-SHA384 60c7260f1bdac254031e3ae8e55c2457f33
SANs: *.creatica.app, creatica.app
CN=YE1,O=Let's Encrypt,C=US (CA) CN=Root YE,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 ECDSA 384 ECDSA-SHA384 5ddd70dd31f801c85c186a7a04b80afe
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.creatica.app. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
app. DS published 23684 8 Verified
creatica.app. No DS Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication Inconclusive

We could not reach the endpoint well enough to judge its authorisation posture.

Result Inconclusive
HTTP status 429

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://api.creatica.app/mcp HTTP error 429
http (plaintext) http://api.creatica.app/mcp HTTPS enforced 301 https://api.creatica.app/mcp
MCP tools · 6 exposed · ~602 tokens

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 →

Tool Tokens
describe_background ~97

Full style card for one structure: what it looks like, mood, where text can go, tips, and every parameter it honours with ranges, defaults and the visual effect of low/high values. Also returns the JSON Schema for a generate request.

NameTypeReqDescription
formatstring–markdown (default) is best for reading; json includes the JSON Schema.
namestringyesStructure name from list_backgrounds, e.g. "wave".

No output schema declared.

No examples provided.

generate_background ~233

Render a background as SVG or PNG. Deterministic: the same structure, options and seed always give the same image, so store the returned seed. Returns a permanent, cacheable image URL you can use directly in <img>/CSS, plus an inline PNG preview. Call describe_background first to learn which shape options the structure honours.

NameTypeReqDescription
brandstring–Slug of a saved brand kit (see list_brand_kits); its colours become the palette baseline.
formatstring–png (default) returns a viewable image; svg returns the vector source.
heightinteger––
paletteobject––
pngWidthinteger–Raster width for PNG output/preview. Defaults to the render width, capped for inline previews.
seedstring–Any string. Omit for a fresh random seed (returned in the result).
shapeobject–Structure-specific options; call describe_background for the exact keys, ranges and what they do.
structurestringyesStructure name, e.g. "wave".
widthinteger––

No output schema declared.

No examples provided.

list_backgrounds ~106

Browse the catalog of background structures. Optionally filter by a free-text query, tag or mood word. Returns name, one-line summary, mood, use cases and a preview URL for each.

NameTypeReqDescription
limitinteger––
moodstring–A mood word, e.g. dark, playful, minimal, retro.
querystring–Free text, e.g. "calm waves" or "geometric poster".
tagstring––

No output schema declared.

No examples provided.

list_brand_kits ~38

Saved brand palettes on this account. Pass a kit's slug as `brand` to generate_background to render on-brand without repeating hex colours.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

list_palettes ~66

Built-in curated colour palettes with their hex colours and derived mood tags (dark, pastel, vivid, warm, cool…). Pass the id as palette.palette to generate_background.

NameTypeReqDescription
moodstring–Filter by a mood tag, e.g. "dark" or "pastel".

No output schema declared.

No examples provided.

suggest_backgrounds ~62

Rank structures for a natural-language brief ("dark aurora glow for an AI landing page"). Returns why each matched, matching built-in palettes, and a ready-to-run example request for generate_background.

NameTypeReqDescription
briefstringyes–
limitinteger––

No output schema declared.

No examples provided.

Install

How do I install the app.creatica/backgrounds MCP server?

app.creatica/backgrounds is a hosted endpoint at https://api.creatica.app/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.creatica.app

# add to Claude Code
claude mcp add --transport http app-creatica-backgrounds 'https://api.creatica.app/mcp'
Common questions

What is the app.creatica/backgrounds MCP server?

app.creatica/backgrounds is an MCP server listed in the public MCP registry as app.creatica/backgrounds. Deterministic procedural SVG/PNG backgrounds: 58 generators, curated palettes, brand kits. This page covers its hosted endpoint (https://api.creatica.app/mcp).

Is the app.creatica/backgrounds MCP server safe to use?

app.creatica/backgrounds scores 23 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 app.creatica/backgrounds MCP server expose?

app.creatica/backgrounds exposes 6 tools: list_backgrounds, suggest_backgrounds, describe_background, list_palettes, list_brand_kits, generate_background. Their descriptions and schemas cost roughly 602 tokens of context every time the server is loaded.

Does the app.creatica/backgrounds MCP server require authentication?

Its publisher declares no required credentials for app.creatica/backgrounds. We have not been able to confirm that against the live endpoint, and a server can require authorisation without declaring it here.

Is the app.creatica/backgrounds MCP server still maintained?

app.creatica/backgrounds 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 app.creatica/backgrounds MCP server?

VerifyMCP ran 5 checks on app.creatica/backgrounds, covering TLS certificate, HTTPS, HSTS header, DNSSEC and 1 more. 6 items could not be completed, a gap on our side rather than a finding about app.creatica/backgrounds: Authorization, Schema quality, Stability, Tool coverage and 2 more. 5 categories score 0 for that reason, because we only credit what we can confirm. 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.