Grocery Shopping: why it is not safe to use
Grocery Shopping passed our review at 84/100, but it stores your Rohlik password in plaintext and can read your order, address, and payment data.
This skill connects Claude to your real Rohlik Group grocery account. It cleared most of our checks and scored 84/100, so it is usable, but two credential-related warnings are worth understanding before you install it.
What we found
- It requires ROHLIK_USERNAME and a plaintext ROHLIK_PASSWORD in your environment or Claude Desktop config. The credentials stay on your machine, but they are stored unencrypted.
- With ROHLIK_DEBUG enabled, login responses can be logged to the console. These include user and address IDs, though not the password itself.
- Once authenticated, it can read personal data: order history, delivery addresses, and payment or premium status. It relies on a reverse-engineered API the author labels "personal use only," so behavior may change.
- On the positive side, we found no data exfiltration, no third-party hosts or telemetry, no shell or filesystem commands, and no obfuscation. Traffic stays within Rohlik Group storefronts, and it cannot place a paid order outside your normal checkout.
What to do instead
- Store the password in your OS keychain or a secrets manager rather than plaintext config, and keep file permissions tight.
- Leave ROHLIK_DEBUG off except when troubleshooting.
- Consider a secondary account, and rotate the password if the config was ever shared or committed.
Want the same outcome, safely? Use our checked skill instead.
Source: https://github.com/tomaspavlin/rohlik-mcp
We report what our security review found at the time we checked, with the goal of keeping people safe. Projects change; if a maintainer has since fixed this, we are glad to recheck it. Email hello@agentpod.com.