Should my agent depend on the MCP server co.creativeclaw/creative-claw?

Verdict: allow — rich-fast-solo — safe to depend on As of 2026-09-06T06:21:45Z: a dated observation with receipts, not a warranty.

Creative Claw

co.creativeclaw/creative-claw

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

— the operator's own registry description reported

Publisher co.creativeclaw · first seen 2026-08-12 · endpoint https://app.creativeclaw.co/mcp

allow

verdict

rich-fast-solo

cluster

ok_tools

answers

tools served

Dependency rating derived

allow
allow — alive & usable · action ● · V n/a

allow — because answers ●, 46 tools legible (band A) ●, no confirmed drift in 6 probes ●; not yet checked: truth (1 attempts unverifiable, 0 disagreements)

Cluster rich-fast-solo · distinctiveness 0.835 (unusual). Every figure is a percentile or class within the 15,472-server census — see the whole spectrum.

Does it answer? Q1 · observed

answersalive_tools

latency55 ms

vs populationfast

protocolcurrent

authopen

Can it be used? Q4 · observed

tools46

vs populationhigh

capabilities4

harnessA

Did it hold when checked? Q3–Q4 · derived

identitysolo

servers on its host1

verifiabilityunassessed

duplicate inventoryno

drift events0

answers true0/0 agree

🔏 Signed receipt rr_c0fa2e76d6a0db8ef97fbde7 · ed25519 · key rs-rcpt-2026-08 — this rating is tamper-evident; an agent gets the full signature from check_server and can verify it against the published key.

Q1Does it answer?alive & usable — 6 probes ●evidence ↓

Q2What is it?action ● evidence ↓

Q3Can it be checked?V n/a for this kind ◐evidence ↓

Q4Did it hold?harness A · truth not yet run · no drift ●evidence ↓

Q5What company does it keep?rich-fast-solo · 1 on its host (context, not verdict) ◐evidence ↓

● observed · ◐ derived · ○ reported — the verdict synthesizes Q1–Q4; Q5 is context. Methodology →

History observed

Every probe we made, oldest → newest (6 shown, 2026-08-12 → 2026-09-06). Green answered · amber answered-but-walled · red no useful answer. A gap in our cadence is a gap in coverage, not evidence about the server.

changelog (2 events)

date	type	what changed
2026-09-06	outcome	ok_tools (was auth_required)
2026-08-12	outcome	first probe: auth_required

What kind of tools these are derived

Verification only means something relative to a tool's NATURE — an email-sender has no "true answer", a generator has no answer key. Classification evidence: classified from tool names/descriptions/annotations WE OBSERVED. What checking applies to each kind (the full methodology →):

nature	tools	meaning	what checking applies
action	25	changes the world	no true answer exists; we check the CONTRACT (destructive/read-only/idempotent declarations, error legibility) and never fire real actions
generative	11	creates content	no answer key exists; disclosure + stability checks, never truth verdicts
unclassified	5	not classifiable from its text	Tier-1 only until its tools describe themselves
retrieval-public	4	serves public facts	truth-checkable against a public source — the V-ladder applies in full
computational	1	deterministic transforms	self-checkable by re-computation and known-answer tests

Tools last seen observed

add_subtitles assemble_film check_job compare_models confirm_upload create_film_project create_template delete_asset delete_character delete_theme extract_frames generate_image generate_speech generate_video get_credits_balance get_credits_link get_film_project get_model_params get_theme get_upload_url import_media isolate_audio list_characters list_film_projects list_models list_templates list_themes load_image manage_character merge_media remove_background render_html render_html_image render_html_video render_template scale_video search_assets submit_feedback transcribe trim_video update_asset update_film_project update_template update_theme upload_asset upscale_media

Harness readiness observed

Can an agent's harness pick this tool and call it correctly? Graded on the three things an agent reads — name, description, typed parameters. Band A — an agent can pick and call these reliably.

legibility check	tools passing	ok
name is clear & specific	46/46	✓
has a description	46/46	✓
description is substantive	46/46	✓
parameters are typed	46/46	✓
parameters are described	44/46	44/46

46 of 46 tools graded · 46 with a captured input schema. RS-008, Tier-1 — no domain knowledge, applies to any tool. “Alive” is not the same as “usable”.

Truth checks observed

Not yet confirmed — 1 attempt(s) currently unverifiable (rate limits, walls, or unmappable schemas — never counted against the server) · 0 disagreements.

claim class	key	verdict	primary source
tariff-duty	unmapped	unverifiable	us-hts

Protocol conformance observed

2025-06-18

protocol version

—

session model

0.1.0

server version imagine-mcp

Capabilities: logging prompts resources tools

Drift observed

No confirmed drift on record. Baseline set 2026-09-06; changes appear here after human review.

raw probe records

probed (UTC)	outcome	http	ms	protocol
2026-09-06T06:11:53Z	ok_tools	200	55	2025-06-18
2026-08-30T06:11:41Z	auth_required	401	34
2026-08-23T06:11:31Z	auth_required	401	64
2026-08-16T06:11:23Z	auth_required	401	39
2026-08-14T19:57:51Z	auth_required	401	47
2026-08-12T05:33:08Z	auth_required	401	39

Watch or embed this verdict

Operators: put the live verdict in your README — it updates with every census, links back here, and is a dated observation, never a warranty:

[![Robin Saige verdict](https://robinsaige.com/badge/co.creativeclaw/creative-claw.svg)](https://robinsaige.com/s/co.creativeclaw/creative-claw)

Depend on it? Subscribe to its change feed — outcome changes and confirmed drift, no account needed. Building on it? The full dossier as JSON — verdict, rating, truth checks, history — stable enough to gate CI on.

← overview

Operator of this server? Everything we hold about it is on this page — free, no account, for anyone. Wrong attribution, stale probe, misclassification? Dispute this record →