0★ stars
0weekly installs
1 month agolast release
Provenancewhere it came from, and what was verified
✦
First-party publisher
Published by the owner of wearmu.com, who proved control of the domain through the official MCP registry.
Verified owner: wearmu.com ↗com.wearmu/mu
Permissions & trustwhat this server can touch before you run it
◆
Network access
Connects to a hosted remote endpoint.
About
Official AI-native print-on-demand MCP — say it, AI designs it, sell 40+ goods, earn royalties.
Packages & transports
remotehttps://mcp.wearmu.com/mcpHTTP
B
Quality 75/100
how much you can lean on this server
Maintenance
36/45
Completeness
28/35
Reliability
11/20
Computed from the server's own data, not a hidden formula. This measures how much you can depend on it, not how popular it is. Stars are shown separately, on purpose. How it's scored →
A
Tool definition quality 85/100
how well its 28 tools describe themselves to an agent
▸mu_register100A
Description
present and substantive
Param types
params declare a type
Param docs
params are described
Structure
required fields declared
▸mu_verify100A
Description
present and substantive
Param types
params declare a type
Param docs
params are described
Structure
required fields declared
▸mu_status100A
Description
present and substantive
Param types
no parameters
Param docs
no parameters
Structure
required fields declared
▸mu_quote93A
Description
present and substantive
Param types
params declare a type
Param docs
params are described
Structure
required fields declared
▸mu_check84B
Description
present and substantive
Param types
params declare a type
Param docs
params are described
Structure
required fields declared
▸mu_spec_draft100A
Description
present and substantive
Param types
params declare a type
Param docs
params are described
Structure
required fields declared
▸mu_rfq_create90A
Description
present and substantive
Param types
params declare a type
Param docs
params are described
Structure
required fields declared
▸mu_rfq_record89A
Description
present and substantive
Param types
params declare a type
Param docs
params are described
Structure
required fields declared
▸mu_rfq_list68C
Description
present and substantive
Param types
params declare a type
Param docs
params are described
Structure
required fields declared
▸mu_create_store100A
Description
present and substantive
Param types
params declare a type
Param docs
params are described
Structure
required fields declared
▸mu_create_product100A
Description
present and substantive
Param types
params declare a type
Param docs
params are described
Structure
required fields declared
▸mu_preview_mockup93A
Description
present and substantive
Param types
params declare a type
Param docs
params are described
Structure
required fields declared
▸mu_affiliate100A
Description
present and substantive
Param types
no parameters
Param docs
no parameters
Structure
required fields declared
▸mu_list_mine100A
Description
present and substantive
Param types
no parameters
Param docs
no parameters
Structure
required fields declared
▸mu_sales100A
Description
present and substantive
Param types
no parameters
Param docs
no parameters
Structure
required fields declared
▸mu_upload_design100A
Description
present and substantive
Param types
params declare a type
Param docs
params are described
Structure
required fields declared
▸mu_retire_product100A
Description
present and substantive
Param types
params declare a type
Param docs
params are described
Structure
required fields declared
▸mu_update_product100A
Description
present and substantive
Param types
params declare a type
Param docs
params are described
Structure
required fields declared
▸mu_submit_feedback100A
Description
present and substantive
Param types
params declare a type
Param docs
params are described
Structure
required fields declared
▸mu_ship_orders93A
Description
present and substantive
Param types
params declare a type
Param docs
params are described
Structure
required fields declared
▸mu_ship_mark100A
Description
present and substantive
Param types
params declare a type
Param docs
params are described
Structure
required fields declared
▸mu_ship_csv93A
Description
present and substantive
Param types
params declare a type
Param docs
params are described
Structure
required fields declared
▸mu_gi_logos100A
Description
present and substantive
Param types
no parameters
Param docs
no parameters
Structure
required fields declared
▸mu_gi_logo_set100A
Description
present and substantive
Param types
params declare a type
Param docs
params are described
Structure
required fields declared
▸mu_ship_import_tracking100A
Description
present and substantive
Param types
params declare a type
Param docs
params are described
Structure
required fields declared
▸mu_ship_order100A
Description
present and substantive
Param types
params declare a type
Param docs
params are described
Structure
required fields declared
▸mu_gi_request_logos100A
Description
present and substantive
Param types
no parameters
Param docs
no parameters
Structure
required fields declared
▸mu_gi_techpack100A
Description
present and substantive
Param types
no parameters
Param docs
no parameters
Structure
required fields declared
Structural, not an LLM's opinion: each check is a fact about the tool's schema, so it's reproducible. One weak tool drags the score (60% average, 40% worst). How it's scored →
For the maintainer
Raise this grade
up to +25 on qualityOwn this server? Here's exactly what to change, biggest wins first. Every number below is a fixed point value, so you can see what each edit is worth before you make it.
+9
Keep it activeMaintenance
Push to the repo or cut a release. Activity within the last 30 days earns the full 45.
+9
Collect working reviewsReliability
With no reviews this sits at a neutral 11. Reviews reporting it works push it toward the full 20.
+7
Declare a licenseCompleteness
Add an SPDX license (like MIT or Apache-2.0) to the repo so it's detected.
Tool definitions to fix first
mu_rfq_list68/100
- 3 of 3 params have no description: `kind`, `status`, `supplier_id`. Describe each one.
- No `required` array. Declare which params are mandatory so an agent knows what it must provide.
mu_check84/100
- 7 of 11 params have no description: `colors`, `material`, `placement`, `dimensions`, +3 more. Describe each one.
mu_rfq_record89/100
- 3 of 7 params have no description: `moq`, `note`, `lead_time_days`. Describe each one.
mu_rfq_create90/100
- 1 of 8 params have no description: `note`. Describe each one.
- No `required` array. Declare which params are mandatory so an agent knows what it must provide.
Already earned (3) ▾Already earned (3) ▴
✓Describe what it does+11
✓Give an install path+11
✓Link the source+6
These are structural checks, so the fixes are exact. See the full formula →
Add a badge to your README
[](https://socketcat.com/servers/com.wearmu/mu)Shows your live quality grade and links back here. It updates itself as the grade changes.
Reviews
Sign in to leave a reviewNo reviews yet. Be the first to say whether it worked.
Add to your client
Pick your client, copy, paste into its config. That's the whole setup.
~/.claude/claude_desktop_config.json
{
"mcpServers": {
"mu": {
"command": "npx",
"args": [
"-y",
"mu"
]
}
}
}▸ Try itlive against mcp.wearmu.com
This server has a hosted endpoint, so we can connect and list its actual tools right here. Nothing runs on your machine.