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.

Creative Claw

REMOTE · APP.CREATIVECLAW.CO

On-brand creative studio for AI agents: images, video, audio, and 3D.

+5 this week 36 Trust /100

Last scanned (12 hours ago)

Scores higher than 19% of remote servers

Reachable. Last reached 6 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 Security89
Transport & Reachability0
Schema Quality & AI Usability0
  • Schema blocked by authentication: the endpoint requires auth we don't have to read it. See how to fix → Unverified
Stability & Change Management0
  • Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
  • Tool coverage blocked by authentication: the endpoint requires auth we don't have to read its tools.Unverified
Tool Safety0
  • Tool safety blocked by authentication: the endpoint requires auth we don't have to read its tools.Unverified
Capabilities0
  • Capabilities blocked by authentication: the endpoint requires auth we don't have to read them. See how to fix → Unverified

Unverified: 6 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. Claim this server and supply a read-only token to verify it and lift the score.

What we tested

Checks we ran (5)

  • TLS certificate
  • Authorization
  • HTTPS
  • HSTS header
  • DNSSEC

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.

  • Transport in Transport & Reachability (scores 0 for this)Transport blocked by authentication: the endpoint requires auth we don't have to verify streamable-http.
  • Schema quality in Schema Quality & AI Usability (scores 0 for this)Schema blocked by authentication: the endpoint requires auth we don't have to read it.
  • 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 blocked by authentication: the endpoint requires auth we don't have to read its tools.
  • Tool safety in Tool Safety (scores 0 for this)Tool safety blocked by authentication: the endpoint requires auth we don't have to read its tools.
  • Capabilities in Capabilities (scores 0 for this)Capabilities blocked by authentication: the endpoint requires auth we don't have to read them.

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.

  • 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
  • 3 Nov 26 +5
    • HTTPS: unverified → 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
  • 23 Sept 26 0
    • Endpoint reachability: reachable → behind authorisation ▼ security
    • Stability: fail → unverified ▼ security
    • Tool safety: pass → unverified ▼ security
    • Transport: pass → unverified ▼ security
    • Authorization: The endpoint enforces authorisation, advertised via RFC 9728 protected-resource metadata. security
    • Capabilities: pass → unverified ▼ functional
    • Tool coverage: 100 → unverified ▼ functional
    • Schema quality: 100 → unverified ▼ functional
  • 22 Sept 26 0
    • This server's schema is too large to store in full, so we cannot compare its tools day to day functional
  • 21 Sept 26 0
    • This server's schema is too large to store in full, so we cannot compare its tools day to day functional
  • 20 Sept 26 0
    • This server's schema is too large to store in full, so we cannot compare its tools day to day 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 6 Nov 2026 · Probed https://app.creativeclaw.co/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=creativeclaw.co CN=YE1,O=Let's Encrypt,C=US 17 Sept 2026 16 Dec 2026 ECDSA 256 ECDSA-SHA384 6efcbe8a543b85ad7d98f2c0beb82256166
SANs: *.creativeclaw.co, creativeclaw.co
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 app.creativeclaw.co. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
co. DS published 7786 8 Verified
creativeclaw.co. No DS Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication Enforced and verified

The endpoint asked for a token and published valid RFC 9728 metadata describing how to get one.

Result Enforced and verified
Enforced On connection
HTTP status 401

WWW-Authenticate challenge Bearer resource_metadata="https://app.creativeclaw.co/.well-known/oauth-protected-resource/mcp"

Bearer resource_metadata="https://app.creativeclaw.co/.well-known/oauth-protected-resource/mcp"
Header Value
www-authenticate Bearer resource_metadata="https://app.creativeclaw.co/.well-known/oauth-protected-resource/mcp"

Protected resource metadata

Document https://app.creativeclaw.co/.well-known/oauth-protected-resource/mcp
Retrieved Yes
Resource https://app.creativeclaw.co/mcp
Authorisation server https://clerk.creativeclaw.co

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

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://app.creativeclaw.co/mcp Auth required 401
http (plaintext) http://app.creativeclaw.co/mcp HTTPS enforced 302 https://app.creativeclaw.co/mcp
MCP tools · 53 exposed · ~24,527 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
update_asset ~223

Organize a media asset by setting its name, tags, or description. Assets are entries in your media library (images, videos, audio, 3D models). - **Name**: Unique per user — lets you reference assets by name instead of ID. - **Tags**: Labels for grouping (e.g. "brand", "logo", "draft"). - **Description**: Free-text description. Examples: update_asset({ id: "...", name: "my-logo", tags: ["brand"] }). Clear name: update_asset({ id: "...", clear_name: true }).

NameTypeReqDescription
clear_nameboolean–Set to true to remove the asset's name
descriptionstring–Set or update the asset description
idstringyesThe asset ID to update
namestring–Set a unique name for this asset. Must be unique across your assets. Use null to clear the name.
tagsarray–Set tags for this asset (replaces existing tags). Pass an empty array to clear tags.

No output schema declared.

No examples provided.

update_film_project ~275

Update a film project: save the script (logline + shots), advance status, attach generated assets, or change the cast/theme. Shots: pass the full `shots` array to replace the shot list (e.g. when first saving the script), OR `patch_shots` to merge changes into existing shots by id (e.g. after generating one shot's storyboard/clip — set its storyboardUrl/clipUrl/status). Each shot: { id, description, prompt?, narration?, storyboardUrl?, clipUrl?, audioUrl?, durationS?, model?, status? }. Status values: drafting → script_ok → storyboard_ok → rendering → preview_ok → final. Set status to reflect approval gates as the user approves.

NameTypeReqDescription
assembled_urlstring–Final stitched film URL
audio_urlstring–Full narration track URL
briefstring––
character_idsarray––
idstringyes–
loglinestring––
namestring––
patch_shotsarray–Validated partial shot updates merged by stable id.
shotsarray–Full validated shot list; replaces the existing list.
statusstring––
target_duration_sinteger––
theme_idstring––

No output schema declared.

No examples provided.

update_template ~306

Update an existing template's fields. Pass template_id or template_name, then any subset of fields to overwrite. Fields you omit are left alone. Kind cannot be changed after creation. **Replacement semantics:** parameters, model_params, and reference_asset_ids are fully replaced when passed. **Validation:** if html or prompt is replaced, every {{token}} must match a parameter — using the NEW parameters when also passed in the same call.

NameTypeReqDescription
descriptionstring–New description
heightinteger–html kind only. New height.
htmlstring–html kind only. Replacement HTML markup.
model_paramsobject–Generative kind only. Replacement model_params object.
namestring–New name (unique per user, case-insensitive)
parametersarray–Replacement parameter list
promptstring–Generative kind only. Replacement prompt body.
recommended_modelstring–Generative kind only. New registry model id.
reference_asset_idsarray–Generative kind only. Replacement reference asset id list.
sizesarray–html kind only. Replacement named sizes list. Pass [] to clear and fall back to width/height.
template_idstring–Template ID. Provide either this or template_name.
template_namestring–Template name to look up (case-insensitive). Provide either this or template_id.
widthinteger–html kind only. New width.

No output schema declared.

No examples provided.

update_theme ~552

Create or update a brand theme. Themes store colors, fonts, logos, a markdown `notes` field (voice / audience / tone / do's-and-don'ts), a reference image, and any brand elements used for consistent media generation. Two modes: - **interactive** (`interactive: true`) — opens the visual editor in the chat for the user to drop fonts/colors/logos and click save. Use this for "edit my theme" / "help me set up a brand" style requests. - **direct** — pass `data`, `images`, and/or `set_default` to mutate without UI. Shallow-merges `data` by default; pass `override: true` to replace it entirely. `images` is always replaced. First image becomes the thumbnail. Creates a new theme if the name doesn't exist. First theme auto-becomes default. Examples: - update_theme({ interactive: true }) // create a new theme via the editor - update_theme({ name: "Acme", interactive: true }) // edit "Acme" in the editor - update_theme({ name: "Acme", data: { colors: [{ name: "Brand", hex: "#FF0000" }] } }) - update_theme({ name: "Acme", images: ["https://r2.../hero1.png"] })

NameTypeReqDescription
dataobject–Theme data — colors, fonts, logos, etc. Merged with existing data by default. Pass only when updating data; pass only `images` to update brand reference images.
imagesarray–Brand reference images for this theme — passed to image/video models as visual references. Replaces the entire images array when provided. The first image is automatically saved as the theme's thumbn…
interactiveboolean–When true, open the visual theme editor (fonts, colors, logos, reference image) in the chat instead of mutating directly. The user fills in the form and clicks save; the editor calls update_theme aga…
namestring–Theme name. Creates the theme if it doesn't exist. Optional only when interactive=true (the user picks/creates a theme inside the editor).
overrideboolean–If true, replaces the entire theme data. If false (default), shallow-merges with existing data — top-level keys are replaced, missing keys are preserved. Only applies to `data`; `images` is always re…
set_defaultboolean–If true, makes this theme the default.

No output schema declared.

No examples provided.

upload_asset ~295

Add a file to your asset library by direct URL. This tool supports images, videos, audio, 3D models, and ZIP archives. The type is inferred from content_type when omitted and the MIME family is unambiguous. Provide type for generic MIME values such as application/octet-stream. HTML webpages and JSON/API responses are rejected. JSON-based glTF is accepted only when served as model/gltf+json with type 3d_model. ZIPs use type zip and are limited to 1 GiB. The check uses the server's Content-Type header and does not inspect file contents. The server stores accepted files permanently and returns a URL usable with other tools. Optionally set name, tags, and description for organization.

NameTypeReqDescription
content_typestringyesMIME type of the file (e.g. "image/png", "video/mp4", "audio/mp3")
descriptionstring–Optional description of the asset
namestring–Optional unique name for the asset
tagsarray–Optional tags for the asset
typestring–Asset type. Optional when content_type clearly identifies an image, video, audio file, 3D model, or ZIP archive.
urlstringyesDirect URL of a publicly accessible image, video, audio, 3D-model, or ZIP file to import and store permanently. Webpage and JSON API URLs are rejected.

No output schema declared.

No examples provided.

upscale_media ~586

Upscale an image or video to higher resolution using AI. Returns a permanent URL to the upscaled result. **Images** — three models: - **aura** (default): Cheapest and fastest, fixed 4x upscale. Just provide the URL. - **clarity**: Best quality, 1-4x, supports prompt-guided upscaling with creativity/resemblance controls. Uses an 80-credit hold based on current fal megapixel pricing. - **recraft**: Simple crisp upscale, no extra params needed. **Videos** — two models: - **realesrgan** (default): Cheapest, 1-8x scale factor. - **bytedance**: Higher quality with target resolution presets (1080p/2k/4k) and FPS boost. Tips: - For quick/cheap upscaling, just provide media_url and type — defaults handle the rest. - For maximum image quality, use clarity model with a prompt. - For 4K video output, use bytedance model with target_resolution="4k".

NameTypeReqDescription
creativitynumber–Creativity level 0-1 (image, clarity model only). Higher = more hallucinated detail. Default: 0
enhancement_presetstring–Enhancement preset (video, bytedance model only). Default: general
media_urlstringyesURL of the image or video to upscale
promptstring–Guide the upscaling (image, clarity model only). Describes desired output quality.
resemblancenumber–Resemblance to original 0-1 (image, clarity model only). Higher = closer to input. Default: 1
seednumber–Seed for reproducibility (image, clarity model only)
target_fpsstring–Target FPS (video, bytedance model only). Default: 30
target_resolutionstring–Target resolution (video, bytedance model only). Default: 1080p
typestringyesType of media: image or video
upscale_factornumber–Upscale factor 1-4x (image, clarity model only). Aura is fixed at 4x. Default: 2
upscale_modelstring–Upscaler model. For images: aura (cheapest/fastest, 4x fixed), clarity (best quality, 1-4x, prompt-guided), recraft (crisp/simple). For videos: realesrgan (cheapest, 1-8x), bytedance (higher quality…
upscale_scaleinteger–Scale factor 1-8x (video, realesrgan model only). Default: 2

No output schema declared.

No examples provided.

Install

How do I install the Creative Claw MCP server?

Creative Claw is a hosted endpoint at https://app.creativeclaw.co/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 · app.creativeclaw.co

# add to Claude Code
claude mcp add --transport http co-creativeclaw-creative-claw 'https://app.creativeclaw.co/mcp'
Common questions

What is the Creative Claw MCP server?

Creative Claw is an MCP server listed in the public MCP registry as co.creativeclaw/creative-claw. On-brand creative studio for AI agents: images, video, audio, and 3D. This page covers its hosted endpoint (https://app.creativeclaw.co/mcp).

Is the Creative Claw MCP server safe to use?

Creative Claw scores 36 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 Creative Claw MCP server expose?

Creative Claw exposes 53 tools: mcp_ui_action, generate_image, compare_models, generate_video, generate_speech, and 48 more. Their descriptions and schemas cost roughly 24,527 tokens of context every time the server is loaded.

Does the Creative Claw MCP server require authentication?

Yes. Creative Claw asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.

Is the Creative Claw MCP server still maintained?

Creative Claw is still listed as active in the MCP registry. We last reached this channel on 6 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 Creative Claw MCP server?

VerifyMCP ran 5 checks on Creative Claw, covering TLS certificate, Authorization, HTTPS, HSTS header and 1 more. 6 items could not be completed, a gap on our side rather than a finding about Creative Claw: Transport, Schema quality, Stability, Tool coverage and 2 more. 6 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.