MCP servers / @gongrzhe/server-gmail-autoauth-mcp
@gongrzhe/server-gmail-autoauth-mcp
None of the releases we tried started without a real key or a running service, so there is nothing to compare.
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
Releases tried: 1.1.6 (2025-04-06), did not start; 1.1.7 (2025-04-10), did not start; 1.1.8 (2025-04-16), did not start; 1.1.9 (2025-05-13), did not start; 1.1.10 (2025-06-19), did not start; 1.1.11 (2025-08-06), did not start.
Lock these tools
Pin what @gongrzhe/server-gmail-autoauth-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@v1Maintain this server? Run the same check on your releases and add the Locked by Verfy badge to your README.