com.mcparmory/e2b
OCI · GHCR.IO/MCPARMORY/E2B:1.0.5 · 2 COMPONENTS · SCANNED SEP 20
Create and manage secure sandboxes for running AI agent code
Available components
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security0
- Malware scan not yet available for this package.Unverified
- Known CVEs could not be checked: this artifact ships no SBOM, so there is no dependency list to read. Publishing one would let us assess it.Unverified
- Install-script risk not yet assessed.Unverified
- Dependency health could not be checked: this artifact ships no SBOM, so there is no dependency list to read. Publishing one would let us assess it.Unverified
Provenance & Transparency32
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- License check failed: no license is declared. See how to fix → Fail
- Actively maintained (last published 130 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability80
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 3559 tokens (~82/item across 43 items; 43 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management80
- Stability observed for 24 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- All 7 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
- An AI judge read all 43 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Unverified: 1 category
A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.
How do I install the com.mcparmory/e2b MCP server?
com.mcparmory/e2b runs locally as a container image, launched with docker run --rm -i ghcr.io/mcparmory/e2b:1.0.5. Ready-made configuration for Claude, Cursor, VS Code, Codex and 3 more is on this page, copied from each client's own documentation.
oci · ghcr.io/mcparmory/e2b:1.0.5
claude mcp add com-mcparmory-e2b -- docker run --rm -i ghcr.io/mcparmory/e2b:1.0.5
{
"mcpServers": {
"com-mcparmory-e2b": {
"command": "docker",
"args": [
"run",
"--rm",
"-i",
"ghcr.io/mcparmory/e2b:1.0.5"
]
}
}
} {
"servers": {
"com-mcparmory-e2b": {
"command": "docker",
"args": [
"run",
"--rm",
"-i",
"ghcr.io/mcparmory/e2b:1.0.5"
]
}
}
} codex mcp add com-mcparmory-e2b -- docker run --rm -i ghcr.io/mcparmory/e2b:1.0.5
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"com-mcparmory-e2b": {
"type": "local",
"command": [
"docker",
"run",
"--rm",
"-i",
"ghcr.io/mcparmory/e2b:1.0.5"
],
"enabled": true
}
}
} mcp_servers:
com-mcparmory-e2b:
command: "docker"
args: ["run", "--rm", "-i", "ghcr.io/mcparmory/e2b:1.0.5"] {
"McpServers": {
"com-mcparmory-e2b": {
"Transport": "stdio",
"Command": "docker",
"Arguments": [
"run",
"--rm",
"-i",
"ghcr.io/mcparmory/e2b:1.0.5"
]
}
}
} {
"mcpServers": {
"com-mcparmory-e2b": {
"command": "docker",
"args": [
"run",
"--rm",
"-i",
"ghcr.io/mcparmory/e2b:1.0.5"
]
}
}
} Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 20 Sept 26 −3
- Stability: pass → 0.80 functional
- 19 Sept 26 +1
- Stability: 0.97 → pass security
- 17 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.
- 15 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
- 12 Sept 26 −3
- Stability: pass → 0.77 functional
- 11 Sept 26 +1
- Stability: 0.97 → pass security
- 9 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.
- 7 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 20 Sept 2026 · Analysed oci/ghcr.io/mcparmory/e2b:1.0.5
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | oci |
| Reason | No attestation published |
Background: How many MCP packages publish verified provenance →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
assign_template_tags Assign Template Tags ~96
Assign one or more tags to a specific template build. Tags help organize and categorize templates for easier discovery and management.
| Name | Type | Req | Description |
|---|---|---|---|
| tags | array | yes | Array of tags to assign to the template. Tags are applied in the order provided and can be used for categorization and filtering. |
| target | string | yes | The target template specified in 'name:tag' format, where name is the template identifier and tag is the specific build version. |
No output schema declared.
No examples provided.
check_template_alias Check Template Alias ~41
Verify whether a template with the specified alias exists in the system.
| Name | Type | Req | Description |
|---|---|---|---|
| alias | string | yes | The unique identifier or name of the template to check for existence. |
No output schema declared.
No examples provided.
connect_sandbox Connect Sandbox ~79
Establish a connection to a sandbox and extend its time-to-live. If the sandbox is paused, it will be automatically resumed.
| Name | Type | Req | Description |
|---|---|---|---|
| sandboxID | string | yes | The unique identifier of the sandbox to connect to. |
| timeout | string | yes | The number of seconds from the current time until the sandbox should automatically expire. Must be a non-negative value. |
No output schema declared.
No examples provided.
create_access_token Create Access Token ~52
Create a new access token for API authentication. The token can be used to authorize requests to protected endpoints.
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | yes | A descriptive name for the access token to help identify its purpose or associated application. |
No output schema declared.
No examples provided.
create_api_key Create API Key ~56
Create a new API key for your team to authenticate API requests. The key can be used to access team resources and data.
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | yes | A descriptive name for the API key to help identify its purpose or associated application. |
No output schema declared.
No examples provided.
create_sandbox Create Sandbox ~225
Create a new sandbox instance from a specified template. The sandbox can be configured with network policies, environment variables, and storage mounts.
| Name | Type | Req | Description |
|---|---|---|---|
| allowOut | array | – | List of CIDR blocks or IP addresses permitted for outbound traffic. Allowed addresses take precedence over denied addresses when both are specified. |
| allowPublicTraffic | boolean | – | Control whether sandbox URLs are publicly accessible or require authentication to access. |
| denyOut | array | – | List of CIDR blocks or IP addresses blocked from outbound traffic. |
| enabled | boolean | yes | Enable automatic resumption of the sandbox when it enters a paused state. |
| envVars | – | – | Environment variables to inject into the sandbox runtime environment. |
| mcp | object | – | Model Context Protocol (MCP) configuration settings for the sandbox. |
| metadata | – | – | Custom metadata to attach to the sandbox for tracking and organization purposes. |
| templateID | string | yes | The unique identifier of the template to use for creating the sandbox. |
| volumeMounts | array | – | Volume mounts to attach to the sandbox, enabling access to external storage or data sources. |
No output schema declared.
No examples provided.
create_sandbox_snapshot Create Sandbox Snapshot ~96
Create a persistent snapshot of the sandbox's current state that can be used to create new sandboxes and persists beyond the original sandbox's lifetime.
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | – | Optional name for the snapshot. If a snapshot with this name already exists, a new build will be assigned to the existing snapshot instead of creating a new one. |
| sandboxID | string | yes | The unique identifier of the sandbox from which to create the snapshot. |
No output schema declared.
No examples provided.
create_template Create Template ~160
Create a new template with optional resource specifications and organizational tags. Templates define sandbox configurations for reproducible environments.
| Name | Type | Req | Description |
|---|---|---|---|
| cpuCount | string | – | Number of CPU cores to allocate to the sandbox. Must be at least 1 core. |
| memoryMB | string | – | Memory to allocate to the sandbox in mebibytes (MiB). Must be at least 128 MiB. |
| name | string | – | Name of the template. Optionally include a version tag using colon separator (e.g., 'my-template:v1'). If a tag is provided in the name, it will be added to the tags array automatically. |
| tags | array | – | Tags to assign to the template for organization and categorization. Tags help identify and group related templates. |
No output schema declared.
No examples provided.
create_volume Create Volume ~62
Create a new team volume for storing and organizing data. The volume name must be unique within the team and follow alphanumeric naming conventions.
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | yes | The name identifier for the volume. Must contain only letters, numbers, hyphens, and underscores. |
No output schema declared.
No examples provided.
delete_api_key Delete API Key ~49
Permanently delete a team API key. This action cannot be undone and will invalidate any requests using this key.
| Name | Type | Req | Description |
|---|---|---|---|
| apiKeyID | string | yes | The unique identifier of the API key to delete. |
No output schema declared.
No examples provided.
delete_template Delete Template ~39
Permanently delete a template by its ID. This action cannot be undone.
| Name | Type | Req | Description |
|---|---|---|---|
| templateID | string | yes | The unique identifier of the template to delete. |
No output schema declared.
No examples provided.
delete_volume Delete Volume ~40
Permanently delete a team volume by its ID. This action cannot be undone.
| Name | Type | Req | Description |
|---|---|---|---|
| volumeID | string | yes | The unique identifier of the volume to delete. |
No output schema declared.
No examples provided.
get_node Get Node ~65
Retrieve detailed information about a specific node, optionally filtered by cluster membership.
| Name | Type | Req | Description |
|---|---|---|---|
| clusterID | string | – | The cluster to which the node belongs. Use this to scope the node lookup to a specific cluster. |
| nodeID | string | yes | The unique identifier of the node to retrieve. |
No output schema declared.
No examples provided.
get_sandbox Get Sandbox ~46
Retrieve a specific sandbox by its unique identifier. Use this operation to fetch detailed information about a sandbox environment.
| Name | Type | Req | Description |
|---|---|---|---|
| sandboxID | string | yes | The unique identifier of the sandbox to retrieve. |
No output schema declared.
No examples provided.
get_sandbox_metrics Get Sandbox Metrics ~117
Retrieve performance and resource metrics for a specific sandbox over an optional time interval. Metrics are aggregated between the specified start and end timestamps.
| Name | Type | Req | Description |
|---|---|---|---|
| end | string | – | Unix timestamp in seconds marking the end of the metrics collection interval. If omitted, metrics are retrieved up to the current time. |
| sandboxID | string | yes | The unique identifier of the sandbox for which to retrieve metrics. |
| start | string | – | Unix timestamp in seconds marking the beginning of the metrics collection interval. If omitted, metrics are retrieved from the earliest available data. |
No output schema declared.
No examples provided.
get_team_metrics Get Team Metrics ~114
Retrieve performance and activity metrics for a specific team over an optional time interval. If no time range is specified, returns metrics for the current period.
| Name | Type | Req | Description |
|---|---|---|---|
| end | string | – | Unix timestamp in seconds marking the end of the metrics interval. If omitted, defaults to the current time. |
| start | string | – | Unix timestamp in seconds marking the start of the metrics interval. If omitted, defaults to the beginning of the current period. |
| teamID | string | yes | The unique identifier of the team for which to retrieve metrics. |
No output schema declared.
No examples provided.
get_team_metrics_maximum Get Team Metrics Maximum ~133
Retrieve the maximum value for a specified metric within a given time interval for a team. Useful for understanding peak performance or resource utilization.
| Name | Type | Req | Description |
|---|---|---|---|
| end | string | – | Unix timestamp in seconds marking the end of the interval. If omitted, metrics up to the current time are included. |
| metric | string | yes | The specific metric to retrieve the maximum value for during the interval. |
| start | string | – | Unix timestamp in seconds marking the start of the interval. If omitted, metrics from the earliest available data are included. |
| teamID | string | yes | The unique identifier of the team for which to retrieve metrics. |
No output schema declared.
No examples provided.
get_template_build_status Get Template Build Status ~149
Retrieve the current status and build logs for a specific template build. Returns build information with optional log filtering by offset, limit, and severity level.
| Name | Type | Req | Description |
|---|---|---|---|
| buildID | string | yes | The unique identifier of the build whose status should be retrieved. |
| level | string | – | Filter logs by severity level. Returns only logs matching the specified level or higher priority. |
| limit | string | – | The maximum number of build logs to return in the response. Useful for controlling response size and pagination. |
| logsOffset | string | – | The starting index for build logs to return. Use this to paginate through large log sets. |
| templateID | string | yes | The unique identifier of the template containing the build. |
No output schema declared.
No examples provided.
get_template_files_upload_link Get Template File Upload Link ~89
Retrieve a download link for a tar archive containing the build layer files associated with a specific template. The link is generated based on the template ID and file hash.
| Name | Type | Req | Description |
|---|---|---|---|
| hash | string | yes | The cryptographic hash that identifies the specific version or snapshot of the template files to retrieve. |
| templateID | string | yes | The unique identifier of the template for which to retrieve the files upload link. |
No output schema declared.
No examples provided.
get_volume Get Volume ~37
Retrieve detailed information about a specific team volume by its unique identifier.
| Name | Type | Req | Description |
|---|---|---|---|
| volumeID | string | yes | The unique identifier of the volume to retrieve. |
No output schema declared.
No examples provided.
list_api_keys List API Keys ~30
Retrieve all API keys associated with your team. Use this to view and manage authentication credentials for API access.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_nodes List Nodes ~29
Retrieve a list of all available nodes in the system. Use this operation to discover and monitor all nodes.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_sandbox_logs List Sandbox Logs ~126
Retrieve logs from a specific sandbox with optional filtering by time range and result limit. Logs can be returned in forward or backward chronological order.
| Name | Type | Req | Description |
|---|---|---|---|
| cursor | string | – | Starting timestamp in milliseconds from which logs should be returned. Use this to paginate through results or retrieve logs after a specific point in time. |
| direction | string | – | Order in which logs should be returned relative to the cursor timestamp. |
| limit | string | – | Maximum number of log entries to return in a single response. |
| sandboxID | string | yes | The unique identifier of the sandbox for which to retrieve logs. |
No output schema declared.
No examples provided.
list_sandbox_metrics List Sandbox Metrics ~57
Retrieve performance and usage metrics for specified sandboxes. Supports querying multiple sandboxes in a single request.
| Name | Type | Req | Description |
|---|---|---|---|
| sandbox_ids | array | yes | One or more sandbox IDs to retrieve metrics for. Provide as a comma-separated list of sandbox identifiers. |
No output schema declared.
No examples provided.
list_sandboxes List Sandboxes ~117
Retrieve a list of all sandboxes with optional filtering by metadata and state. Results are paginated with a configurable limit.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | string | – | Maximum number of sandboxes to return per page. Must be between 1 and 100. |
| metadata | string | – | Filter sandboxes by metadata key-value pairs. Use URL encoding for both keys and values (e.g., user=abc&app=prod). |
| state | array | – | Filter sandboxes by one or more states. Provide as an array of state values. |
No output schema declared.
No examples provided.
list_snapshots List Snapshots ~67
Retrieve all snapshots for your team, with optional filtering by source sandbox and pagination support.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | string | – | Number of snapshots to return per page. Useful for paginating through large result sets. |
| sandboxID | string | – | Filter results to snapshots created from a specific sandbox ID. |
No output schema declared.
No examples provided.
list_teams List Teams ~32
Retrieve a list of all teams in the system. Use this operation to discover available teams for management or assignment purposes.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_template_build_logs List Template Build Logs ~192
Retrieve logs from a template build execution. Supports filtering by log level and source, with pagination and directional traversal of log entries.
| Name | Type | Req | Description |
|---|---|---|---|
| buildID | string | yes | The unique identifier of the build whose logs should be retrieved. |
| cursor | string | – | Starting point for log retrieval specified as a Unix timestamp in milliseconds. Logs returned will be from this timestamp onward (or backward, depending on direction). |
| direction | string | – | Order in which log entries should be returned relative to the cursor timestamp. |
| level | string | – | Filter logs by severity level. Only entries matching the specified level will be returned. |
| limit | string | – | Maximum number of log entries to return in a single response. |
| source | string | – | Filter logs by their storage source. Temporary logs are transient, while persistent logs are retained long-term. |
| templateID | string | yes | The unique identifier of the template containing the build. |
No output schema declared.
No examples provided.
list_template_builds List Template Builds ~78
Retrieve all builds associated with a specific template. Use pagination to control the number of results returned per page.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | string | – | The maximum number of builds to return in a single page of results. Defaults to 100 if not specified. |
| templateID | string | yes | The unique identifier of the template for which to retrieve builds. |
No output schema declared.
No examples provided.
list_template_tags List Template Tags ~51
Retrieve all tags associated with a specific template. Tags are used to categorize and organize templates for easier discovery and management.
| Name | Type | Req | Description |
|---|---|---|---|
| templateID | string | yes | The unique identifier of the template for which to retrieve tags. |
No output schema declared.
No examples provided.
list_templates List Templates ~62
Retrieve all templates available in the system, optionally filtered by a specific team. Use this to discover and display template options for users.
| Name | Type | Req | Description |
|---|---|---|---|
| teamID | string | – | Filter templates to a specific team. If omitted, returns templates accessible to all teams or the default scope. |
No output schema declared.
No examples provided.
list_volumes List Volumes ~33
Retrieve all volumes available to the team. This operation returns a complete list of storage volumes with their metadata and configuration details.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
pause_sandbox Pause Sandbox ~49
Pause an active sandbox to temporarily suspend its execution and resource consumption. The sandbox can be resumed later without losing its state.
| Name | Type | Req | Description |
|---|---|---|---|
| sandboxID | string | yes | The unique identifier of the sandbox to pause. |
No output schema declared.
No examples provided.
refresh_sandbox Refresh Sandbox ~80
Extend the time to live of an active sandbox by refreshing it. Optionally specify a custom duration to keep the sandbox alive.
| Name | Type | Req | Description |
|---|---|---|---|
| duration | integer | – | The duration in seconds to extend the sandbox's time to live. If not specified, a default duration will be applied. |
| sandboxID | string | yes | The unique identifier of the sandbox to refresh. |
No output schema declared.
No examples provided.
remove_template_tags Remove Template Tags ~71
Remove one or more tags from a specific template. This operation allows bulk deletion of tags associated with a template.
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | yes | The name of the template from which tags will be removed. |
| tags | array | yes | An array of tag names to remove from the template. Order is not significant. |
No output schema declared.
No examples provided.
revoke_access_token Revoke Access Token ~46
Revoke and delete an access token, immediately invalidating it for future API requests.
| Name | Type | Req | Description |
|---|---|---|---|
| accessTokenID | string | yes | The unique identifier of the access token to revoke and delete. |
No output schema declared.
No examples provided.
set_sandbox_timeout Set Sandbox Timeout ~102
Set the expiration time for a sandbox by specifying a timeout duration in seconds from the current request time. Calling this operation multiple times resets the sandbox's time-to-live (TTL), with each call using the current timestamp as the new starting point.
| Name | Type | Req | Description |
|---|---|---|---|
| sandboxID | string | yes | The unique identifier of the sandbox to configure. |
| timeout | string | yes | The number of seconds from the current time until the sandbox should automatically expire. Must be a non-negative integer. |
No output schema declared.
No examples provided.
start_template_build Start Template Build ~218
Initiate a build process for a specific template. This operation executes the build with optional customization including base template selection, build steps, and post-build commands.
| Name | Type | Req | Description |
|---|---|---|---|
| buildID | string | yes | The unique identifier for this specific build execution. |
| force | boolean | – | Whether to bypass cache and force the entire build to execute from scratch. |
| fromImageRegistry | – | – | Optional image registry configuration for sourcing or pushing build artifacts. |
| fromTemplate | string | – | Optional template ID to use as a base for this template build, allowing inheritance of template configuration. |
| readyCmd | string | – | Command to execute after the build to verify the template is ready and operational, used for health checks or readiness validation. |
| startCmd | string | – | Command to execute within the template after the build completes, typically used to start services or initialize the environment. |
| steps | array | – | Ordered list of build steps to execute. Each step represents a discrete build operation performed sequentially. |
| templateID | string | yes | The unique identifier of the template to build. |
No output schema declared.
No examples provided.
terminate_sandbox Terminate Sandbox ~47
Terminate and remove a sandbox environment by its ID. This operation permanently deletes the sandbox and all associated resources.
| Name | Type | Req | Description |
|---|---|---|---|
| sandboxID | string | yes | The unique identifier of the sandbox to terminate. |
No output schema declared.
No examples provided.
terminate_team_sandboxes Terminate Team Sandboxes ~57
Terminates all active sandboxes for a specified team. This operation will immediately stop and remove all sandbox instances associated with the team.
| Name | Type | Req | Description |
|---|---|---|---|
| teamID | string | yes | The unique identifier of the team whose sandboxes should be terminated. |
No output schema declared.
No examples provided.
update_api_key Update API Key ~78
Update the name of a team API key. Allows you to rename an existing API key for better organization and identification.
| Name | Type | Req | Description |
|---|---|---|---|
| apiKeyID | string | yes | The unique identifier of the API key to update. |
| name | string | yes | The new name for the API key. Use a descriptive name to identify the key's purpose or associated application. |
No output schema declared.
No examples provided.
update_node_status Update Node Status ~111
Update the operational status of a node within a cluster. This operation allows you to transition a node between different states such as ready, draining, connecting, or unhealthy.
| Name | Type | Req | Description |
|---|---|---|---|
| clusterID | string | – | The unique identifier of the cluster containing the node. Required to scope the node operation within the correct cluster context. |
| nodeID | string | yes | The unique identifier of the node to update. |
| status | string | yes | The desired operational status for the node. Determines how the node handles workloads and cluster participation. |
No output schema declared.
No examples provided.
update_template Update Template ~81
Update an existing template's properties, such as its visibility settings. Modify template accessibility to be public or restricted to team members only.
| Name | Type | Req | Description |
|---|---|---|---|
| public | boolean | – | Controls template visibility. When true, the template is accessible to anyone; when false, it is restricted to team members only. |
| templateID | string | yes | The unique identifier of the template to update. |
No output schema declared.
No examples provided.
What is the com.mcparmory/e2b MCP server?
com.mcparmory/e2b is an MCP server listed in the public MCP registry as com.mcparmory/e2b. Create and manage secure sandboxes for running AI agent code. This page covers its container image (ghcr.io/mcparmory/e2b:1.0.5).
Is the com.mcparmory/e2b MCP server safe to use?
com.mcparmory/e2b scores 50 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the com.mcparmory/e2b MCP server expose?
com.mcparmory/e2b exposes 43 tools: list_teams, get_team_metrics, get_team_metrics_maximum, create_sandbox, list_sandboxes, and 38 more. Their descriptions and schemas cost roughly 3,559 tokens of context every time the server is loaded.
Is the com.mcparmory/e2b MCP server still maintained?
com.mcparmory/e2b is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.