Smasher Studio — AI Fashion Design
REMOTE · WWW.SMASHER.STUDIO · SCANNED SEP 27
AI fashion design — product photos, videos, tech packs, colorways & fabric sims.
Available components
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 Security69
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement. View diagnostics → Unverified
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability76
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 2488 tokens (~226/item across 11 items; 5 tools + 6 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management23
- Stability check failed: schema churn in the 30 days we've observed: 6 tool removals, 0 breaking changes, 0 auth/transport breaks, 3 additions. See how to fix → Fail
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
- Structured output schemas are declared (60% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 7 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
How do I install the Smasher Studio — AI Fashion Design MCP server?
Smasher Studio — AI Fashion Design is a hosted endpoint at https://www.smasher.studio/mcp/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 · www.smasher.studio
claude mcp add --transport http atenkai-smasher-studio 'https://www.smasher.studio/mcp/mcp'
{
"mcpServers": {
"atenkai-smasher-studio": {
"url": "https://www.smasher.studio/mcp/mcp"
}
}
} {
"servers": {
"atenkai-smasher-studio": {
"type": "http",
"url": "https://www.smasher.studio/mcp/mcp"
}
}
} [mcp_servers.atenkai-smasher-studio] url = "https://www.smasher.studio/mcp/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"atenkai-smasher-studio": {
"type": "remote",
"url": "https://www.smasher.studio/mcp/mcp",
"enabled": true
}
}
} openclaw mcp add atenkai-smasher-studio --url 'https://www.smasher.studio/mcp/mcp' --transport streamable-http
mcp_servers:
atenkai-smasher-studio:
url: "https://www.smasher.studio/mcp/mcp" {
"McpServers": {
"atenkai-smasher-studio": {
"Transport": "http",
"Url": "https://www.smasher.studio/mcp/mcp"
}
}
} assistant mcp add atenkai-smasher-studio -t streamable-http -u 'https://www.smasher.studio/mcp/mcp'
{
"mcpServers": {
"atenkai-smasher-studio": {
"type": "http",
"url": "https://www.smasher.studio/mcp/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
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.
- 27 Sept 26 0
- This server's schema is too large to store in full, so we cannot compare its tools day to day functional
- 26 Sept 26 0
- This server's schema is too large to store in full, so we cannot compare its tools day to day 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
- 24 Sept 26 0
- This server's schema is too large to store in full, so we cannot compare its tools day to day functional
- 23 Sept 26 0
- This server's schema is too large to store in full, so we cannot compare its tools day to day 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
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 27 Sept 2026 · Probed https://www.smasher.studio/mcp/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=www.smasher.studio | CN=YR1,O=Let's Encrypt,C=US | 23 Sept 2026 | 22 Dec 2026 | RSA 2048 | SHA256-RSA | 6cd4ce7a1b2da485381b9de05f0b726f4c7 |
| SANs: www.smasher.studio | ||||||
| CN=YR1,O=Let's Encrypt,C=US (CA) | CN=Root YR,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | RSA 2048 | SHA256-RSA | a20253f15f2691c05dc1ce13b9bcca4e |
| CN=Root YR,O=ISRG,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | RSA 4096 | SHA256-RSA | f24b6d17f9d9ad7cb1c9fea78782699f |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of www.smasher.studio. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| studio. | present | 1354 | 8 | Verified |
| smasher.studio. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=31536000; includeSubDomains |
| content-security-policy | default-src 'self'; script-src 'self' 'nonce-/OTCrKq9ZDOlzIKCBa8IBw==' 'unsafe-inline' https://accounts.google.com https://apis.google.com https://js.stripe.com https://m.stripe.network https://connect.facebook.net; style-src 'self' 'unsafe-inline' https://fonts.googleapis.com https://accounts.google.com; img-src 'self' data: blob: https://link.storjshare.io https://*.bfl.ai https://api.bfl.ai https://bflusercontent.com https://*.bflusercontent.com https://*.runwayml.com https://*.fal.media https://storage.googleapis.com https://*.stripe.com https://avatars.githubusercontent.com https://lh3.googleusercontent.com https://images.unsplash.com; media-src 'self' data: blob: https://link.storjshare.io https://*.bfl.ai https://api.bfl.ai https://bflusercontent.com https://*.bflusercontent.com https://*.runwayml.com https://*.fal.media https://storage.googleapis.com; font-src 'self' https://fonts.gstatic.com; connect-src 'self' https://smasher-studio-server-727599f8d65c.herokuapp.com https://link.storjshare.io https: |
| x-content-type-options | nosniff |
| x-frame-options | DENY |
| referrer-policy | strict-origin-when-cross-origin |
| permissions-policy | camera=(), microphone=(), geolocation=(), payment=(self) |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://www.smasher.studio/mcp/mcp | Verified | 200 | |
| http (plaintext) | http://www.smasher.studio/mcp/mcp | Inconclusive | 405 |
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 →
check_credits Check Credits ~44
Check the user's current credit balance, subscription plan, and monthly allocation. Free to use.
| Name | Type | Req | Description |
|---|---|---|---|
| verbose | boolean | – | If true, include detailed plan info and upgrade suggestions |
| Name | Type | Req | Description |
|---|---|---|---|
| authenticated | boolean | yes | Whether the user is authenticated |
| credits_per_month | number | – | Monthly credit allocation (authenticated users) |
| credits_per_month_guest | number | – | Monthly credit limit (guest users) |
| credits_remaining | number | yes | Current credit balance |
| plan | string | yes | Subscription plan: free, creator, studio, pro, or guest |
| tip | string | – | Guidance for unauthenticated users |
No examples provided.
get_order_status Get Order Status ~119
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.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Maximum number of orders to return (default 10) |
| order_id | string | – | A single order id. Omit to list the caller's orders. |
| status | string | – | Filter the list by status, e.g. SUBMITTED, IN_PROGRESS, COMPLETED |
No output schema declared.
No examples provided.
get_tech_pack_spec Get Tech Pack Spec ~218
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.
| Name | Type | Req | Description |
|---|---|---|---|
| base_size | string | – | Base size for the measurement table: XS, S, M, L, XL. Defaults to M. |
| description | string | – | Construction detail that refines the read: panels, lining, closures, pockets |
| fabric_class | string | – | How the fabric behaves. Decides the stretch note and the cutting warnings. |
| fabric_weight | string | – | Fabric weight band, if known |
| garment_type | string | yes | Garment family in plain words: "structured blazer", "midi dress", "hoodie" |
No output schema declared.
No examples provided.
list_collections List Collections ~41
List the user's design collections with session counts and asset counts. Requires authentication.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | number | – | Maximum number of collections to return (default: all) |
| Name | Type | Req | Description |
|---|---|---|---|
| authenticated | boolean | yes | Whether the user is authenticated |
| collections | array | yes | List of design collections |
| tip | string | – | Guidance for unauthenticated users |
| total | number | yes | Total number of collections |
No examples provided.
quote_dxf_pattern Quote a DXF Pattern ~230
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. Bands: 2 à 6 pièces = $29, 7 à 15 pièces = $59, 16 pièces et plus = $129.
| Name | Type | Req | Description |
|---|---|---|---|
| add_ons | array | – | Optional paid extras to include in the total. Each is priced separately and none is included in the base fee. |
| garment_description | string | yes | The garment in plain words: type, silhouette, construction, linings, closures. "Lined wool overcoat with welt pockets and a half belt" |
| piece_estimate | integer | – | Number of pattern pieces, if known. Only used when the description does not name a garment the classifier recognises. |
| Name | Type | Req | Description |
|---|---|---|---|
| add_ons | array | yes | Every paid add-on, with its price. None is included in the base fee. |
| currency | string | yes | Always USD |
| delivery_hours | number | yes | Hours from a pattern maker claiming the order |
| estimated | boolean | yes | Always true: the binding classification is made server-side at order time |
| fee_usd | number | yes | Base fee for the tier, in USD |
| how_to_order | string | yes | Where the order is actually placed |
| tier | string | yes | Estimated complexity tier |
| total_usd | number | yes | Base fee plus the selected add-ons |
No examples provided.
What is the Smasher Studio — AI Fashion Design MCP server?
Smasher Studio — AI Fashion Design is an MCP server listed in the public MCP registry as io.github.Atenkai/smasher-studio. AI fashion design, product photos, videos, tech packs, colorways & fabric sims. This page covers its hosted endpoint (https://www.smasher.studio/mcp/mcp).
Is the Smasher Studio — AI Fashion Design MCP server safe to use?
Smasher Studio — AI Fashion Design scores 73 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 Smasher Studio — AI Fashion Design MCP server expose?
Smasher Studio — AI Fashion Design exposes 5 tools: check_credits, list_collections, quote_dxf_pattern, get_tech_pack_spec, get_order_status. Their descriptions and schemas cost roughly 652 tokens of context every time the server is loaded.
Does the Smasher Studio — AI Fashion Design MCP server require authentication?
No. We connected to Smasher Studio — AI Fashion Design without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Smasher Studio — AI Fashion Design MCP server still maintained?
Smasher Studio — AI Fashion Design is still listed as active in the MCP registry. We last reached this channel on 27 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.