Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx agentmods add mcp/agentalabs/agenta-plugin/e2bgit clone --depth 1 https://github.com/agentalabs/agenta-pluginGrade A, and why
e2b scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 2d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
What it actually says
{
"e2b": {
"command": "npx",
"args": [
"-y",
"@e2b/mcp-server"
],
"env": {
"E2B_API_KEY": "${E2B_API_KEY}"
},
"description": "Cloud sandboxed code execution for TypeScript and Python"
}
}What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 2d ago First seen · 13 lines scan A c0744f99bfe1
e2b is an MCP server published in the GitHub repository agentalabs/agenta-plugin (2 stars, last pushed 5mo ago), licensed MIT. Its token cost is not measured: an MCP server costs its tool schemas, not its config file. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other mcp servers, from other repositories
nora
MCP server for Nora — deploy, monitor, and operate self-hosted OpenClaw and Hermes agent fleets on Docker or Kubernetes. Runs locally from the @noraai/mcp-server npm package. Needs 1 environment variable to run.
bedrock-agentcore
MCP server "bedrock-agentcore" as configured in aws-samples/sample-host-openclaw-on-amazon-bedrock-agentcore. Launched with /home/ec2-user/.local/bin/uvx awslabs.amazon-bedrock-agentcore-mcp-server@latest. Needs 1 environment variable to run.
oci-mcp-blueprint
MCP server "oci-mcp-blueprint" as configured in luigisaetta/oci-mcp-blueprint. Runs locally from the oci-mcp-blueprint Python package.
oci-context-mcp
MCP server "oci-context-mcp" as configured in Dennesssy/oci-context-mcp. Runs locally from the oci-context-mcp Python package.
vercel-mcp-pro
Complete Vercel MCP: deploys, logs, projects, env, domains, DNS, certs via the full REST API. Runs locally from the vercel-mcp-pro npm package. Needs 3 environment variables to run.
docs-langchain
MCP server "docs-langchain", hosted remotely at docs.langchain.com, as configured in langchain-ai/langchain.