Miyamura80
Joined 4 years ago
Karma
11
Submissions
26
Member since
Feb 10
Founder sealgate.ai - Connect & govern AI interaction with your data | BT6 | Oxford CS Alum, prev. Self-Driving @ wayve.ai
View on Hacker NewsRecent submissions
Comment · 19 days ago
Sealgate.ai team here
We're really excited about the capability of mobile tunnel MCP to let agents fully control mobile phone capabilities via MCP: Bluetooth, Camera, mobile use, etc
Unlock: Agents control phone banking apps (not available any other way), drone apps, IoT and many others.
Comment · 24 days ago
Hey! We built infrastructure that can provide ACLs around command & credential restrictions, using MCP as auth middleware encrypted credentials to prevent agent overpriviledge - see sealgate.ai and let me know if this solves any issues here
Comment · 25 days ago
Yup this is 100% the best security measure we recommend clients & others, so they get better control over that single-point-of-access
Comment · 1 month ago
> MCP is a tool more for security than anything else.
+1 to this; API keys mean:
a) Your agents are overprivileged by default
b) Your API key is more likely to get into logs and pre-training / leaked as FrinkleFrankie mentioned
c) You can't manage it centrally with granular tool policies in Enterprises. (e.g. "you're not allowed to read slack channel for #finances")
Also, you can always collapse MCP to CLI, so MCP as auth/security middleware makes a lot of sense.
PoC of MCP -> CLI: https://github.com/edison-watch/cli
Comment · 1 month ago
If you need a solution that streams to your SIEM, we do that: https://sealgate.ai/docs/enterprise/siem-integration
Comment · 1 month ago
Agree! CLIs are still superior for piping etc, but as an auth middleware where the LLM doesn't see the credentials, I think it is really shaping up well
Comment · 2 months ago
Awesome!
Comment · 2 months ago
Many members of our team were users of Beeper, a "unified inbox" for chat networks like WhatsApp, Telegram, iMessage, Slack, LinkedIn DMs, etc, and wanted to expose this to our agents. However, we quickly ran into the issue where the Beeper MCP server requires the Beeper desktop app running locally and cannot connect via cloud agents.
This meant that any cloud/mobile agents (like Claude.ai, ChatGPT, Devin) not running on our laptops/devices with Beeper desktop installed could not access the Beeper MCP. This significantly limited many of the automations we wanted to build with Beeper MCP, some examples being:
Syncing LinkedIn DMs with CRM
Lurking on Large Community Group Chats and looking for insights
Automating repetitive messaging workflows
We built a mechanism for these cloud/mobile agents to be able to connect to Beeper, love to know how you find it!
1-line Quick Start:
Technical Blog:
https://sealgate.ai/blog/stdio-tunnels-cloud-agents-reach-lo...
Comment · 2 months ago
This makes a tonne of sense. NVIDIA actively does not want a world where they only have two customers between Anthropic and OpenAI, and empowering open source seems like the most beneficial way for them to commoditize OpenAI and Anthropic, and buying the biggest open source model hoster is a no-brainer
Comment · 2 months ago
This is cool, we've built similar things, I'm a bit uneasy with crypto stuff involved, especially with algorand
But FIDO2 passkey signature I absolutely agree should be the way to go. Just need more open standard without tokens involved
Comment · 2 months ago
Afaik the other main issue with github downtime is the choice they made a while back coming back to bite them