# com.wearmu/mu (remote · mcp.wearmu.com)

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

- Trust score: 64/100 (medium)
- Change this week: +4
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-08-03

## Components

- remote · `mcp.wearmu.com`: 64/100 (this document), [markdown](https://verifymcp.io/servers/com-wearmu-mu/mcp.md), [page](https://verifymcp.io/servers/com-wearmu-mu/mcp)

## Channel facts

- Endpoint: `https://mcp.wearmu.com/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.2.0`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-08-03.

- **Endpoint Security**: 57/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - 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.
  - HTTPS is enforced; there's no plaintext access path.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 65/100
  - AI-judged instruction clarity (excellent).
  - 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.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 27/100
  - Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 95/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 85% of tool parameters carry a description.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### Claude

```bash
claude mcp add --transport http com-wearmu-mu https://mcp.wearmu.com/mcp
```

### Codex

```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
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add com-wearmu-mu --url https://mcp.wearmu.com/mcp --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  com-wearmu-mu:
    url: "https://mcp.wearmu.com/mcp"
```

### Other

```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 recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-08-02 (score 64, +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.

### 2026-07-31 (score 63, +1)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-30 (score 62, 0)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-29 (score 62, +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.

### 2026-07-28 (score 61, +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.

### 2026-07-27 (score 60, 0)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-26 (score 60)

First indexed and scored.

## MCP tools (28)

### `mu_register` (~84 tokens)

Register an MU agent

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.

Input parameters:

- `agent_name` (string): Optional human-readable agent name.
- `email` (string, required): Email address to register; the 6-digit code is sent here.

### `mu_verify` (~81 tokens)

Verify MU registration code

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.

Input parameters:

- `code` (string, required): The 6-digit code from the verification email.
- `email` (string, required): The email used in mu_register.

### `mu_status` (~56 tokens)

Get MU agent status

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>`.

### `mu_quote` (~530 tokens)

Quote how to manufacture something

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.

Input parameters:

- `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.

### `mu_check` (~306 tokens)

Check spec / legal / supplier requirements for a make

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.

Input parameters:

- `colors` (string)
- `dimensions` (string)
- `embroidery_spec` (string)
- `kind` (string, required): 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.

### `mu_spec_draft` (~134 tokens)

Draft a complete manufacturing spec from a free-text request

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.

Input parameters:

- `prompt` (string, required): What to make, in free text. E.g. 「黒の帆布トート、ロゴ刺繍、A4が入る、200枚」.

### `mu_rfq_create` (~279 tokens)

Draft an RFQ to a factory (your account; does not send)

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).

Input parameters:

- `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.

### `mu_rfq_record` (~203 tokens)

Record a supplier's RFQ reply (your account)

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).

Input parameters:

- `id` (integer, required): 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).

### `mu_rfq_list` (~75 tokens)

List RFQs (your account)

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).

Input parameters:

- `kind` (string)
- `status` (string)
- `supplier_id` (string)

### `mu_create_store` (~137 tokens)

Create an MU store

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>`.

Input parameters:

- `color_primary` (string): Optional primary brand color, hex e.g. "#0a4d9c".
- `emoji` (string): Optional emoji used as the store mark.
- `name` (string, required): Display name of the store.
- `slug` (string, required): URL slug for the store, e.g. "my-dojo" → wearmu.com/my-dojo.
- `tagline` (string): Optional short tagline shown on the storefront.

### `mu_create_product` (~995 tokens)

Create an MU product

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>`.

Input parameters:

- `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, required): 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, required): 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, required): 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, required): Slug of the store to add the product to.

### `mu_preview_mockup` (~319 tokens)

Preview a product mockup (before creating)

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>`.

Input parameters:

- `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".

### `mu_affiliate` (~100 tokens)

Get my MU affiliate link

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>`.

### `mu_list_mine` (~61 tokens)

List my MU products

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>`.

### `mu_sales` (~56 tokens)

Get my MU sales

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>`.

### `mu_upload_design` (~102 tokens)

Upload a design image

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>`.

Input parameters:

- `data_base64` (string, required): Base64-encoded PNG bytes (a leading data:image/png;base64, prefix is OK). Max ~3MB decoded.
- `filename` (string): Optional original filename (informational only).

### `mu_retire_product` (~64 tokens)

Retire an MU product

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

Input parameters:

- `sku` (string, required): SKU of the product to retire (must belong to one of your stores).

### `mu_update_product` (~243 tokens)

Update an MU product

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>`.

Input parameters:

- `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, required): SKU of the product to update (must belong to one of your stores).

### `mu_submit_feedback` (~167 tokens)

Report a bug or suggest an improvement to MU

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>`.

Input parameters:

- `category` (string, required): bug = something is broken; feature = new capability; improvement = make existing better.
- `description` (string, required): 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, required): Short one-line summary (<=200 chars).

### `mu_ship_orders` (~124 tokens)

List MU physical-shipping orders (owner only)

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).

Input parameters:

- `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.

### `mu_ship_mark` (~153 tokens)

Update an order's shipping status (owner only)

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.

Input parameters:

- `courier` (string): Courier, e.g. yamato | sagawa (when status=shipped).
- `id` (number, required): 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, required): New shipping status.
- `tracking` (string): Tracking / 送り状 number (when status=shipped).

### `mu_ship_csv` (~139 tokens)

Generate a courier shipping-label CSV (owner only)

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.

Input parameters:

- `courier` (string): Courier CSV format (default yamato).

### `mu_gi_logos` (~119 tokens)

List ISAMI gi sponsor logos + status (owner only)

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.

### `mu_gi_logo_set` (~196 tokens)

Update an ISAMI gi sponsor logo (owner only)

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.

Input parameters:

- `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, required): Placement slot, e.g. "lsleeve-kagi" (from mu_gi_logos).
- `status` (string): New logo-file status.

### `mu_ship_import_tracking` (~114 tokens)

Import courier tracking numbers from a label CSV (owner only)

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.

Input parameters:

- `courier` (string): Courier (default yamato).
- `csv` (string, required): The full CSV text exported from B2クラウド/e飛伝 after issuing labels.

### `mu_ship_order` (~66 tokens)

Get one shipping order's detail (owner only)

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

Input parameters:

- `id` (number, required): catalog_orders.id of the order.
- `reveal` (boolean): Show full address/phone (default false = masked).

### `mu_gi_request_logos` (~84 tokens)

Draft logo-permission request emails for the gi (owner only)

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.

### `mu_gi_techpack` (~65 tokens)

Get the gi techpack / mockup asset URLs (owner only)

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.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/com-wearmu-mu/mcp#diagnostics

## Score history

- 2026-08-03: 64
- 2026-08-02: 64
- 2026-08-01: 63
- 2026-07-31: 63
- 2026-07-30: 62
- 2026-07-29: 62
- 2026-07-28: 61
- 2026-07-27: 60
- 2026-07-26: 60

## Links

- Remote endpoint: https://mcp.wearmu.com/mcp
- Repository: https://github.com/yukihamada/mu-mcp
- Website: https://wearmu.com/
- Changelog RSS feed: https://verifymcp.io/servers/com-wearmu-mu/mcp/changelog.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-wearmu-mu/mcp/changelog.json
- HTML version of this page: https://verifymcp.io/servers/com-wearmu-mu/mcp