Verfy

MCP servers / @magicuidesign/mcp

MCP tool changes

@magicuidesign/mcp

2 of its last 4 updates changed what the agent reads: 0 tool descriptions rewritten, up to 2.1.0.

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

2.0.0 → 2.1.0

minor release, 2 November 2026

getRegistryItem: title, annotations or output schema changed

listRegistryItems: title, annotations or output schema changed

searchRegistryItems: title, annotations or output schema changed

1.0.6 → 2.0.0

major release, 9 March 2026

Added: getRegistryItem, listRegistryItems, searchRegistryItems

Removed: getAnimations, getBackgrounds, getButtons, getComponents, getDeviceMocks, getSpecialEffects, getTextAnimations, getUIComponents

1.0.5 → 1.0.6

patch release, 17 April 2025

No tool definition changed.

1.0.4 → 1.0.5

patch release, 16 April 2025

No tool definition changed.

Releases tried: 1.0.3 (2025-04-16), did not start; 1.0.4 (2025-04-16); 1.0.5 (2025-04-16); 1.0.6 (2025-04-17); 2.0.0 (2026-03-09); 2.1.0 (2026-11-02).

Tools in 2.1.0

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 2.1.0
ToolDescriptionPin
listRegistryItemsLists Magic UI registry items with optional filtering by kind, query, and limit.3b736b328d62
getRegistryItemGets detailed information for a single Magic UI registry item.95f09c890c26
searchRegistryItemsSearches Magic UI registry items by keyword or use case.d0a4a27087d2

Lock these tools

Pin what @magicuidesign/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.