Letting users trust their own MCP clients, without opening a phishing hole
The problem You run your own agent: a Slack bot, a service on a VPS, an MCP client you wrote over a weekend. You want it on your files, which on Stream Vessel means your own S3 bucket, where an agent can read, write and delete through the MCP server. The agent speaks MCP's standard OAuth sign-in: i…
Read the full story at DEV Community — AI ↗
Timeline · 1 report
- 2026-11-04 15:39 · DEV Community — AI
Letting users trust their own MCP clients, without opening a phishing hole