MCP/Risk

Scan report

co.creativeclaw/creative-claw

remote, scanned 2026-09-10, tool surface via remote-tools-list

This page reports an automated security scan of co.creativeclaw/creative-claw (remote), scanned 2026-09-10. It rates trust (provenance, transport, known vulnerabilities, instruction integrity) as grade D and capability risk (what the tools can do) separately at high. It does not certify the server is safe to connect; it reports what could be checked from outside.

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

Verify manually - the scoring model can’t judge these for you

  • §2.3 - Is the tool surface no broader than the server’s stated purpose requires?
  • §3.4 - For stdio servers: which environment credentials does it read, and are they scoped rather than org-wide tokens?
  • §6.1 - Cross this server’s capabilities with your already-connected servers: any read-capability × send-capability pairs need explicit sign-off.
  • §6.2 - Run the connecting agent with sandboxing and egress controls sized to the combined tool surface, not just this server’s.

Methodology: MCP Server Security Policy. Checks and scoring weights are open source. Unfamiliar term? See the glossary.