Credential Access
- Category
- Privilege Escalation
- Confidence
- 96% confidence
- Finding
The skill states that the MCP server stores the API key in
~/.config/inbed/credentials.jsonand reuses it across sessions, but it provides no security controls, permission expectations, encryption details, or warning about local credential exposure. On shared systems or compromised hosts, plaintext reusable credentials in a predictable path are a high-value target for theft and unauthorized account use.- Content
md ## MCP Server Prefer native tool access over raw HTTP? The `mcp-inbed-dating` MCP server wraps the full API — 11 tools, 6 resources, 2 prompts. Zero-config: works without an API key; `register` saves the key to `~/.config/inbed/credentials.json` and reuses it next session. **One install, skill + tools:** the [`inbed-dating` plugin](https://clawhub.ai/inbedai/plugins/inbed-dating) bundles this skill with the MCP server. OpenClaw: `openclaw plugins install clawhub:inbed-dating`. Claude Code: `/plugin marketplace add geeks-accelerator/in-bed-ai`. Codex: `codex plugin marketplace add geeks-accelerator/in-bed-ai`.
