1.17.0 → 1.18.0
minor release, 11 November 2026crt-usrs-lst-input: input schema changed
upd-usr: input schema changed
upload-file: input schema changed
MCP servers / @ivotoby/openapi-mcp-server
1 of its last 5 updates changed what the agent reads: 0 tool descriptions rewritten, up to 1.18.0.
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.
crt-usrs-lst-input: input schema changed
upd-usr: input schema changed
upload-file: input schema changed
No tool definition changed.
No tool definition changed.
No tool definition changed.
No tool definition changed.
Releases tried: 1.14.1 (2026-06-14); 1.15.0 (2026-06-14); 1.16.0 (2026-06-14); 1.16.1 (2026-06-15); 1.17.0 (2026-11-06); 1.18.0 (2026-11-11).
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 |
|---|---|---|
| upd-pet | Update an existing pet by Id. | c61d586136dc |
| add-pet | Add a new pet to the store. | 4aafa640d5b1 |
| find-pets-by-status | Multiple status values can be provided with comma separated strings. | 03a9ce079b87 |
| find-pets-by-tags | Multiple tags can be provided with comma separated strings. Use tag1, tag2, tag3 for testing. | 587e40ac77b3 |
| get-pet-by-id | Returns a single pet. | 28dd874370c5 |
| upd-pet-form | Updates a pet resource based on the form data. | 92f98471bc22 |
| del-pet | Delete a pet. | a53f2eed3ca4 |
| upload-file | Upload image of the pet. | 402ed31b745d |
| get-inventory | Returns a map of status codes to quantities. | c636b3b89dda |
| place-order | Place a new order in the store. | 0df8979837fe |
| get-order-by-id | For valid response try integer IDs with value <= 5 or > 10. Other values will generate exceptions. | e2ce51ccd92d |
| del-order | For valid response try integer IDs with value < 1000. Anything above 1000 or non-integers will generate API errors. | ad469a2bf22e |
| crt-usr | This can only be done by the logged in user. | a1c408678fd6 |
| crt-usrs-lst-input | Creates list of users with given input array. | d3d8ec5d14df |
| login-usr | Log into the system. | f99371dec0bf |
| logout-usr | Log user out of the system. | c5dff645eee0 |
| get-usr-by-name | Get user detail based on username. | 43e7ebe396dd |
| upd-usr | This can only be done by the logged in user. | b8e3d62de174 |
| del-usr | This can only be done by the logged in user. | 113b891ecde7 |
Pin what @ivotoby/openapi-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.