Verfy

MCP servers / @jpisnice/shadcn-ui-mcp-server

MCP tool changes

@jpisnice/shadcn-ui-mcp-server

2 of its last 5 updates changed what the agent reads: 1 tool description rewritten, up to 3.0.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 → 3.0.0

major release, 3 October 2026

apply_theme: title, annotations or output schema changed

get_block: description and input schema changed
Before (2.0.0)
Get source code for a specific shadcn/ui v4 block (e.g., calendar-01, dashboard-01)
After (3.0.0)
Get source code for a specific shadcn/ui v4 block (e.g., dashboard-01, login-02, sidebar-01)

get_component: title, annotations or output schema changed

get_component_demo: title, annotations or output schema changed

get_component_metadata: title, annotations or output schema changed

get_directory_structure: title, annotations or output schema changed

get_theme: title, annotations or output schema changed

list_blocks: title, annotations or output schema changed

list_components: title, annotations or output schema changed

list_themes: title, annotations or output schema changed

1.1.4 → 2.0.0

major release, 30 January 2026

Added: apply_theme, get_theme, list_themes

1.0.4 → 1.1.4

minor release, 23 October 2025

No tool definition changed.

1.1.0 → 1.0.4

minor release, 23 October 2025

No tool definition changed.

1.0.3 → 1.1.0

minor release, 13 August 2025

No tool definition changed.

Releases tried: 1.0.3 (2025-07-19); 1.1.0 (2025-08-13); 1.0.4 (2025-10-23); 1.1.4 (2025-10-23); 2.0.0 (2026-01-30); 3.0.0 (2026-10-03).

Tools in 3.0.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 3.0.0
ToolDescriptionPin
get_componentGet the source code for a specific shadcn/ui v4 componentc8bca1a4a1cf
get_component_demoGet demo code illustrating how a shadcn/ui v4 component should be useda72e8fd713c5
list_componentsGet all available shadcn/ui v4 componentsb5bff1dec545
get_component_metadataGet metadata for a specific shadcn/ui v4 component3326c1c69447
get_directory_structureGet the directory structure of the shadcn-ui v4 repositorya74cf9b7addc
get_blockGet source code for a specific shadcn/ui v4 block (e.g., dashboard-01, login-02, sidebar-01)b78cfe5cc871
list_blocksGet all available shadcn/ui v4 blocks with categorization693584c8eee3
apply_themeApply a TweakCN theme preset to the project4fa6ef6fe1d1
list_themesList available tweakcn themesc9d02b720aa5
get_themeGet details of a specific tweakcn theme62cdb6637fd4
prompt:build-shadcn-pageGenerate a complete shadcn/ui page using v4 components and blocks4b691723eff0
prompt:create-dashboardCreate a comprehensive dashboard using shadcn/ui v4 blocks and components8ca3143a0571
prompt:create-auth-flowGenerate authentication pages using shadcn/ui v4 login blocksab824eb7888d
prompt:optimize-shadcn-componentOptimize or enhance existing shadcn/ui components with best practices1a5a20cc030e
prompt:create-data-tableCreate advanced data tables with shadcn/ui components7e0efa2fc6d8

Lock these tools

Pin what @jpisnice/shadcn-ui-mcp-server 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.