# JumpServer Bastion (jms) (mcpb · jms-client.mcpb)

Run commands, transfer files and browse assets on a JumpServer v4 bastion from your AI assistant.

- Trust score: 49/100 (low)
- Change this week: +4
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- mcpb · `jms-client.mcpb`: 49/100 (this document), [markdown](https://verifymcp.io/servers/mifazhan-jms-client/jms-client.md), [page](https://verifymcp.io/servers/mifazhan-jms-client/jms-client)

## Channel facts

- Registry: `mcpb`
- Package: `https://github.com/MiFaZhan/jms-client/releases/download/v0.2.1/jms-client.mcpb`
- Transport: `stdio`
- SHA-256: `cf06d02334893ddb5f9f096387c35b717f78bace2c8d4188586a0f1a0cbc1c40`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-05.

- **Supply Chain Security**: 0/100
  - No malware scan is available for this kind of package: the supply-chain vendors we use do not cover it. This is a permanent gap in our coverage, not a finding about the package.
  - Known CVEs could not be checked: we found no dependency list to check in this bundle: either it runs a compiled binary, whose bundled manifests we do not read, or none of the package.json, requirements.txt, pyproject.toml or uv.lock files it ships for its runtime declares a dependency we can read (a requirements.txt that only points at a setup.py project, a local path, or a nested requirements file we cannot follow counts as none).
  - Install-script risk not yet assessed.
  - Dependency health could not be checked: we found no dependency list to check in this bundle: either it runs a compiled binary, whose bundled manifests we do not read, or none of the package.json, requirements.txt, pyproject.toml or uv.lock files it ships for its runtime declares a dependency we can read (a requirements.txt that only points at a setup.py project, a local path, or a nested requirements file we cannot follow counts as none).
- **Provenance & Transparency**: 45/100
  - Source repository is publicly reachable at the declared URL.
  - Provenance check failed: no build-provenance attestation is published.
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 0 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 71/100
  - AI-judged instruction clarity (good).
  - Tool/resource definitions use about 1277 tokens (~85/item across 15 items; 15 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 73/100
  - Stability observed for 22 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 75/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - 0 of 3 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "jms_asset_delete" implies "delete" and declares no destructiveHint at all, which the MCP spec reads as destructive by default.
  - An AI judge read all 15 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a current MCP spec version (2026-07-28).

**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.

## Install

### How do I install the JumpServer Bastion (jms) MCP server?

JumpServer Bastion (jms) ships as an MCPB bundle, a single file you download and open in an MCP host that supports MCPB bundles, such as Claude Desktop. The host reads the launch command from the bundle's own manifest, so there is no command to copy. Before opening it, check the file's SHA-256 matches the one the MCP registry declares for it, cf06d02334893ddb5f9f096387c35b717f78bace2c8d4188586a0f1a0cbc1c40; the commands to do that are on this page. If it does not match, do not open it.

- Download bundle: `https://github.com/MiFaZhan/jms-client/releases/download/v0.2.1/jms-client.mcpb`
- SHA-256: `cf06d02334893ddb5f9f096387c35b717f78bace2c8d4188586a0f1a0cbc1c40`

### Verify on macOS / Linux

```bash
echo "cf06d02334893ddb5f9f096387c35b717f78bace2c8d4188586a0f1a0cbc1c40  jms-client.mcpb" | shasum -a 256 -c
```

### Verify on Windows (PowerShell)

```powershell
(Get-FileHash -Algorithm SHA256 .\jms-client.mcpb).Hash -eq "cf06d02334893ddb5f9f096387c35b717f78bace2c8d4188586a0f1a0cbc1c40"
```

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-05 (score 49, +1)

No change was recorded against any check on this day. Stability & Change Management went from 70 to 73. That category is still filling its 30-day observation window: 21 days of observed history at the previous scan, 22 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-04 (score 48, +1)

- [functional regression] Schema quality: 75 → 85

### 2026-11-01 (score 47, +1)

No change was recorded against any check on this day. Stability & Change Management went from 57 to 60. That category is still filling its 30-day observation window: 17 days of observed history at the previous scan, 18 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-31 (score 46, 0)

- [functional regression] Security disclosure: unverified → fail

### 2026-10-30 (score 46, +1)

- [functional regression] Security disclosure: fail → unverified

### 2026-10-28 (score 45, +1)

No change was recorded against any check on this day. Stability & Change Management went from 43 to 47. That category is still filling its 30-day observation window: 13 days of observed history at the previous scan, 14 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-26 (score 44, +1)

No change was recorded against any check on this day. Stability & Change Management went from 37 to 40. That category is still filling its 30-day observation window: 11 days of observed history at the previous scan, 12 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-24 (score 43, +1)

No change was recorded against any check on this day. Stability & Change Management went from 30 to 33. That category is still filling its 30-day observation window: 9 days of observed history at the previous scan, 10 at this one. The score rises as the window fills, whether or not the server changes.

## MCP tools (15)

### `jms_asset_create` (~182 tokens)

Create a host asset on a JumpServer.

Input parameters:

- `account` (string): Account display name to attach; without one the asset cannot be connected to.
- `address` (string, required): Reachable address of the target host.
- `comment` (string): Free-text note stored with the asset.
- `config_path` (string): Configuration file path override.
- `name` (string, required): Asset name; must be unique on the server.
- `node_id` (string): Asset node id; the default node is used when omitted.
- `password` (string): Account password; sent in the request and never stored locally.
- `platform_id` (integer): Platform id; 0 means Linux.
- `server` (string): Server alias; the default server when omitted.
- `username` (string): Login name on the target host; defaults to the account name.

### `jms_asset_delete` (~59 tokens)

Delete a JumpServer asset. This cannot be undone.

Input parameters:

- `config_path` (string): Configuration file path override.
- `server` (string): Server alias; the default server when omitted.
- `target` (string, required): Asset name or id.

### `jms_asset_grant` (~165 tokens)

Grant users access to a JumpServer asset by creating an AssetPermission. A newly created asset is not reachable until it has been granted.

Input parameters:

- `accounts` (string): Accounts to allow; @ALL when omitted.
- `actions` (string): Actions to allow; connect when omitted.
- `comment` (string): Free-text note.
- `config_path` (string): Configuration file path override.
- `name` (string): Permission name; defaults to grant-<asset>.
- `protocols` (string): Protocols to allow; all when omitted.
- `server` (string): Server alias; the default server when omitted.
- `target` (string, required): Asset name or id to grant.
- `users` (string): User ids to grant; the authenticated user when omitted.

### `jms_asset_list` (~56 tokens)

List every asset that exists on a JumpServer, not only the ones you may connect to.

Input parameters:

- `config_path` (string): Configuration file path override.
- `server` (string): Server alias; the default server when omitted.

### `jms_asset_permissions` (~66 tokens)

List JumpServer asset permissions, optionally restricted to one asset.

Input parameters:

- `config_path` (string): Configuration file path override.
- `server` (string): Server alias; the default server when omitted.
- `target` (string): Asset name or id; lists every permission when omitted.

### `jms_asset_revoke` (~69 tokens)

Revoke a JumpServer asset permission. The asset stays; only the access it granted is removed.

Input parameters:

- `config_path` (string): Configuration file path override.
- `server` (string): Server alias; the default server when omitted.
- `target` (string, required): Permission name or id.

### `jms_asset_show` (~62 tokens)

Show one JumpServer asset in detail, by name or by id.

Input parameters:

- `config_path` (string): Configuration file path override.
- `server` (string): Server alias; the default server when omitted.
- `target` (string, required): Asset name or id.

### `jms_asset_update` (~89 tokens)

Update a JumpServer asset's name, comment or address.

Input parameters:

- `address` (string): New address.
- `comment` (string): New comment.
- `config_path` (string): Configuration file path override.
- `new_name` (string): New asset name.
- `server` (string): Server alias; the default server when omitted.
- `target` (string, required): Asset name or id.

### `jms_config_list` (~34 tokens)

List configured JumpServer servers, marking the default with '*'.

Input parameters:

- `config_path` (string): Configuration file path override.

### `jms_exec` (~117 tokens)

Execute a command on an asset and return its output.

Input parameters:

- `account` (string): Account override.
- `asset` (string, required): Asset name or address, optionally <asset>@<server>.
- `command` (string, required): Shell command to run.
- `config_path` (string): Configuration file path override.
- `protocol` (string): Protocol override.
- `server` (string): Server alias; the default server when omitted.
- `timeout` (integer): Timeout in seconds; 300 when omitted (override with JMS_MCP_EXEC_TIMEOUT).

### `jms_ls` (~60 tokens)

List or search authorized assets on a JumpServer.

Input parameters:

- `config_path` (string): Configuration file path override.
- `keyword` (string): Search keyword; lists everything when omitted.
- `server` (string): Server alias; the default server when omitted.

### `jms_resolve_asset` (~63 tokens)

Resolve an asset to its connection info (address, account, protocol).

Input parameters:

- `asset` (string, required): Asset name or address.
- `config_path` (string): Configuration file path override.
- `server` (string): Server alias; the default server when omitted.

### `jms_sftp_download` (~90 tokens)

Download a file from an asset to the local machine via SFTP.

Input parameters:

- `asset` (string, required): Source asset, optionally <asset>@<server>.
- `config_path` (string): Configuration file path override.
- `dst` (string, required): Local destination path.
- `server` (string): Server alias; the default server when omitted.
- `src` (string, required): Source path inside the asset.

### `jms_sftp_relay` (~78 tokens)

Relay a file between two assets (streamed, no local disk).

Input parameters:

- `config_path` (string): Configuration file path override.
- `dst_spec` (string, required): Destination spec <asset>[@<server>]:<path>.
- `src_spec` (string, required): Source spec <asset>[@<server>]:<path>.

### `jms_sftp_upload` (~87 tokens)

Upload a local file to an asset via SFTP.

Input parameters:

- `asset` (string, required): Target asset, optionally <asset>@<server>.
- `config_path` (string): Configuration file path override.
- `dst` (string, required): Destination path inside the asset.
- `server` (string): Server alias; the default server when omitted.
- `src` (string, required): Local source path.

## Diagnostics

Captured diagnostic sections: Provenance. The full working is on the page: https://verifymcp.io/servers/mifazhan-jms-client/jms-client#diagnostics

## Score history

- 2026-11-05: 49
- 2026-11-04: 48
- 2026-11-03: 47
- 2026-11-02: 47
- 2026-11-01: 47
- 2026-10-31: 46
- 2026-10-30: 46
- 2026-10-29: 45
- 2026-10-28: 45
- 2026-10-27: 44
- 2026-10-26: 44
- 2026-10-25: 43
- 2026-10-24: 43
- 2026-10-23: 42
- 2026-10-22: 42
- 2026-10-21: 38
- 2026-10-20: 38
- 2026-10-19: 38
- 2026-10-18: 38
- 2026-10-17: 38
- 2026-10-16: 38
- 2026-10-15: 38
- 2026-10-14: 38
- 2026-10-13: 8
- 2026-10-12: 8
- 2026-10-10: 9

## Common questions

### What is the JumpServer Bastion (jms) MCP server?

JumpServer Bastion (jms) is an MCP server listed in the public MCP registry as io.github.MiFaZhan/jms-client. Run commands, transfer files and browse assets on a JumpServer v4 bastion from your AI assistant. This page covers its MCPB bundle (https://github.com/MiFaZhan/jms-client/releases/download/v0.2.1/jms-client.mcpb).

### Is the JumpServer Bastion (jms) MCP server safe to use?

JumpServer Bastion (jms) scores 49 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 JumpServer Bastion (jms) MCP server expose?

JumpServer Bastion (jms) exposes 15 tools: jms_asset_create, jms_asset_delete, jms_asset_grant, jms_asset_list, jms_asset_permissions, and 10 more. Their descriptions and schemas cost roughly 1,277 tokens of context every time the server is loaded.

### What licence is the JumpServer Bastion (jms) MCP server under?

JumpServer Bastion (jms) declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.

## Links

- Repository: https://github.com/MiFaZhan/jms-client
- Changelog RSS feed: https://verifymcp.io/servers/mifazhan-jms-client/jms-client.xml
- Changelog JSON feed: https://verifymcp.io/servers/mifazhan-jms-client/jms-client.json
- HTML version of this page: https://verifymcp.io/servers/mifazhan-jms-client/jms-client