mui-mcp
[ tools: 2 ][ checks: 11 ][ latency: 25ms ]
85/100(B)
npx -y @mui/mcp@latest
check breakdown
✓Tools exposed — Server exposed 2 tools.
• generateReactCode
• fetchDocs
✓Input schemas valid — All tools have a valid JSON-Schema input definition.
✓Input schema quality — Input schemas are well-typed and documented.
!Output schemas — 1 of 2 tool(s) have no outputSchema.
• fetchDocs
→ Optional: add outputSchema to the remaining tools for consistency.
✓Duplicate tool names — All tool names are unique.
✓Tool naming — All tool names use spec-legal characters.
Advisory (not scored): 2 name(s) aren't lower_snake_case — consistent lower_snake_case tends to help model tool-selection reliability, though mixed case, digits, underscores, hyphens, and dots are all spec-legal.
• "generateReactCode"
• "fetchDocs"
✓Descriptions — Every tool and parameter is clearly described.
!Tool annotations — Annotation coverage 0% (0/10 hint fields set).
• generateReactCode: no annotations at all
• fetchDocs: no annotations at all
→ Add annotations: title, readOnlyHint, destructiveHint, idempotentHint, openWorldHint.
→ These let clients gate risky calls and give agents/users a friendly display name — optional but valuable.
!Tool titles — 2 of 2 tool(s) have no title.
• generateReactCode: no top-level title (or annotations.title)
• fetchDocs: no top-level title (or annotations.title)
→ Declare a top-level `title` on each tool — it gives clients a friendly display name distinct from the machine-readable `name`.
→ `annotations.title` (the older location) is also accepted, but the top-level `title` field is now the spec-preferred place for it.
!Server instructions — No top-level instructions declared.
→ Declare instructions to guide agents on when/how to use this server.
→ Return a non-empty `instructions` string in your InitializeResult — most SDKs let you set this alongside serverInfo.
✓Handshake + list latency — tools/list responded in 25ms.
add the badge
Paste into your README:
[](https://scoremcp.dev/servers/mui-mcp)