com.wearmu/mu
REMOTE · MCP.WEARMU.COM · SCANNED AUG 3
Official AI-native print-on-demand MCP — say it, AI designs it, sell 40+ goods, earn royalties.
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 →
Endpoint Security57
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 28 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- 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 Usability65
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 5052 tokens (~180/item across 28 items; 28 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 Management27
- Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage95
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 85% of tool parameters carry a description.Partial
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.
remote · mcp.wearmu.com
claude mcp add --transport http com-wearmu-mu https://mcp.wearmu.com/mcp
[mcp_servers.com-wearmu-mu] url = "https://mcp.wearmu.com/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"com-wearmu-mu": {
"type": "remote",
"url": "https://mcp.wearmu.com/mcp",
"enabled": true
}
}
} openclaw mcp add com-wearmu-mu --url https://mcp.wearmu.com/mcp --transport streamable-http
mcp_servers:
com-wearmu-mu:
url: "https://mcp.wearmu.com/mcp" {
"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.
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.
- 2 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.
- 31 Jul 26 +1
- 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
- 29 Jul 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.
- 28 Jul 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.
- 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
- 26 Jul 26 60
First indexed and scored.
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 3 Aug 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 |
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 |
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 |
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.
mu_affiliate Get my MU affiliate link ~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 Check spec / legal / supplier requirements for a make ~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.
| Name | Type | Req | Description |
|---|---|---|---|
| colors | string | — | — |
| dimensions | string | — | — |
| embroidery_spec | string | — | — |
| kind | string | yes | Product kind (e.g. gi / tote / rashguard_ls). |
| material | string | — | — |
| placement | string | — | — |
| print_method | string | — | — |
| region | string | — | Region, e.g. jp/us. Triggers region-specific legal requirements. |
| size_range | string | — | — |
| spec | string | — | Spec as a JSON string, e.g. {"material":"8oz canvas","dimensions":"A4"}. |
| supplier_id | string | — | Supplier id (e.g. isami_gi) to also check its order terms. |
No output schema declared.
No examples provided.
mu_create_product Create an MU 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>`.
| Name | Type | Req | Description |
|---|---|---|---|
| ai_prompt | string | — | 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_url | string | — | song only: absolute https URL of the audio file delivered to the buyer on purchase. |
| capacity | integer | — | event_ticket only: seat limit (定員). Once sold out, checkout is blocked. Omit = unlimited. |
| description | string | yes | Product description. |
| design_url | string | — | Absolute https URL to ready-made design artwork (ticket art / song cover for digital kinds). Provide this OR ai_prompt (not both). |
| kind | string | yes | Product 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… |
| label | string | yes | Product label / title. |
| position | object | — | 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_jpy | integer | — | Optional retail price in JPY. Must respect the kind's price_floor_jpy (see mu_status). |
| printful_product_id | integer | — | 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_id | integer | — | printful_custom only: the Printful variant id (size/color) for the chosen product. |
| store | string | yes | Slug of the store to add the product to. |
No output schema declared.
No examples provided.
mu_create_store Create an MU 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>`.
| Name | Type | Req | Description |
|---|---|---|---|
| color_primary | string | — | Optional primary brand color, hex e.g. "#0a4d9c". |
| emoji | string | — | Optional emoji used as the store mark. |
| name | string | yes | Display name of the store. |
| slug | string | yes | URL slug for the store, e.g. "my-dojo" → wearmu.com/my-dojo. |
| tagline | string | — | Optional short tagline shown on the storefront. |
No output schema declared.
No examples provided.
mu_gi_logo_set Update an ISAMI gi sponsor logo (owner only) ~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.
| Name | Type | Req | Description |
|---|---|---|---|
| consent | string | — | 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_url | string | — | New absolute https URL of the hi-res / vector logo. |
| note | string | — | Free note, e.g. 'vector requested from pr@…'. |
| slot | string | yes | Placement slot, e.g. "lsleeve-kagi" (from mu_gi_logos). |
| status | string | — | New logo-file status. |
No output schema declared.
No examples provided.
mu_gi_logos List ISAMI gi sponsor logos + status (owner only) ~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 Draft logo-permission request emails for the gi (owner only) ~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 Get the gi techpack / mockup asset URLs (owner only) ~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 List my MU products ~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_preview_mockup Preview a product mockup (before creating) ~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>`.
| Name | Type | Req | Description |
|---|---|---|---|
| design_url | string | — | Absolute https URL of the design artwork (required unless preview_id is set). Use mu_upload_design first for local images. |
| kind | string | — | Product kind to preview on (required unless preview_id is set). |
| position | object | — | 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_id | string | — | Continue waiting on an earlier preview that returned status="processing". |
No output schema declared.
No examples provided.
mu_quote Quote how to manufacture something ~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.
| Name | Type | Req | Description |
|---|---|---|---|
| budget | integer | — | Target budget per unit in JPY. Flags options as within_budget / not. |
| description | string | — | Free-text description of what to make (used to infer kind when `kind` is omitted). |
| kind | string | — | 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,… |
| qty | integer | — | Quantity (default 1). Used to check each supplier's MOQ. |
| region | string | — | Ship-to / make region, e.g. "jp" or "us". Prefers region-matching suppliers. |
No output schema declared.
No examples provided.
mu_register Register an MU agent ~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.
| Name | Type | Req | Description |
|---|---|---|---|
| agent_name | string | — | Optional human-readable agent name. |
| string | yes | Email address to register; the 6-digit code is sent here. |
No output schema declared.
No examples provided.
mu_retire_product Retire an MU product ~64
Retire one of your products (sets status=retired, removes it from the storefront). Owner-only. Requires `Authorization: Bearer <api_key>`.
| Name | Type | Req | Description |
|---|---|---|---|
| sku | string | yes | SKU of the product to retire (must belong to one of your stores). |
No output schema declared.
No examples provided.
mu_rfq_create Draft an RFQ to a factory (your account; does not send) ~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).
| Name | Type | Req | Description |
|---|---|---|---|
| description | string | — | Free text to infer kind when kind/supplier omitted. |
| kind | string | — | Product kind (e.g. gi/seamless_knit). |
| note | string | — | — |
| product_ref | string | — | Reference SKU or /make ref. |
| qty | integer | — | Quantity (default 1). |
| spec_id | string | — | Spec id from mu_spec_draft to attach. |
| spec_pack_url | string | — | URL of a techpack/mockup pack for the supplier. |
| supplier_id | string | — | 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 List RFQs (your account) ~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).
| Name | Type | Req | Description |
|---|---|---|---|
| kind | string | — | — |
| status | string | — | — |
| supplier_id | string | — | — |
No output schema declared.
No examples provided.
mu_rfq_record Record a supplier's RFQ reply (your account) ~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).
| Name | Type | Req | Description |
|---|---|---|---|
| id | integer | yes | RFQ id (from mu_rfq_create / mu_rfq_list). |
| lead_time_days | integer | — | — |
| moq | integer | — | — |
| note | string | — | — |
| quoted_unit_jpy | integer | — | Quoted unit price in JPY (required when status=received). |
| status | string | — | New status. 'received' requires quoted_unit_jpy. |
| valid_until | string | — | Quote validity end date, ISO (YYYY-MM-DD). |
No output schema declared.
No examples provided.
mu_sales Get my 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 Generate a courier shipping-label CSV (owner only) ~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.
| Name | Type | Req | Description |
|---|---|---|---|
| courier | string | — | Courier CSV format (default yamato). |
No output schema declared.
No examples provided.
mu_ship_import_tracking Import courier tracking numbers from a label CSV (owner only) ~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.
| Name | Type | Req | Description |
|---|---|---|---|
| courier | string | — | Courier (default yamato). |
| csv | string | yes | The full CSV text exported from B2クラウド/e飛伝 after issuing labels. |
No output schema declared.
No examples provided.
mu_ship_mark Update an order's shipping status (owner only) ~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.
| Name | Type | Req | Description |
|---|---|---|---|
| courier | string | — | Courier, e.g. yamato | sagawa (when status=shipped). |
| id | number | yes | catalog_orders.id of the order (from mu_ship_orders). |
| notify | boolean | — | When status=shipped, email the customer a shipped + tracking notice (default false). Transactional shipping mail to the buyer of THIS order. |
| status | string | yes | New shipping status. |
| tracking | string | — | Tracking / 送り状 number (when status=shipped). |
No output schema declared.
No examples provided.
mu_ship_order Get one shipping order's detail (owner only) ~66
Fetch a single physical order by id with its status, courier and tracking. Address/phone are masked unless reveal=true. Owner-only.
| Name | Type | Req | Description |
|---|---|---|---|
| id | number | yes | catalog_orders.id of the order. |
| reveal | boolean | — | Show full address/phone (default false = masked). |
No output schema declared.
No examples provided.
mu_ship_orders List MU physical-shipping orders (owner only) ~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).
| Name | Type | Req | Description |
|---|---|---|---|
| all | boolean | — | Include delivered orders too (default false = active only). |
| reveal | boolean | — | 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 Draft a complete manufacturing spec from a free-text request ~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.
| Name | Type | Req | Description |
|---|---|---|---|
| prompt | string | yes | What to make, in free text. E.g. 「黒の帆布トート、ロゴ刺繍、A4が入る、200枚」. |
No output schema declared.
No examples provided.
mu_status Get MU agent 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 Report a bug or suggest an improvement to MU ~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>`.
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | yes | bug = something is broken; feature = new capability; improvement = make existing better. |
| description | string | yes | What happened / what you want. Steps to reproduce for bugs. (<=2000 chars) |
| severity | string | — | Optional (bugs): how bad is it? |
| sku | string | — | Optional: the SKU this feedback is about. |
| title | string | yes | Short one-line summary (<=200 chars). |
No output schema declared.
No examples provided.
mu_update_product Update an MU 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>`.
| Name | Type | Req | Description |
|---|---|---|---|
| description | string | — | New product description. |
| design_url | string | — | New absolute https URL to the design artwork. |
| label | string | — | New product label / title. |
| position | object | — | 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_jpy | integer | — | New retail price in JPY (clamped up to the kind's price_floor_jpy). |
| sku | string | yes | SKU of the product to update (must belong to one of your stores). |
No output schema declared.
No examples provided.
mu_upload_design Upload a design image ~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>`.
| Name | Type | Req | Description |
|---|---|---|---|
| data_base64 | string | yes | Base64-encoded PNG bytes (a leading data:image/png;base64, prefix is OK). Max ~3MB decoded. |
| filename | string | — | Optional original filename (informational only). |
No output schema declared.
No examples provided.
mu_verify Verify MU registration code ~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.
| Name | Type | Req | Description |
|---|---|---|---|
| code | string | yes | The 6-digit code from the verification email. |
| string | yes | The email used in mu_register. |
No output schema declared.
No examples provided.