Verfy

MCP servers / mcp-server-duckdb

MCP tool changes

mcp-server-duckdb

None of the releases we tried started without a real key or a running service, so there is nothing to compare.

PyPI 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. PyPI page · Method and limits · this data as JSON.

Release by release

Releases tried: 0.2.1 (2024-12-01), did not start; 0.2.3 (2025-01-04), did not start; 0.2.4 (2025-01-05), did not start; 1.0.0 (2025-03-18), did not start; 1.0.1 (2025-03-18), did not start; 1.1.0 (2025-05-05), did not start.

Lock these tools

Pin what mcp-server-duckdb 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.