Letting users trust their own MCP clients, without opening a phishing hole
- Stream Vessel / Blog November 4, 2026 · Alexander Loginov · 10 min read 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: it registers itself, opens a browser, you click Approve, it gets a token.
Unverified
- Stream Vessel / Blog November 4, 2026 · Alexander Loginov · 10 min read 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: it registers itself, opens a browser, you click Approve, it gets a token.
Sources: Streamvessel