Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

com.wearmu/mu

REMOTE · MCP.WEARMU.COM · SCANNED SEP 25

Official AI-native print-on-demand MCP — say it, AI designs it, sell 40+ goods, earn royalties.

Available components

0 this week 77 Trust /100
Trust breakdown (7 categories)

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 Security57
Transport & Reachability100
Schema Quality & AI Usability70
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 5468 tokens (~176/item across 31 items; 31 tools + 0 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 Management100
  • No destabilizing schema changes in the last 30 days.Pass
Tool Coverage94
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 83% of tool parameters carry a description.Partial
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 31 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 31 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
Install

How do I install the com.wearmu/mu MCP server?

com.wearmu/mu is a hosted endpoint at https://mcp.wearmu.com/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 · mcp.wearmu.com

# add to Claude Code
claude mcp add --transport http com-wearmu-mu 'https://mcp.wearmu.com/mcp'
// .cursor/mcp.json
{
  "mcpServers": {
    "com-wearmu-mu": {
      "url": "https://mcp.wearmu.com/mcp"
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "com-wearmu-mu": {
      "type": "http",
      "url": "https://mcp.wearmu.com/mcp"
    }
  }
}
# ~/.codex/config.toml
[mcp_servers.com-wearmu-mu]
url = "https://mcp.wearmu.com/mcp"
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-wearmu-mu": {
      "type": "remote",
      "url": "https://mcp.wearmu.com/mcp",
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add com-wearmu-mu --url 'https://mcp.wearmu.com/mcp' --transport streamable-http
# ~/.hermes/config.yaml
mcp_servers:
  com-wearmu-mu:
    url: "https://mcp.wearmu.com/mcp"
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "com-wearmu-mu": {
      "Transport": "http",
      "Url": "https://mcp.wearmu.com/mcp"
    }
  }
}
# add to Vellum
assistant mcp add com-wearmu-mu -t streamable-http -u 'https://mcp.wearmu.com/mcp'
// mcp.json
{
  "mcpServers": {
    "com-wearmu-mu": {
      "type": "http",
      "url": "https://mcp.wearmu.com/mcp"
    }
  }
}

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

Changelog

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.

  • 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
  • 26 Aug 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
  • 25 Aug 26 0
    • Stability: 0.97 → pass security
  • 23 Aug 26 0
    • New tool “mu_order_advance” functional
    • New tool “mu_order_create” functional
    • New tool “mu_order_status” functional
  • 11 Aug 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
  • 31 Jul 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
  • 30 Jul 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
  • 27 Jul 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
Diagnostics

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 25 Sept 2026 · Probed https://mcp.wearmu.com/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=mcp.wearmu.com CN=YE2,O=Let's Encrypt,C=US 29 Jul 2026 27 Oct 2026 ECDSA 256 ECDSA-SHA384 6813a32a8bb85d7e200b3b023d503730d89
SANs: mcp.wearmu.com
CN=YE2,O=Let's Encrypt,C=US (CA) CN=Root YE,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 ECDSA 384 ECDSA-SHA384 4df3b15dd6c0784c507cd37b58e6f115
CN=Root YE,O=ISRG,C=US (CA) CN=ISRG Root X2,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 ECDSA-SHA384 872165fc34b6e5fba8add5b3705fb53a
CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 SHA256-RSA 6c8f1dc727c7117f7baf853ac980f9cd

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of mcp.wearmu.com. — Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
com. present 19718 13 Verified
wearmu.com. 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

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://mcp.wearmu.com/mcp Verified 200
http (plaintext) http://mcp.wearmu.com/mcp HTTPS enforced 301 https://mcp.wearmu.com/mcp
MCP tools · 31 exposed · ~5,468 tokens

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 →

Tool Tokens
mu_affiliate ~100

Get your personal MU affiliate (referral) link + stats. Share the `link`; when someone buys any MU product within 30 days of clicking it, you earn a commission as MU store credit (default 10% of the sale). You can also append the returned `ref_param` to any product URL. Returns clicks, sales (uses), earned_jpy and your mu_credit_balance. Requires `Authorization: Bearer <api_key>`.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

mu_check ~306

Ask the MU requirements engine whether a planned make satisfies its requirements: product spec floor (required attributes per kind), legal/compliance flags (e.g. JP 家庭用品品質表示法 / 技適 / 食品衛生法), and supplier order terms (MOQ, accepted input format, material constraints). Pass `kind` (required) + optional `region` (e.g. jp), `supplier_id`, and either `spec` (a JSON string) or individual attributes (material/dimensions/colors/print_method/placement/qty/size_range/embroidery_spec). Returns { ok, kind, report: { ok, gaps[], actions[] } }. Read-only, no API key. Use before mu_create_product or mu_rfq_create.

NameTypeReqDescription
colorsstring––
dimensionsstring––
embroidery_specstring––
kindstringyesProduct kind (e.g. gi / tote / rashguard_ls).
materialstring––
placementstring––
print_methodstring––
regionstring–Region, e.g. jp/us. Triggers region-specific legal requirements.
size_rangestring––
specstring–Spec as a JSON string, e.g. {"material":"8oz canvas","dimensions":"A4"}.
supplier_idstring–Supplier id (e.g. isami_gi) to also check its order terms.

No output schema declared.

No examples provided.

mu_create_product ~995

Create a product in one of your MU stores. Provide the artwork EITHER as `design_url` (an absolute https URL to ready-made art) OR as `ai_prompt` (a text brief — MU generates the artwork for you and deducts the AI-gen cost from your mu_credits balance; see mu_status → limits.ai_gen for cost_jpy and whether it is enabled). Pass exactly one of the two. `kind` must be one of: tee, tee_white, rashguard_ls, rashguard_black, hoodie, crewneck, sticker, mug, tote, tank, cap, phone_case, long_sleeve_tee, shorts, beanie, leggings, joggers, apron, canvas, metal_print, pillow, blanket, coaster, placemat, journal, mug_black, wine_glass, towel, bottle, mouse_pad, laptop_sleeve, poster, nfc_coin, device, event_ticket, song, zine, video, karaoke_ticket, house, socks, drawstring_bag, beach_towel, fanny_pack, bucket_hat, kids_tee, backpack, flag, printful_custom. `phone_case` is an iPhone tough case (Printful) — the buyer picks their iPhone model (11〜17, all sizes) inside checkout, so you create ONE product and it ships to whichever model they choose. . Two digital kinds need an extra field: `event_ticket` (a sellable event ticket — pass `capacity` for the seat limit; on purchase the buyer is emailed a QR that opens a VALID ticket page; no shipping) and `song` (a sellable track — pass `audio_url`, the https link to the audio; on purchase the buyer is emailed a private listen/download link; no shipping). Other digital kinds (`zine` PDF, `video`, `karaoke_ticket`) and manual-fulfilment kinds (`poster`, `tee_white`, `nfc_coin`, `device`, `house`) all take the same `design_url`/`ai_prompt` artwork; the buyer gets a download/redemption link (digital) or the operator ships/builds it (manual). Products go live immediately for trusted owners unless the risk gate trips, otherwise they wait for MA-council review — ALWAYS report the `status` field from the response, do not assume. Requires `Authorization: Bearer <api_key>`.

NameTypeReqDescription
ai_promptstring–Text brief for MU to generate the artwork (<=600 chars). Costs mu_credits (see mu_status → limits.ai_gen). Provide this OR design_url (not both).
audio_urlstring–song only: absolute https URL of the audio file delivered to the buyer on purchase.
capacityinteger–event_ticket only: seat limit (定員). Once sold out, checkout is blocked. Omit = unlimited.
descriptionstringyesProduct description.
design_urlstring–Absolute https URL to ready-made design artwork (ticket art / song cover for digital kinds). Provide this OR ai_prompt (not both).
kindstringyesProduct kind. One of: tee, tee_white, rashguard_ls, rashguard_black, hoodie, crewneck, sticker, mug, tote, tank, cap, phone_case, long_sleeve_tee, shorts, beanie, leggings, joggers, apron, canvas, me…
labelstringyesProduct label / title.
positionobject–Optional print placement — front-print DTG apparel only (tee / tee_white / hoodie / crewneck / tank / long_sleeve_tee). The preview mockup AND the real print order use the same resolved box (WYSIWYG)…
price_jpyinteger–Optional retail price in JPY. Must respect the kind's price_floor_jpy (see mu_status).
printful_product_idinteger–printful_custom only: the Printful catalog product id (from the Printful catalog API). MU makes ANY of Printful's ~500 catalog products this way — placement, fulfillment route and price floor are res…
printful_variant_idinteger–printful_custom only: the Printful variant id (size/color) for the chosen product.
storestringyesSlug of the store to add the product to.

No output schema declared.

No examples provided.

mu_create_store ~137

Open a new MU store (a branded storefront) under your agent account. Returns the store slug and public store_url. Requires `Authorization: Bearer <api_key>`.

NameTypeReqDescription
color_primarystring–Optional primary brand color, hex e.g. "#0a4d9c".
emojistring–Optional emoji used as the store mark.
namestringyesDisplay name of the store.
slugstringyesURL slug for the store, e.g. "my-dojo" → wearmu.com/my-dojo.
taglinestring–Optional short tagline shown on the storefront.

No output schema declared.

No examples provided.

mu_gi_logo_set ~196

Update one gi sponsor placement (by slot from mu_gi_logos) — swap its logo_url, set its status (ok|low|request|missing) and/or add a note (e.g. where the vector was requested). Owner-only.

NameTypeReqDescription
consentstring–Written permission to embroider this brand on the gi. yes=have written OK; requested=asked, not yet granted; no=declined. Only consent=yes AND status=ok is print-ready — set yes ONLY when you actuall…
logo_urlstring–New absolute https URL of the hi-res / vector logo.
notestring–Free note, e.g. 'vector requested from pr@…'.
slotstringyesPlacement slot, e.g. "lsleeve-kagi" (from mu_gi_logos).
statusstring–New logo-file status.

No output schema declared.

No examples provided.

mu_gi_logos ~119

List the MU × JiuFlow sponsored gi's 17 sponsor placements with each logo's slot, brand, position, finished size, thread color, logo file/url, status (ok=hi-res | low=low-res | request=not collected | missing), and consent (yes=written permission to embroider on apparel | requested | no). ready_to_print is true ONLY when status=ok AND consent=yes — anything else must NOT be sent to ISAMI (using a brand's mark without permission is trademark misuse). Owner-only.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

mu_gi_request_logos ~84

For every gi sponsor whose consent is not yes, generate a ready-to-send draft asking for (1) written permission to embroider their mark on the gi and (2) the vector logo. Does NOT send (outbound mail is a human gate). When a brand grants permission, record it with mu_gi_logo_set consent:yes. Owner-only.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

mu_gi_techpack ~65

Return the MU × JiuFlow gi's public page and lifestyle/mockup image URLs (front/back/crest/QR). The dimensioned tech-pack PDF lives in the repo (docs/gi-isami-2026-05-12/). Owner-only.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

mu_list_mine ~61

List every product you have created across your MU stores: sku, store, label, kind, retail_price_jpy, status (review/live/retired/…), design_file and pdp_url. Requires `Authorization: Bearer <api_key>`.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

mu_order_advance ~95

Move an order one step in the lifecycle: ordered→production→shipped→completed, or ordered→refund_pending (lot expiry / human judgment), refund_pending→refunded (human recorded refund). Backward/skipped transitions are rejected. Production is blocked while lot_lock=true until the lot fills.

NameTypeReqDescription
idintegeryesOrder id.
notestring––
statusstring–New status.

No output schema declared.

No examples provided.

mu_order_create ~239

Open a purchase order (受注) from a received RFQ (pass `rfq_id`) or directly with `supplier_id`+`kind`. If the supplier's MOQ is unmet, the order is lot-locked (lot_lock=true) until the lot (same supplier+kind) fills. Fills are public: any agent can contribute to a lot. If the deadline (30d) passes before fill, the order flips to refund_pending and is listed as an auto-refund candidate (human executes the refund). Status flow: ordered → production → shipped → completed, with refund_pending → refunded. Orders are scoped to your account (admin sees all).

NameTypeReqDescription
kindstring–Product kind (if rfq_id omitted).
notestring––
qtyinteger–Quantity (default: from rfq, else 1).
rfq_idinteger–RFQ id (must be status='received').
supplier_idstring–Supplier id (if rfq_id omitted).
unit_jpyinteger–Unit price (from rfq's quoted_unit_jpy if omitted).

No output schema declared.

No examples provided.

mu_order_status ~82

List purchase orders with optional filters by `supplier_id`, `status`, and `refund=1` to show only auto-refund candidates (refund_pending). Orders are scoped to your account (admin sees all).

NameTypeReqDescription
refundboolean–If true, show only auto-refund candidates.
statusstring––
supplier_idstring––

No output schema declared.

No examples provided.

mu_preview_mockup ~319

See the mockup BEFORE creating any product — nothing is created or sold, and it costs no credits. Renders the design on the real garment (Printful) when the kind supports it (source: "printful"), otherwise a clean MU product card (source: "card"), and returns a durable preview image URL. Optionally pass `position` (front-print DTG apparel only: tee / tee_white / hoodie / crewneck / tank / long_sleeve_tee) to preview a custom print placement — passing the SAME position to mu_create_product prints exactly what you previewed (WYSIWYG). Usually answers in 10-45s; if it returns status="processing", call this tool again with the returned `preview_id` to keep waiting. Rate limit: 30 previews/hour. Requires `Authorization: Bearer <api_key>`.

NameTypeReqDescription
design_urlstring–Absolute https URL of the design artwork (required unless preview_id is set). Use mu_upload_design first for local images.
kindstring–Product kind to preview on (required unless preview_id is set).
positionobject–Optional print placement — front-print DTG apparel only (tee / tee_white / hoodie / crewneck / tank / long_sleeve_tee). The preview mockup AND the real print order use the same resolved box (WYSIWYG)…
preview_idstring–Continue waiting on an earlier preview that returned status="processing".

No output schema declared.

No examples provided.

mu_quote ~530

Ask the MU manufacturing router how a thing could be MADE before you create a product: which supplier(s) can make it, the est. unit price (JPY), MOQ, lead time, fulfillment route, and whether it ships auto (POD, zero-inventory, order now) or needs a quote (RFQ to a factory). Pass `kind` (a known POD kind like tee/hoodie/rashguard_ls, OR a non-POD kind like `gi`/`loopwheel_sweat`/`seamless_knit`/`rashguard_premium`) OR a free-text `description` (e.g. "道着 for a dojo", "a seamless knit sweater") and the router infers the kind. Optional `qty`, `region` (e.g. jp/us), `budget` (JPY/unit). Read-only — creates nothing. No API key required. Options are ranked: buyable-now (auto + in budget) first. If an option's mode is `auto`, follow up with mu_create_product; if `quote`, it needs a human RFQ.

NameTypeReqDescription
budgetinteger–Target budget per unit in JPY. Flags options as within_budget / not.
descriptionstring–Free-text description of what to make (used to infer kind when `kind` is omitted).
kindstring–Product kind. POD kinds: tee, tee_white, rashguard_ls, rashguard_black, hoodie, crewneck, sticker, mug, tote, tank, cap, phone_case, long_sleeve_tee, shorts, beanie, leggings, joggers, apron, canvas,…
qtyinteger–Quantity (default 1). Used to check each supplier's MOQ.
regionstring–Ship-to / make region, e.g. "jp" or "us". Prefers region-matching suppliers.

No output schema declared.

No examples provided.

mu_register ~84

Start MU agent registration. Emails a 6-digit verification code to the address. After receiving the code, call mu_verify with {email, code} to obtain your api_key. No authentication required for this call.

NameTypeReqDescription
agent_namestring–Optional human-readable agent name.
emailstringyesEmail address to register; the 6-digit code is sent here.

No output schema declared.

No examples provided.

mu_retire_product ~64

Retire one of your products (sets status=retired, removes it from the storefront). Owner-only. Requires `Authorization: Bearer <api_key>`.

NameTypeReqDescription
skustringyesSKU of the product to retire (must belong to one of your stores).

No output schema declared.

No examples provided.

mu_rfq_create ~279

Open a quote request (RFQ) to a non-POD supplier (gi/loopwheel/seamless-knit/premium AOP). Generates a ready-to-send draft (subject/body) and saves it status='drafted'. Does NOT send — outbound mail/PO is a human gate. Pass `supplier_id` OR `kind`/`description` (the router resolves a quote-mode supplier), `qty`, and optionally `spec_id` (from mu_spec_draft), `product_ref`, `spec_pack_url`, `note`. RFQs are scoped to your account (admin sees all).

NameTypeReqDescription
descriptionstring–Free text to infer kind when kind/supplier omitted.
kindstring–Product kind (e.g. gi/seamless_knit).
notestring––
product_refstring–Reference SKU or /make ref.
qtyinteger–Quantity (default 1).
spec_idstring–Spec id from mu_spec_draft to attach.
spec_pack_urlstring–URL of a techpack/mockup pack for the supplier.
supplier_idstring–Supplier id (e.g. isami_gi/heritage_loopwheel/shima_seamless/contrado_uk). Omit to resolve from kind/description.

No output schema declared.

No examples provided.

mu_rfq_list ~75

List quote requests (RFQs) with optional filters by `supplier_id`, `kind`, `status` (drafted/sent/received/expired). RFQs are scoped to your account (admin sees all).

NameTypeReqDescription
kindstring––
statusstring––
supplier_idstring––

No output schema declared.

No examples provided.

mu_rfq_record ~203

After a factory replies, record the quote against an RFQ: set `status` (sent/received/expired) and, for received, `quoted_unit_jpy` (required) plus `moq`, `lead_time_days`, `valid_until` (ISO date). A received, still-valid quote is reflected back into mu_quote's est_unit_jpy (display only). RFQs are scoped to your account (admin sees all).

NameTypeReqDescription
idintegeryesRFQ id (from mu_rfq_create / mu_rfq_list).
lead_time_daysinteger––
moqinteger––
notestring––
quoted_unit_jpyinteger–Quoted unit price in JPY (required when status=received).
statusstring–New status. 'received' requires quoted_unit_jpy.
valid_untilstring–Quote validity end date, ISO (YYYY-MM-DD).

No output schema declared.

No examples provided.

mu_sales ~56

Get sales for your MU stores: per-store and total order_count + revenue_jpy, plus the 50 most recent orders (sku, amount_jpy, created_at, status). Requires `Authorization: Bearer <api_key>`.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

mu_ship_csv ~139

Generate a 送り状 CSV for all un-shipped orders, formatted for import into ヤマト B2クラウド (courier=yamato) or 佐川 e飛伝 (courier=sagawa). No carrier API/contract needed — import the CSV to request pickup. Returns {filename, csv_utf8 (for reading), csv_shift_jis_base64 (decode this for the actual import — B2クラウド/e飛伝 expect Shift_JIS)}. First time, register the column layout in B2クラウド. Owner-only.

NameTypeReqDescription
courierstring–Courier CSV format (default yamato).

No output schema declared.

No examples provided.

mu_ship_import_tracking ~114

Paste the CSV that B2クラウド / e飛伝 produced AFTER issuing labels (it contains your お客様管理番号 MU-{id} plus the assigned 送り状番号). Matches each MU-{id} to the order and sets tracking + marks it shipped, in bulk. The natural counterpart to mu_ship_csv. Owner-only.

NameTypeReqDescription
courierstring–Courier (default yamato).
csvstringyesThe full CSV text exported from B2クラウド/e飛伝 after issuing labels.

No output schema declared.

No examples provided.

mu_ship_mark ~153

Advance a physical order's ship_status and (when shipping) record the courier + tracking number. Owner-only. status must be one of pending|in_production|shipped|delivered.

NameTypeReqDescription
courierstring–Courier, e.g. yamato | sagawa (when status=shipped).
idnumberyescatalog_orders.id of the order (from mu_ship_orders).
notifyboolean–When status=shipped, email the customer a shipped + tracking notice (default false). Transactional shipping mail to the buyer of THIS order.
statusstringyesNew shipping status.
trackingstring–Tracking / 送り状 number (when status=shipped).

No output schema declared.

No examples provided.

mu_ship_order ~66

Fetch a single physical order by id with its status, courier and tracking. Address/phone are masked unless reveal=true. Owner-only.

NameTypeReqDescription
idnumberyescatalog_orders.id of the order.
revealboolean–Show full address/phone (default false = masked).

No output schema declared.

No examples provided.

mu_ship_orders ~124

List physical (address-bearing) orders for the factory shipping console with their ship_status (pending|in_production|shipped|delivered), courier and tracking. Owner-only: requires the store owner's `Authorization: Bearer <api_key>` (403 otherwise).

NameTypeReqDescription
allboolean–Include delivered orders too (default false = active only).
revealboolean–Show full address/phone. Default false = masked (city + last-4) so customer PII stays out of the chat log; set true only when you actually need the full address.

No output schema declared.

No examples provided.

mu_spec_draft ~134

Turn a natural-language request into a structured manufacturing spec (kind, material, dimensions, colors, print_method, placement, qty, region). Missing required attributes come back as `missing` with a follow-up `next_question` to fill them in. Feed the resulting spec_id into mu_rfq_create. Requires an API key (register/verify first) — uses a small amount of AI budget per call.

NameTypeReqDescription
promptstringyesWhat to make, in free text. E.g. 「黒の帆布トート、ロゴ刺繍、A4が入る、200枚」.

No output schema declared.

No examples provided.

mu_status ~56

Get the authenticated agent's profile: email, mu_credits_balance, MA-council flag, their stores, and limits (allowed product kinds with price floors + per-hour caps). Requires `Authorization: Bearer <api_key>`.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

mu_submit_feedback ~167

Found a bug, or have an idea to make MU better? File it here. Use this when something on the platform/API misbehaves, a product looks wrong, or you want to request a feature. It lands in the MA-council triage queue. Requires `Authorization: Bearer <api_key>`.

NameTypeReqDescription
categorystringyesbug = something is broken; feature = new capability; improvement = make existing better.
descriptionstringyesWhat happened / what you want. Steps to reproduce for bugs. (<=2000 chars)
severitystring–Optional (bugs): how bad is it?
skustring–Optional: the SKU this feedback is about.
titlestringyesShort one-line summary (<=200 chars).

No output schema declared.

No examples provided.

mu_update_product ~243

Update one of your products. Allowed ONLY while the product is in 'review' or 'retired' (never a live product). You may change label, description, price_jpy (clamped up to the kind's floor), design_url and position (print placement; re-renders the mockup). Printful ids can never change. Owner-only. Requires `Authorization: Bearer <api_key>`.

NameTypeReqDescription
descriptionstring–New product description.
design_urlstring–New absolute https URL to the design artwork.
labelstring–New product label / title.
positionobject–Optional print placement — front-print DTG apparel only (tee / tee_white / hoodie / crewneck / tank / long_sleeve_tee). The preview mockup AND the real print order use the same resolved box (WYSIWYG)…
price_jpyinteger–New retail price in JPY (clamped up to the kind's price_floor_jpy).
skustringyesSKU of the product to update (must belong to one of your stores).

No output schema declared.

No examples provided.

mu_upload_design ~102

Upload a PNG design (base64-encoded, <=3MB decoded) and receive a durable https url. Pass that url as `design_url` to mu_create_product. Requires `Authorization: Bearer <api_key>`.

NameTypeReqDescription
data_base64stringyesBase64-encoded PNG bytes (a leading data:image/png;base64, prefix is OK). Max ~3MB decoded.
filenamestring–Optional original filename (informational only).

No output schema declared.

No examples provided.

mu_verify ~81

Verify the 6-digit code emailed by mu_register and receive your permanent api_key. Use that key as `Authorization: Bearer <api_key>` on all subsequent MU tool calls. No authentication required for this call.

NameTypeReqDescription
codestringyesThe 6-digit code from the verification email.
emailstringyesThe email used in mu_register.

No output schema declared.

No examples provided.

Common questions

What is the com.wearmu/mu MCP server?

com.wearmu/mu is an MCP server listed in the public MCP registry as com.wearmu/mu. Official AI-native print-on-demand MCP, say it, AI designs it, sell 40+ goods, earn royalties. This page covers its hosted endpoint (https://mcp.wearmu.com/mcp).

Is the com.wearmu/mu MCP server safe to use?

com.wearmu/mu scores 77 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 com.wearmu/mu MCP server expose?

com.wearmu/mu exposes 31 tools: mu_register, mu_verify, mu_status, mu_quote, mu_check, and 26 more. Their descriptions and schemas cost roughly 5,468 tokens of context every time the server is loaded.

Does the com.wearmu/mu MCP server require authentication?

No. We connected to com.wearmu/mu without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the com.wearmu/mu MCP server still maintained?

com.wearmu/mu is still listed as active in the MCP registry. We last reached this channel on 25 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.