Skip to content

Smasher Studio — AI Fashion Design MCP server

io.github.Atenkai/smasher-studioAtenkaistreamable-httpv1.0.0Scanned

AI fashion design — product photos, videos, tech packs, colorways & fabric sims.

5 tools: 2 change things and 3 only read.

Tools: 0 delete, 0 irreversible, 2 write, 3 read.
  • Reads private data · 0
  • Reads text others write · 0
  • Can send data out · 0
  • No findings

Tools listed without sign-in. Remote posture

With Anlyon

2 tools here change things. Govern them.

  • Anlyon lists the tools and adopts none.
  • Each tool you adopt gets approvals and receipts.
  • Your agent never holds the key.
Govern this server →

A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.

What the Smasher Studio — AI Fashion Design MCP server can do

The Smasher Studio — AI Fashion Design MCP server is published by the GitHub account Atenkai. It has 5 tools. It can create or change data (2 tools: check_credits and quote_dxf_pattern), but cannot delete data. 3 tools only read.

None of its tools reads private data, brings in text other people write, or sends data out.

None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.

Its remote endpoint lists its tools without sign-in, and its tools changed once since Anlyon Radar first saw them.

Last scanned Nov 15, 2026, version 1.0.0.

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

5 tools

Changes things 2Claude Code: ask
  • check_creditsCheck the user's current credit balance, subscription plan, and monthly allocation.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    Check the user's current credit balance, subscription plan, and monthly allocation. Free to use.

    Annotations the server declares

    • title: Check Credits
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • quote_dxf_patternEstimate the price of a factory-ready DXF cutting pattern for a garment, cut by a human pattern maker.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    Estimate the price of a factory-ready DXF cutting pattern for a garment, cut by a human pattern maker. Returns the complexity tier, the fee in USD, the delivery window and the add-on prices. Free, and it creates nothing: no order, no payment, no account needed. The tier is ESTIMATED here; the binding classification is made server-side when the order is created in the web app, and the buyer never chooses it. Garments and sewn accessories (ties, bags, backpacks, hats, belts, scarves): footwear and hard goods (jewellery, eyewear, watches) are refused with code non_apparel. Bands: 2 à 6 pièces = $29, 7 à 15 pièces = $59, 16 pièces et plus = $129.

    Annotations the server declares

    • title: Quote a DXF Pattern
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
Only reads 3Show 3 read-only tools
  • get_order_statusCheck the status of the caller's own pattern-making orders: where each one is, its complexity tier, its fee and when it was placed.No findings

    Why it is in this group

    • The name "get_order_status" says "get": a word for reading.
    Description, as the server wrote it
    Check the status of the caller's own pattern-making orders: where each one is, its complexity tier, its fee and when it was placed. Free. Requires authentication. Read-only: it cannot create, pay for or cancel an order.

    Annotations the server declares

    • title: Get Order Status
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • get_tech_pack_specReturn the specification a pattern maker works from for a garment: points of measure with tolerances at a base size, the fabric class, weight band and stretch behaviour, and the se…No findings

    Why it is in this group

    • The name "get_tech_pack_spec" says "get": a word for reading.
    Description, as the server wrote it
    Return the specification a pattern maker works from for a garment: points of measure with tolerances at a base size, the fabric class, weight band and stretch behaviour, and the seam and hem allowance convention. Free, stores nothing, needs no account. This is the SPEC, not the pattern: the DXF itself is cut by a human pattern maker on a paid order, and it is delivered NET of seam allowance unless the seam allowance extra ($5) is bought.

    Annotations the server declares

    • title: Get Tech Pack Spec
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • list_collectionsList the user's design collections with session counts and asset counts.No findings

    Why it is in this group

    • The name "list_collections" says "list": a word for reading.
    Description, as the server wrote it
    List the user's design collections with session counts and asset counts. Requires authentication.

    Annotations the server declares

    • title: List Collections
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or untrusted-input or outbound.

Reads private data0
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write0
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out0
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

Tools listed without sign-in

Looked at Nov 20, 2026, 18:56 UTC, unchanged since Oct 22, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
yes
HTTP status of an anonymous initialize
200
tools/list served without credentials
yes
Tools that change things, listed without credentials
2
Protocol version
2025-06-18
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
https://www.smasher.studio/.well-known/oauth-protected-resource
Authorization servers
https://www.smasher.studio
Legacy HTTP+SSE transport
no
Dynamic client registration
yes
Client ID metadata documents
no
  • WarnThe whole server

    The endpoint served tools/list without credentials, and the list has 2 tools that change things (2 write). Whether a call also works without credentials was not tested: tools are never called.

    Matched text

    https://www.smasher.studio/mcp/mcp: tools/list returned 5 tools to an anonymous client, including check_credits (write), quote_dxf_pattern (write)

    What this check looks for

Findings

Matches of fixed checks, with the text they matched.

No check matched anything in these tool definitions. That is not a safety guarantee.

History

Changes to its tool definitions and to its remote endpoint, newest first.

  1. Tools1 changed.~1 changedView diff

Install

Pinned to version 1.0.0. Values in angle brackets are yours to fill in.

claude mcp add --transport http smasher-studio https://www.smasher.studio/mcp/mcp
claude mcp add --transport http smasher-studio https://www.smasher.studio/mcp/mcp

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__smasher-studio__list_collections",
      "mcp__smasher-studio__get_tech_pack_spec",
      "mcp__smasher-studio__get_order_status"
    ],
    "ask": [
      "mcp__smasher-studio__check_credits",
      "mcp__smasher-studio__quote_dxf_pattern"
    ],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as smasher-studio. Review it before you use it.

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://radar.anlyon.com/api/v1/servers/io.github.Atenkai/smasher-studio/verify?hash=3994a4d71e361527fbf595a95d04abf9abda7feaf3f5575fb51f12880b095054" | jq -e '.changed == false'

Pinned hash 3994a4d71e36, from Nov 15, 2026, 17:17 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/io.github.Atenkai/smasher-studio/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for io.github.Atenkai/smasher-studio
[![Anlyon Radar](https://radar.anlyon.com/badge/io.github.Atenkai/smasher-studio.svg)](https://radar.anlyon.com/servers/io.github.Atenkai/smasher-studio)

Source: MCP Registry · repository. Synced Oct 21, 2026, 18:14 UTC.

Smasher Studio — AI Fashion Design MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the Smasher Studio — AI Fashion Design MCP server safe?

No scan can promise that. What its definitions show: 5 tools, 2 of which can change, send or delete something, and 0 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.

Can the Smasher Studio — AI Fashion Design MCP server delete data?

No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.

Can the Smasher Studio — AI Fashion Design MCP server do things that cannot be undone?

No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.

What tools does the Smasher Studio — AI Fashion Design MCP server have?

5 tools: 2 write, 3 read. check_credits, quote_dxf_pattern, list_collections, get_tech_pack_spec and get_order_status.

Does the Smasher Studio — AI Fashion Design MCP server need sign-in or OAuth?

Its remote endpoint listed its tools to an anonymous client, without sign-in.

Does the Smasher Studio — AI Fashion Design MCP server send data to outside services?

None of its tools sends, posts or publishes, or takes a recipient, channel or URL.

Has the Smasher Studio — AI Fashion Design MCP server changed its tools?

Yes, once since Anlyon Radar started tracking it, most recently on Nov 2, 2026. Every change is on this page and in its Atom feed.