
概览
主要功能
- 一条命令的MCP服务器部署
- 容器化、隔离的工具执行
- 内置的机密管理
- 对于代理的策略和访问控制
- 审计过的MCP服务器注册表
- 与常见AI客户端的集成
价格
- 模型
- Free
- 分类
- Legal
- 评分
- 4.7 / 5 (6)
使用场景
一条命令部署MCP服务器
开发人员快速打开审计过的MCP服务器容器, 让AI代理访问新工具而不需要复杂的设置或配置
管控AI代理工具访问
平台工程师根据政策进行访问控制,确保安全和安全交互内部资料及外部服务
机密中心化处理
安全团队用内置的机密管理功能集中管理凭证,避免散播 API 键在MCP服务器部署
审计AI行为
组织实现对代理工具使用和sandboxed执行的可见性,以便更轻松地审计AI行为并满足法规要求
优点 & 缺点
优点
- 开源和自主托管
- 以容器隔离MCP服务器的安全更强
- 中心化秘密和策略控制
- 筛选过的注册表简化工具发现
缺点
- 需要了解容器和MCP方案的知识
- 生态体系还在成熟
- 仅在基于MCP的工作流外没有价值
评测
6 个评分的平均值。
登录以留下评测。
Compared a few options
Evaluated this against two competitors. Where it wins: containerized, sandboxed tool execution and isolates MCP servers in containers for stronger security. Where it lags: ecosystem still maturing. On balance the feature set — especially containerized, sandboxed tool execution — justifies the 5 stars for our use case.
Skeptical, then convinced
I went in skeptical — most tools in this space overpromise. It actually delivers on registry of vetted MCP servers, and curated registry simplifies tool discovery caught me off guard. still, I'd recommend giving it a real trial.
Does the job
Pretty happy overall. Registry of vetted MCP servers just works and curated registry simplifies tool discovery. but no dealbreakers — I'd recommend it to a friend without hesitating.
Does the job
Pretty happy overall. Registry of vetted MCP servers just works and open source and self-hostable. but no dealbreakers — I'd recommend it to a friend without hesitating.
Years in this space
I've evaluated a lot of these over the years. What stands out here is registry of vetted MCP servers — handled better than most — and centralized secrets and policy controls. Ecosystem still maturing is my one real gripe. Worth the time if this is your use case.
Solid for our team
We rolled this out across the team last quarter and isolates MCP servers in containers for stronger security. Policy and access controls for agents fits neatly into how we already work, and policy and access controls for agents removed a step we used to do by hand. Limited value outside MCP-based workflows, which is the main caveat, but it has held up under daily use.
问答
暂无问题 — 来当第一个提问的人吧。





