Verfy

MCP servers / @mui/mcp

MCP tool changes

@mui/mcp

No tool definition changed across the 6 releases that started, up to 0.1.9.

npm package · last recorded on 13 November 2026 on a clean machine with placeholder settings; only tools/list was sent. A changed description is not a vulnerability. npm page · Method and limits · this data as JSON.

Release by release

0.1.8 → 0.1.9

patch release, 30 October 2026

No tool definition changed.

0.1.7 → 0.1.8

patch release, 20 October 2026

No tool definition changed.

0.1.6 → 0.1.7

patch release, 6 October 2026

No tool definition changed.

0.1.5 → 0.1.6

patch release, 17 September 2026

No tool definition changed.

0.1.4 → 0.1.5

patch release, 4 September 2026

No tool definition changed.

Releases tried: 0.1.4 (2026-08-06); 0.1.5 (2026-09-04); 0.1.6 (2026-09-17); 0.1.7 (2026-10-06); 0.1.8 (2026-10-20); 0.1.9 (2026-10-30).

Tools in 0.1.9

The pin is the SHA-256 of the tool's name, description and input schema, as verfy.lock records it. The same pin in your lock means your agent reads this exact definition. Verfy 0.16.0 and later also pin a tool's title, annotations and output schema when the server sends them, so such a tool shows a different pin in your lock.

Tools in 0.1.9
ToolDescriptionPin
generateReactCodegenerates React + Material UI code from a natural-language prompt (optionally grounded in a Figma frame). Returns the generated files plus a short explanation. Requires `MUI_RECIPES_API_KEY`. Pass `threadId` back on subsequent calls to keep multi-turn conversations on the same chat. Pass `muiPairing` to target a specific MUI / MUI X major.64f4a06e9fa3
fetchDocsFetch documentation for one or more URLs extracted from previous tool calls responses. The URLs should be passed as an array in the "urls" argument.c983588a0c60

Lock these tools

Pin what @mui/mcp serves you today, commit the lock, and a pull request fails when a tool changes, with the text before and after. Pin the package version in your MCP config as well.

$ pip install verfy
$ verfy lock check --update   # shows each tool, then writes verfy.lock
$ git add verfy.lock
# .github/workflows/verfy.yml, after actions/checkout
- uses: verfy-dev/verfy-action@v1

Maintain this server? Run the same check on your releases and add the Locked by Verfy badge to your README.