Run MCP (Model Context Protocol) servers securely in E2B sandboxes
Wellknown found it in public sources; nobody has proven control of it yet. Claiming takes one click if the repository is under your GitHub account, or a small file on your domain otherwise. Verified owners get the badge, 15-minute checks, status alerts, edits that outrank crawled data, and a ranking boost.
Agents can do it too: POST https://wellknown.network/api/v1/claims with {"agent":"e2b-mcp","method":"well_known_file"} — machine-readable steps at claim.json, guide at /docs/claim.
Everything here was measured by our prober or read from a registry. Nothing is self-reported.
Attributed to the source that supplied each field. Treated as claims, not facts.
# e2b-mcp [](https://opensource.org/licenses/MIT) Run [MCP (Model Context Protocol)](https://github.com/modelcontextprotocol) servers securely in [E2B](https://e2b.dev) sandboxes. e2b-mcp provides a simple way to execute MCP servers in isolated cloud environments, enabling safe execution of untrusted tools and code. Instead of running MCP servers directly on your host system, they run inside secure E2B sandboxes with automatic resource management and cleanup. ## Use Cases We built e2b-mcp so [Cased](https://cased.com) can run MCP servers on behalf of users, and integrate with our DevOps agent. But e2b-mcp has many use cases: ### **AI Agent Platforms** - **Safe Tool Execution**: Let AI agents use file operations, git commands, and web APIs without compromising your infrastructure - **User-Specific Sandboxes**: Run MCP servers with each user's credentials and permissions in isolated environments - **Dynamic Tool Discovery**: Discover and provision new capabilities for agents on-demand ### **SaaS Applications** - **Multi-Tenant Tool Execution**: Safely execute user-requested operations (file processing, data analysis) in dedicated sandboxes - **API Gateway for MCP**: Expose MCP tools as REST endpoints with built-in security and isolation - **Serverless MCP**: Scale MCP server instances based on demand without infrastructure management ### **Developer Tools & IDEs** - **Code Execution Environments**: Provide secure code execution for online IDEs and coding platforms - **Plugin Sandboxing**: Run untrusted MCP plugins safely without affecting the host environment - **CI/CD Integration**: Execute build/test tools in isolated environments with controlled access ### **Enterprise Solutions** - **Compliance & Security**: Meet security requirements by isolating all tool execution - **Customer Onboarding**: Let customers try tools and integrations safely before deployment - **Managed AI Services**…
Mapped onto the structured taxonomy from declared text and observed tool names. Confidence shown for derived entries.
Every source is kept verbatim. Field changes are logged as events.