io.github.AkaciaNL/basicdeploy-mcp
NPM · BASICDEPLOY-MCP · SCANNED SEP 22
The runtime your agent deploys to — DB, storage, and a public URL in one MCP call.
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 Security98
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- 31 of 95 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
- 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
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 18 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability84
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 1018 tokens (~84/item across 12 items; 12 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 Safety75
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- 0 of 3 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "exec_command" implies "exec" and declares no destructiveHint at all, which the MCP spec reads as destructive by default. See how to fix → Fail
- An AI judge read all 12 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
How do I install the io.github.AkaciaNL/basicdeploy-mcp server?
io.github.AkaciaNL/basicdeploy-mcp runs locally as an npm package, launched with npx -y basicdeploy-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · basicdeploy-mcp
claude mcp add akacianl-basicdeploy-mcp -- npx -y basicdeploy-mcp
{
"mcpServers": {
"akacianl-basicdeploy-mcp": {
"command": "npx",
"args": [
"-y",
"basicdeploy-mcp"
]
}
}
} {
"servers": {
"akacianl-basicdeploy-mcp": {
"command": "npx",
"args": [
"-y",
"basicdeploy-mcp"
]
}
}
} codex mcp add akacianl-basicdeploy-mcp -- npx -y basicdeploy-mcp
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"akacianl-basicdeploy-mcp": {
"type": "local",
"command": [
"npx",
"-y",
"basicdeploy-mcp"
],
"enabled": true
}
}
} openclaw mcp add akacianl-basicdeploy-mcp --command npx --arg -y --arg basicdeploy-mcp
mcp_servers:
akacianl-basicdeploy-mcp:
command: "npx"
args: ["-y", "basicdeploy-mcp"] {
"McpServers": {
"akacianl-basicdeploy-mcp": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"basicdeploy-mcp"
]
}
}
} assistant mcp add akacianl-basicdeploy-mcp -t stdio -c npx -a -y basicdeploy-mcp
{
"mcpServers": {
"akacianl-basicdeploy-mcp": {
"command": "npx",
"args": [
"-y",
"basicdeploy-mcp"
]
}
}
} 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.
- 22 Sept 26 −3
- Stability: pass → 0.80 functional
- 21 Sept 26 0
- Stability: 0.97 → pass security
- 20 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 18 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.
- 16 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.
- 15 Sept 26 −3
- Stability: pass → 0.80 functional
- 14 Sept 26 0
- Stability: 0.97 → pass security
- 13 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 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 22 Sept 2026 · Analysed npm/basicdeploy-mcp@1.0.7
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Background: How many MCP packages publish verified provenance →
Dependencies 95 packages
| Packages resolved | 95 |
|---|---|
| Stale | 31 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
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 →
create_container ~175
Create a new empty BasicDeploy container. A PostgreSQL database and an S3 bucket are provisioned automatically for it. Returns the container's id, subdomain, and public URL. Use deploy_app or exec_command afterwards to put an application in it. Optional memoryMb (256/512/1024/2048) and alwaysOn require the plan/add-ons to allow them (see get_account); larger sizes need Pro/Scale, and always-on on Free consumes a paid add-on slot.
| Name | Type | Req | Description |
|---|---|---|---|
| alwaysOn | boolean | – | Keep the container running 24/7 (never auto-sleep). On Free this uses a paid add-on slot. |
| memoryMb | number | – | Memory for the container in MB: 256, 512, 1024, or 2048. Defaults to the plan's default. |
No output schema declared.
No examples provided.
delete_container ~70
PERMANENTLY delete a container. This destroys the container, its database, and all its files (S3 bucket contents included) and cannot be undone. Only call this when the user has clearly asked for the container to be removed.
| Name | Type | Req | Description |
|---|---|---|---|
| containerId | string | yes | UUID of the container to delete |
No output schema declared.
No examples provided.
deploy_app ~154
Deploy an application from a local tarball (.tar, .tar.gz, .tgz, or .zip) to BasicDeploy. The runtime (Node.js, Python, or Go) is auto-detected from the archive contents. If containerId is omitted, a new container (with DB + S3) is created for the app; if provided, the archive is deployed into that existing container. Returns the resulting container and its public URL.
| Name | Type | Req | Description |
|---|---|---|---|
| containerId | string | – | Optional UUID of an existing container to deploy into. Omit to create a new one. |
| tarballPath | string | yes | Absolute path on local disk to the app archive (.tar, .tar.gz, .tgz, .zip) |
No output schema declared.
No examples provided.
exec_command ~73
Run a shell command inside a container (like docker exec). Returns the combined stdout/stderr output and the exit code. Useful for inspecting files, installing packages, or restarting processes inside the container.
| Name | Type | Req | Description |
|---|---|---|---|
| command | string | yes | Shell command to execute inside the container |
| containerId | string | yes | UUID of the container |
No output schema declared.
No examples provided.
get_account ~64
Show the account's plan and capabilities: plan tier, container limit (plan base + add-ons), the memory sizes you may select, storage limit, how many always-on add-ons you hold, and whether containers auto-sleep. Use this to see what you're allowed to set.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_container ~54
Get full details of one container: id, subdomain, public URL, status, ports, database name and username, S3 bucket, volume path, and timestamps.
| Name | Type | Req | Description |
|---|---|---|---|
| containerId | string | yes | UUID of the container |
No output schema declared.
No examples provided.
get_logs ~57
Fetch recent logs from a container. Use this to debug crashes or check application output.
| Name | Type | Req | Description |
|---|---|---|---|
| containerId | string | yes | UUID of the container |
| tail | integer | – | Number of log lines to return from the end (default 200) |
No output schema declared.
No examples provided.
list_containers ~43
List all BasicDeploy containers owned by (or shared with) the authenticated user. Returns each container's id, subdomain, public URL, status, and creation time.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
set_always_on ~91
Turn a container's always-on (24/7, never sleeps) flag on or off. On Free this consumes a paid always-on add-on slot (fails if none is free); on Pro/Scale every container is always-on already. Returns the updated container.
| Name | Type | Req | Description |
|---|---|---|---|
| containerId | string | yes | The container's UUID. |
| enabled | boolean | yes | true to enable always-on, false to disable. |
No output schema declared.
No examples provided.
share_container ~119
Share a container with another BasicDeploy user by email, giving them access to it. The recipient is emailed a link that signs them in and opens the container. Optionally pass expiresInHours to make the share expire after that many hours (omit for a share that never expires).
| Name | Type | Req | Description |
|---|---|---|---|
| containerId | string | yes | UUID of the container |
| string | yes | Email address of the user to share with | |
| expiresInHours | integer | – | Optional. Hours until the share expires. Omit for an unlimited (never-expiring) share. |
No output schema declared.
No examples provided.
sleep_container ~55
Sleep a running container: stop it to free memory while keeping its volume, database, and public URL, so it wakes again on the next request. Returns the updated container.
| Name | Type | Req | Description |
|---|---|---|---|
| containerId | string | yes | The container's UUID. |
No output schema declared.
No examples provided.
wake_container ~63
Wake a slept container so it serves traffic again (start it). A no-op if it is already running. Note: any web request to the container's public URL also wakes it automatically. Returns the updated container.
| Name | Type | Req | Description |
|---|---|---|---|
| containerId | string | yes | The container's UUID. |
No output schema declared.
No examples provided.
What is the io.github.AkaciaNL/basicdeploy-mcp server?
io.github.AkaciaNL/basicdeploy-mcp is listed in the public MCP registry as io.github.AkaciaNL/basicdeploy-mcp. The runtime your agent deploys to, DB, storage, and a public URL in one MCP call. This page covers its npm package (basicdeploy-mcp).
Is the io.github.AkaciaNL/basicdeploy-mcp server safe to use?
io.github.AkaciaNL/basicdeploy-mcp scores 81 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 22 September 2026. It declares no install or post-install scripts. 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 io.github.AkaciaNL/basicdeploy-mcp server expose?
io.github.AkaciaNL/basicdeploy-mcp exposes 12 tools: list_containers, create_container, set_always_on, wake_container, sleep_container, and 7 more. Their descriptions and schemas cost roughly 1,018 tokens of context every time the server is loaded.
Is the io.github.AkaciaNL/basicdeploy-mcp server still maintained?
io.github.AkaciaNL/basicdeploy-mcp is still listed as active in the MCP registry. We last reached this channel on 22 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the io.github.AkaciaNL/basicdeploy-mcp server under?
io.github.AkaciaNL/basicdeploy-mcp declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.