Verfy

MCP servers / @bytebase/dbhub

MCP tool changes

@bytebase/dbhub

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

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

1.6.0 → 1.6.1

patch release, 11 November 2026

No tool definition changed.

1.5.1 → 1.6.0

minor release, 7 November 2026

No tool definition changed.

1.5.0 → 1.5.1

patch release, 3 November 2026

No tool definition changed.

1.4.0 → 1.5.0

minor release, 9 October 2026

No tool definition changed.

1.3.1 → 1.4.0

minor release, 28 September 2026

No tool definition changed.

Releases tried: 1.3.1 (2026-09-21); 1.4.0 (2026-09-28); 1.5.0 (2026-10-09); 1.5.1 (2026-11-03); 1.6.0 (2026-11-07); 1.6.1 (2026-11-11).

Tools in 1.6.1

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 1.6.1
ToolDescriptionPin
execute_sqlExecute SQL queries on the sqlite database3d2d8aa9f0bb
search_objectsSearch and list database objects on the sqlite database457147f2b6b8

Lock these tools

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