Verfy

MCP servers / @cocal/google-calendar-mcp

MCP tool changes

@cocal/google-calendar-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: 2.6.1 (2026-03-02), did not start; 2.6.2 (2026-06-01), did not start; 2.6.3 (2026-09-02), did not start; 2.7.0 (2026-09-28), did not start; 2.8.0 (2026-10-28), did not start; 2.8.1 (2026-10-29), did not start.

Lock these tools

Pin what @cocal/google-calendar-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@v1

Maintain this server? Run the same check on your releases and add the Locked by Verfy badge to your README.