0.7.0 → 0.7.2
patch release, 14 March 2025No tool definition changed.
MCP servers / puppeteer-mcp-server
No tool definition changed across the 3 releases that started, up to 0.7.2.
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.
No tool definition changed.
No tool definition changed.
Releases tried: 0.6.2 (2025-03-02); 0.7.0 (2025-03-02); 0.7.2 (2025-03-14).
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.
| Tool | Description | Pin |
|---|---|---|
| puppeteer_connect_active_tab | Connect to an existing Chrome instance with remote debugging enabled | 44161590579b |
| puppeteer_navigate | Navigate to a URL | 7ad7b7d5afb8 |
| puppeteer_screenshot | Take a screenshot of the current page or a specific element | 97a462616c12 |
| puppeteer_click | Click an element on the page | 52113c65fbb6 |
| puppeteer_fill | Fill out an input field | 50179ac0adff |
| puppeteer_select | Select an element on the page with Select tag | 2e006928c682 |
| puppeteer_hover | Hover an element on the page | 9bd33952c6b4 |
| puppeteer_evaluate | Execute JavaScript in the browser console | ad1319891acd |
Pin what puppeteer-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@v1Maintain this server? Run the same check on your releases and add the Locked by Verfy badge to your README.