IBM Code Engine MCP Server
NPM · CODE-ENGINE-MCP-SERVER
Deploy to IBM Code Engine from Cursor, Copilot, Claude & Cline. Build, push, deploy via MCP.
Available components
Last scanned (13 hours ago)
Scores higher than 68% of npm servers
Category Cloud Infrastructure
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
- 33 of 106 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 (Apache-2.0).Pass
- Actively maintained (last published 35 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability74
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 4603 tokens (~70/item across 65 items; 65 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage85
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 56% of tool parameters carry a description.Partial
Tool Safety75
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- 0 of 11 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "icr_delete_image" implies "delete" 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 65 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
Checks we ran (16)
- Malware scan
- Known CVEs
- Install scripts
- Dependency health
- Source repository
- Provenance
- License
- Maintenance
- Security disclosure
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Does not apply to this package (2)
- Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
- Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
The score does not measure everything. What the score does not measure →
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.
- 6 Nov 26 0
- Stability: 0.97 → pass security
- Security disclosure: unverified → fail ▼ functional
- 5 Nov 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.
- 4 Nov 26 −1
- Stability: pass → 0.93 functional
- 2 Nov 26 0
- Security disclosure: fail → unverified ▼ functional
- 29 Oct 26 0
- Stability: 0.97 → pass security
- 28 Oct 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.
- 27 Oct 26 −1
- Stability: pass → 0.93 functional
- 17 Oct 26 +2
- Stability: 0.83 → pass security
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 6 Nov 2026 · Analysed npm/code-engine-mcp-server@1.4.2
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 106 packages
| Packages resolved | 106 |
|---|---|
| Stale | 33 |
| 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 →
icr_create_namespace ~79
Create a new namespace in IBM Container Registry. Required before pushing images for the first time. Uses the ICR REST API with your IBM Cloud API key.
| Name | Type | Req | Description |
|---|---|---|---|
| namespace | string | yes | Namespace name to create (lowercase, alphanumeric and hyphens) |
| region | string | – | ICR host (default: us.icr.io) |
No output schema declared.
No examples provided.
icr_delete_image ~75
Delete an image from IBM Container Registry (ICR) by tag or digest
| Name | Type | Req | Description |
|---|---|---|---|
| image | string | yes | Full image reference to delete, e.g. us.icr.io/mynamespace/myapp:v1.0.0 |
| region | string | – | ICR region host (default: us.icr.io) |
No output schema declared.
No examples provided.
icr_list_images ~50
List images in IBM Container Registry (ICR)
| Name | Type | Req | Description |
|---|---|---|---|
| namespace | string | – | Filter by namespace (optional) |
| region | string | – | ICR region host (default: us.icr.io) |
No output schema declared.
No examples provided.
icr_list_namespaces ~42
List IBM Container Registry (ICR) namespaces in your account
| Name | Type | Req | Description |
|---|---|---|---|
| region | string | – | ICR region host (default: us.icr.io) |
No output schema declared.
No examples provided.
inspect_container_image ~53
Inspect a local container image — shows architecture, labels, environment variables, entrypoint, exposed ports, and layer count
| Name | Type | Req | Description |
|---|---|---|---|
| image_name | string | yes | Image name/tag to inspect |
| runtime | string | – | – |
No output schema declared.
No examples provided.
list_local_images ~22
List all local container images
| Name | Type | Req | Description |
|---|---|---|---|
| runtime | string | – | – |
No output schema declared.
No examples provided.
login_to_registry ~123
Log in to a container registry (e.g. IBM Container Registry) so images can be pushed/pulled. Uses IBM Cloud IAM token for ICR or username/password for other registries.
| Name | Type | Req | Description |
|---|---|---|---|
| password | string | – | Password or API key. For ICR leave blank to use IBMCLOUD_API_KEY env var. |
| registry | string | yes | Registry hostname (default: us.icr.io for ICR) |
| runtime | string | – | – |
| username | string | – | Username — use "iamapikey" for ICR with an IBM Cloud API key |
No output schema declared.
No examples provided.
proc_build_push_deploy ~413
PROCEDURE: Full container pipeline in one step — auto-detects Podman or Docker, builds for linux/amd64, pushes to IBM Container Registry (ICR), creates or updates a Code Engine application, waits for ready, and returns the public URL. Accepts a project name or ID. Builds the full ICR image path from namespace + app name + tag so you do not need to know ICR URLs. When PROVENANCE_ENABLED=true, emits signed receipts for Dockerfile validation and deploy completion (fail-open).
| Name | Type | Req | Description |
|---|---|---|---|
| app_name | string | yes | Name for the application in Code Engine (e.g. my-app) |
| context_path | string | yes | Path to the directory containing the Dockerfile (e.g. examples/starwars-splash or ./my-app) |
| env_vars | object | – | Key/value environment variables to set on the app |
| icr_host | string | – | ICR host (default: us.icr.io — leave blank unless using a different region) |
| icr_namespace | string | yes | Your IBM Container Registry namespace (e.g. my-namespace). Use icr_list_namespaces to find it. |
| image_secret | string | yes | Name of the registry pull secret in Code Engine (e.g. icr-pull-secret). Created with ce_create_secret format=registry. |
| image_tag | string | – | Image version tag (e.g. v1.0.0 or latest). Defaults to "latest". |
| port | number | – | Container port the app listens on (default 8080) |
| project_id_or_name | string | yes | Code Engine project name (e.g. "my-project") or project ID (UUID). Use ce_list_projects if unsure. |
| scale_max_instances | number | – | Maximum running instances (default 10) |
| scale_min_instances | number | – | Minimum running instances (default 0 = scale to zero) |
| timeout_seconds | number | – | Max seconds to wait for app ready (default 180) |
No output schema declared.
No examples provided.
proc_setup_custom_domain ~211
PROCEDURE: Custom domain setup in one step — reads TLS certificate PEM files from disk (e.g. from certbot/Let's Encrypt), creates a TLS secret in Code Engine, then creates the domain mapping. Returns the CNAME target value to add in your DNS provider.
| Name | Type | Req | Description |
|---|---|---|---|
| app_name | string | yes | The Code Engine app to map the custom domain to |
| cert_pem_path | string | yes | Path to the certificate chain PEM file — typically ~/certbot/config/live/<domain>/fullchain.pem |
| domain_name | string | yes | Your custom domain (e.g. myapp.example.com) |
| key_pem_path | string | yes | Path to the private key PEM file — typically ~/certbot/config/live/<domain>/privkey.pem |
| project_id_or_name | string | yes | Code Engine project name or ID |
| tls_secret_name | string | yes | Name to give the TLS secret in Code Engine (e.g. myapp-tls). Must be unique in the project. |
No output schema declared.
No examples provided.
prune_images ~63
Remove unused/dangling container images to reclaim disk space. By default removes only dangling images; use all=true to remove all unused images.
| Name | Type | Req | Description |
|---|---|---|---|
| all | boolean | – | Remove all unused images, not just dangling ones (default: false) |
| runtime | string | – | – |
No output schema declared.
No examples provided.
push_container_image ~35
Push container image to registry
| Name | Type | Req | Description |
|---|---|---|---|
| image_name | string | yes | Full image name with registry |
| runtime | string | – | – |
No output schema declared.
No examples provided.
remove_local_image ~81
Remove a local container image to free disk space
| Name | Type | Req | Description |
|---|---|---|---|
| force | boolean | – | Force removal even if the image is used by a stopped container (default: false) |
| image_name | string | yes | Image name/tag to remove (e.g. us.icr.io/mynamespace/myapp:v1.0.0) |
| runtime | string | – | – |
No output schema declared.
No examples provided.
tag_container_image ~96
Tag a local container image with a new name/tag — useful to retag before pushing to ICR
| Name | Type | Req | Description |
|---|---|---|---|
| runtime | string | – | Container runtime (default: auto-detected) |
| source_image | string | yes | Existing image name/tag (e.g. myapp:latest) |
| target_image | string | yes | New image name/tag (e.g. us.icr.io/mynamespace/myapp:v1.0.0) |
No output schema declared.
No examples provided.
test_container_locally ~61
Run container locally for testing
| Name | Type | Req | Description |
|---|---|---|---|
| env_vars | object | – | Environment variables |
| image_name | string | yes | – |
| port_mapping | string | – | Port mapping (e.g., 8080:8080) |
| runtime | string | – | – |
No output schema declared.
No examples provided.
write_or_modify_file ~94
Write or update a text file in the workspace. Returns bytes written and content hash. When PROVENANCE_ENABLED=true, emits a signed provenance receipt after completion (fail-open).
| Name | Type | Req | Description |
|---|---|---|---|
| content | string | yes | Full file content (UTF-8 text) |
| operation | string | – | create | update | auto (default auto — detect from existing file) |
| path | string | yes | Relative or absolute file path to write |
No output schema declared.
No examples provided.
How do I install the IBM Code Engine MCP Server server?
IBM Code Engine MCP Server runs locally as an npm package, launched with npx -y code-engine-mcp-server. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · code-engine-mcp-server
claude mcp add markusvankempen-code-engine-mcp-server -- npx -y code-engine-mcp-server
What is the IBM Code Engine MCP Server server?
IBM Code Engine MCP Server is listed in the public MCP registry as io.github.markusvankempen/code-engine-mcp-server. Deploy to IBM Code Engine from Cursor, Copilot, Claude & Cline. Build, push, deploy via MCP. This page covers its npm package (code-engine-mcp-server).
Is the IBM Code Engine MCP Server server safe to use?
IBM Code Engine MCP Server scores 81 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 6 November 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 IBM Code Engine MCP Server server expose?
IBM Code Engine MCP Server exposes 65 tools: detect_container_runtime, build_container_image, push_container_image, list_local_images, test_container_locally, and 60 more. Their descriptions and schemas cost roughly 4,603 tokens of context every time the server is loaded.
Is the IBM Code Engine MCP Server server still maintained?
IBM Code Engine MCP Server is still listed as active in the MCP registry. We last reached this channel on 6 November 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 IBM Code Engine MCP Server server under?
IBM Code Engine MCP Server declares the Apache-2.0 licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.
What did VerifyMCP test on the IBM Code Engine MCP Server server?
VerifyMCP ran 16 checks on IBM Code Engine MCP Server, covering Malware scan, Known CVEs, Install scripts, Dependency health and 12 more. Endpoint Security and Transport & Reachability do not apply to an npm package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.