The CLI checks npm for updates at startup, but only displays an update command; it does not install automatically. Token use is tied to the explicit login and hotel commands and is directed to the service endpoints used by the package.
Static reason
One or more suspicious static signals were detected.
Trigger
The version check runs at CLI startup; OAuth and hotel API operations run when their corresponding commands are invoked.
Impact
The reviewed source shows no automatic collection or unrelated transmission of user data. Updating requires running the explicit update command.
Mechanism
Startup checks the npm registry for a newer version. Login uses OAuth, while hotel API requests send the saved access token to the configured MCP endpoint.
Evidence
~/.hotel-cli/token.json (or %USERPROFILE%/.hotel-cli/token.json)
Network endpoints5
registry.npmjs.orgrollinggo.storeapi.rollinggo.cnmcp.rollinggo.cnapi.qrserver.com