Ibmcloud MCP Server

ibmcloud-mcp-server npm v1.0.1

Published by expertvagabond — no publish provenance, so origin is unverified, but the source is public: the repository link below is self-declared yet readable, so you can inspect the code before adopting it.

Trust grade
A
93/100
Last scanned get badge →
Trust
A · 93/100
Adoption risk for you: the threat score, then adjusted down for blast radius, publisher verification and how much the scan could see. Deterministic; every point is auditable.
Capability
High
Blast radius if it went rogue — what the server’s tools could reach. Independent of trust.
Coverage
Source
How much the scan could actually inspect. Shallow coverage is stated, never hidden.
A Why this grade threat 100 − adoption risk = 93/100

The grade answers one question — how safe is this server for you to adopt — so it is computed in two auditable stages. Nothing below is an opinion or an LLM's guess; every line is a real term the deterministic engine applied, and the same input always yields the same number.

1. Threat score — 100 − 0 = 100. What the published surface and source actually contain:

The deterministic scan raised no scored threat in the surface it inspected — the threat score stayed at 100. Capability observations and advisory notes are recorded but never lower it.

2. Client adoption risk — 100 − 7 = 93. Three small, subtract-only factors that reflect your risk in adopting it — a clean scan proves less on a powerful, unverified or barely-inspectable package, so the grade says so plainly:

PointsAdoption-risk factor
−6 capability blast radius (high) — client exposure if the model is manipulated
−1 publisher verification (public source) — no provenance, but the source is public and inspectable

Capability observations and info notes are shown under Findings but never scored. Open any row's finding below for the file, line and evidence behind a deduction.

Findings 2

high Shell/command execution in server code (dist/cli.js)MTC-SRC-002

In the server's implementation (`dist/cli.js:1`): Spawning a shell/process is command-execution capability; with unsanitized tool input it is command injection / RCE. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.

Evidence: import { spawn } from "child_process"; export async function executeIBMCloud(args, options) { return new Promise((r

Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.

Location: server dist/cli.js

high Shell/command execution in server code (src/cli.ts)MTC-SRC-002

In the server's implementation (`src/cli.ts:1`): Spawning a shell/process is command-execution capability; with unsanitized tool input it is command injection / RCE. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.

Evidence: import { spawn } from "child_process"; export interface CLIResult { success: boolean; stdout: string; stderr: st

Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.

Location: server src/cli.ts

Tools 88

Each tool and what it can reach — statically extracted from the published source.

  • ibmcloud_account_listno sensitive capability
  • ibmcloud_account_showno sensitive capability
  • ibmcloud_apino sensitive capability
  • ibmcloud_billing_account_usageno sensitive capability
  • ibmcloud_billing_org_usageno sensitive capability
  • ibmcloud_billing_resource_group_usageno sensitive capability
  • ibmcloud_billing_resource_instances_usageno sensitive capability
  • ibmcloud_catalog_searchno sensitive capability
  • ibmcloud_catalog_serviceno sensitive capability
  • ibmcloud_catalog_service_plansno sensitive capability
Show 78 more tools ↓
  • ibmcloud_cf_appno sensitive capability
  • ibmcloud_cf_appsno sensitive capability
  • ibmcloud_cf_bind_serviceno sensitive capability
  • ibmcloud_cf_create_serviceno sensitive capability
  • ibmcloud_cf_deleteno sensitive capability
  • ibmcloud_cf_envno sensitive capability
  • ibmcloud_cf_logsno sensitive capability
  • ibmcloud_cf_marketplaceno sensitive capability
  • ibmcloud_cf_orgsno sensitive capability
  • ibmcloud_cf_pushno sensitive capability
  • ibmcloud_cf_restartno sensitive capability
  • ibmcloud_cf_routesno sensitive capability
  • ibmcloud_cf_scaleno sensitive capability
  • ibmcloud_cf_servicesno sensitive capability
  • ibmcloud_cf_set_envno sensitive capability
  • ibmcloud_cf_spacesno sensitive capability
  • ibmcloud_cf_startno sensitive capability
  • ibmcloud_cf_stopno sensitive capability
  • ibmcloud_cf_unbind_serviceno sensitive capability
  • ibmcloud_config_listno sensitive capability
  • ibmcloud_cr_image_rmno sensitive capability
  • ibmcloud_cr_imagesno sensitive capability
  • ibmcloud_cr_namespace_addno sensitive capability
  • ibmcloud_cr_namespacesno sensitive capability
  • ibmcloud_cr_quotano sensitive capability
  • ibmcloud_iam_access_groupno sensitive capability
  • ibmcloud_iam_access_group_createno sensitive capability
  • ibmcloud_iam_access_group_policiesno sensitive capability
  • ibmcloud_iam_access_group_policy_createno sensitive capability
  • ibmcloud_iam_access_group_user_addno sensitive capability
  • ibmcloud_iam_access_group_usersno sensitive capability
  • ibmcloud_iam_access_groupsno sensitive capability
  • ibmcloud_iam_api_key_createno sensitive capability
  • ibmcloud_iam_api_key_deleteno sensitive capability
  • ibmcloud_iam_api_keysno sensitive capability
  • ibmcloud_iam_rolesno sensitive capability
  • ibmcloud_iam_service_api_key_createno sensitive capability
  • ibmcloud_iam_service_api_keysno sensitive capability
  • ibmcloud_iam_service_idno sensitive capability
  • ibmcloud_iam_service_id_createno sensitive capability
  • ibmcloud_iam_service_id_deleteno sensitive capability
  • ibmcloud_iam_service_idsno sensitive capability
  • ibmcloud_iam_user_inviteno sensitive capability
  • ibmcloud_iam_usersno sensitive capability
  • ibmcloud_ks_clusterno sensitive capability
  • ibmcloud_ks_cluster_configno sensitive capability
  • ibmcloud_ks_cluster_createno sensitive capability
  • ibmcloud_ks_cluster_deleteno sensitive capability
  • ibmcloud_ks_clustersno sensitive capability
  • ibmcloud_ks_flavorsno sensitive capability
  • ibmcloud_ks_versionsno sensitive capability
  • ibmcloud_ks_worker_pool_createno sensitive capability
  • ibmcloud_ks_worker_pool_resizeno sensitive capability
  • ibmcloud_ks_worker_poolsno sensitive capability
  • ibmcloud_ks_workersno sensitive capability
  • ibmcloud_ks_zonesno sensitive capability
  • ibmcloud_loginno sensitive capability
  • ibmcloud_logoutno sensitive capability
  • ibmcloud_plugin_installno sensitive capability
  • ibmcloud_plugin_listno sensitive capability
  • ibmcloud_plugin_repo_pluginsno sensitive capability
  • ibmcloud_regionsno sensitive capability
  • ibmcloud_resource_group_createno sensitive capability
  • ibmcloud_resource_groupsno sensitive capability
  • ibmcloud_resource_searchno sensitive capability
  • ibmcloud_resource_service_instanceno sensitive capability
  • ibmcloud_resource_service_instance_createno sensitive capability
  • ibmcloud_resource_service_instance_deleteno sensitive capability
  • ibmcloud_resource_service_instance_updateno sensitive capability
  • ibmcloud_resource_service_instancesno sensitive capability
  • ibmcloud_resource_service_keyno sensitive capability
  • ibmcloud_resource_service_key_createno sensitive capability
  • ibmcloud_resource_service_key_deleteno sensitive capability
  • ibmcloud_resource_service_keysno sensitive capability
  • ibmcloud_resource_tag_attachno sensitive capability
  • ibmcloud_resource_tagsno sensitive capability
  • ibmcloud_targetno sensitive capability
  • ibmcloud_versionno sensitive capability

What this scan could not see

Versions 1

Scan history per published version. The engine is deterministic — the same version always yields the same score, so a changed score means the package itself changed.

VersionScoreFindingsEngineScanned
v1.0.1 latest A 93/100 2 1.9.0 2026-07-23

Embed this score

Show this server's live Trust Score in your README, docs or website. The badge is served straight from the registry and updates automatically after every rescan — no API key needed. It links back to this page, so anyone who sees the grade can also read the findings behind it instead of taking a number on faith.

MCP Trust Score: A · 93/100
Markdown (GitHub README)
[![MCP Trust Score](https://mcptrustchecker.com/registry/ibmcloud-mcp-server/badge.svg)](https://mcptrustchecker.com/registry/ibmcloud-mcp-server)
HTML
<a href="https://mcptrustchecker.com/registry/ibmcloud-mcp-server"><img src="https://mcptrustchecker.com/registry/ibmcloud-mcp-server/badge.svg" alt="MCP Trust Score" height="20"></a>
Prefer shields.io styling? Point it at https://mcptrustchecker.com/registry/ibmcloud-mcp-server/badge.json via https://img.shields.io/endpoint?url=…

Verify this score yourself

The score above is reproducible: the same package version always yields the same result. Run it locally or over the free API — no account, no LLM, fully deterministic.

npx mcptrustchecker scan ibmcloud-mcp-server --online

Use the free API → How scoring works

More in Developer Tools