MCP/Risk

Directory / server

co.creativeclaw/creative-claw

registry.modelcontextprotocol.io, scanned 2026-09-10, tool surface via remote-tools-list

This directory entry reports an automated security scan of co.creativeclaw/creative-claw, scanned 2026-09-10. Trust grade D rates provenance, transport, known vulnerabilities and instruction integrity; capability risk is reported separately, not folded into the grade.

Automated checks

StatusCheckPolicyResult
PASS Listed on the official MCP registry §1.1
Listed on registry.modelcontextprotocol.io as co.creativeclaw/creative-claw. 1 finding
  • Registry entry: co.creativeclaw/creative-claw ↗
WARN Source repository is public and maintained §1.2
Repository health issues: no license. 5 findings
  • Repository ↗
  • Last push: 0 days ago
  • Stars: 2
  • License: none detected
  • Security policy (SECURITY.md): absent
INFO Published package is consistent and attested §1.3

No published package associated with this server (remote-only or non-npm/PyPI source).
PASS Tool surface is inspectable and proportionate §2.1–§2.4
53 tool(s) enumerated. Capabilities detected: network-egress. Reported as capability risk (§2.4); whether each is essential to the server's stated purpose is §2.3 and remains a manual judgement. 3 findings
  • Tools exposed: 53
  • get_upload_url: network-egress
  • Detected capabilities: network-egress
PASS HTTPS-only endpoint §3.1
Endpoint uses HTTPS. 1 finding
  • Endpoint: https://app.creativeclaw.co/mcp
FAIL Authentication required §3.2

Server answers anonymous requests (HTTP 200) while exposing non-trivial or unverifiable capabilities - fail per §3.2.
PASS OAuth protected-resource metadata published §3.3
Publishes /.well-known/oauth-protected-resource per the June 2025 authorization spec. 1 finding
  • Authorization server: https://clerk.creativeclaw.co
INFO No known vulnerabilities (OSV.dev) §4.1

No package to query (remote-only server).
WARN Server-supplied instructions free of poisoning indicators §5.1–§5.4
7 suspicious indicator(s) found in server-supplied instructions, tool descriptions, or schemas. 7 findings
  • server instructions: oversized: 7405 chars (limit 4096)
  • generate_image description: oversized: 4446 chars (limit 2048)
  • generate_video description: oversized: 5194 chars (limit 2048)
  • generate_speech description: oversized: 5737 chars (limit 2048)
  • transcribe description: oversized: 2516 chars (limit 2048)
  • server instructions: cross-tool shadowing: before calling the downstream tool
  • update_theme: embedded URL: https://r2.../hero1.png

Score history

DateGradeScore
2026-09-10D61/100
2026-07-28C79/100
What this grade covers
  • Provenance & supply-chain integrity (§1)
  • Tool surface & capability risk (§2)
  • Transport & authentication (§3)
  • Known CVEs via OSV.dev (§4)
  • Instruction/tool poisoning patterns (§5)

Limitations: pattern-based only (no semantic injection detection), static npm analysis (live server instructions not retrieved for package-only scans), single-server scope (no cross-server toxic flow analysis). See the full policy.

Methodology: MCP Server Security Policy. Unfamiliar term? See the glossary.