Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

JumpServer Bastion (jms)

MCPB · JMS-CLIENT.MCPB

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

Available components

+4 this week 49 Trust /100

Last scanned (24 minutes ago)

Scores higher than 79% of MCPB servers

Category Cloud Infrastructure

Trust breakdown (7 categories)

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
  • 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.Unverified
  • 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).Unverified
  • Install-script risk not yet assessed.Unverified
  • 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).Unverified
Provenance & Transparency45
Schema Quality & AI Usability71
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 1277 tokens (~85/item across 15 items; 15 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management73
  • Stability observed for 22 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; "jms_asset_delete" 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 15 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a current MCP spec version (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.

Changelog

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.

  • 5 Nov 26 +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.

  • 4 Nov 26 +1
    • Schema quality: 75 → 85 ▼ functional
  • 1 Nov 26 +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.

  • 31 Oct 26 0
    • Security disclosure: unverified → fail ▼ functional
  • 30 Oct 26 +1
    • Security disclosure: fail → unverified ▼ functional
  • 28 Oct 26 +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.

  • 26 Oct 26 +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.

  • 24 Oct 26 +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.

Diagnostics

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 5 Nov 2026 · Analysed mcpb/https://github.com/MiFaZhan/jms-client/releases/download/v0.2.1/jms-client.mcpb

Provenance No attestation

The registry publishes no build provenance for this version, so there is nothing to verify.

Result No attestation
Ecosystem mcpb
Reason No attestation published

Background: How many MCP packages publish verified provenance →

MCP tools · 15 exposed · ~1,277 tokens

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 →

Tool Tokens
jms_asset_create ~182

Create a host asset on a JumpServer.

NameTypeReqDescription
accountstring–Account display name to attach; without one the asset cannot be connected to.
addressstringyesReachable address of the target host.
commentstring–Free-text note stored with the asset.
config_pathstring–Configuration file path override.
namestringyesAsset name; must be unique on the server.
node_idstring–Asset node id; the default node is used when omitted.
passwordstring–Account password; sent in the request and never stored locally.
platform_idinteger–Platform id; 0 means Linux.
serverstring–Server alias; the default server when omitted.
usernamestring–Login name on the target host; defaults to the account name.

No output schema declared.

No examples provided.

jms_asset_delete ~59

Delete a JumpServer asset. This cannot be undone.

NameTypeReqDescription
config_pathstring–Configuration file path override.
serverstring–Server alias; the default server when omitted.
targetstringyesAsset name or id.

No output schema declared.

No examples provided.

jms_asset_grant ~165

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

NameTypeReqDescription
accountsstring–Accounts to allow; @ALL when omitted.
actionsstring–Actions to allow; connect when omitted.
commentstring–Free-text note.
config_pathstring–Configuration file path override.
namestring–Permission name; defaults to grant-<asset>.
protocolsstring–Protocols to allow; all when omitted.
serverstring–Server alias; the default server when omitted.
targetstringyesAsset name or id to grant.
usersstring–User ids to grant; the authenticated user when omitted.

No output schema declared.

No examples provided.

jms_asset_list ~56

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

NameTypeReqDescription
config_pathstring–Configuration file path override.
serverstring–Server alias; the default server when omitted.

No output schema declared.

No examples provided.

jms_asset_permissions ~66

List JumpServer asset permissions, optionally restricted to one asset.

NameTypeReqDescription
config_pathstring–Configuration file path override.
serverstring–Server alias; the default server when omitted.
targetstring–Asset name or id; lists every permission when omitted.

No output schema declared.

No examples provided.

jms_asset_revoke ~69

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

NameTypeReqDescription
config_pathstring–Configuration file path override.
serverstring–Server alias; the default server when omitted.
targetstringyesPermission name or id.

No output schema declared.

No examples provided.

jms_asset_show ~62

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

NameTypeReqDescription
config_pathstring–Configuration file path override.
serverstring–Server alias; the default server when omitted.
targetstringyesAsset name or id.

No output schema declared.

No examples provided.

jms_asset_update ~89

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

NameTypeReqDescription
addressstring–New address.
commentstring–New comment.
config_pathstring–Configuration file path override.
new_namestring–New asset name.
serverstring–Server alias; the default server when omitted.
targetstringyesAsset name or id.

No output schema declared.

No examples provided.

jms_config_list ~34

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

NameTypeReqDescription
config_pathstring–Configuration file path override.

No output schema declared.

No examples provided.

jms_exec ~117

Execute a command on an asset and return its output.

NameTypeReqDescription
accountstring–Account override.
assetstringyesAsset name or address, optionally <asset>@<server>.
commandstringyesShell command to run.
config_pathstring–Configuration file path override.
protocolstring–Protocol override.
serverstring–Server alias; the default server when omitted.
timeoutinteger–Timeout in seconds; 300 when omitted (override with JMS_MCP_EXEC_TIMEOUT).

No output schema declared.

No examples provided.

jms_ls ~60

List or search authorized assets on a JumpServer.

NameTypeReqDescription
config_pathstring–Configuration file path override.
keywordstring–Search keyword; lists everything when omitted.
serverstring–Server alias; the default server when omitted.

No output schema declared.

No examples provided.

jms_resolve_asset ~63

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

NameTypeReqDescription
assetstringyesAsset name or address.
config_pathstring–Configuration file path override.
serverstring–Server alias; the default server when omitted.

No output schema declared.

No examples provided.

jms_sftp_download ~90

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

NameTypeReqDescription
assetstringyesSource asset, optionally <asset>@<server>.
config_pathstring–Configuration file path override.
dststringyesLocal destination path.
serverstring–Server alias; the default server when omitted.
srcstringyesSource path inside the asset.

No output schema declared.

No examples provided.

jms_sftp_relay ~78

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

NameTypeReqDescription
config_pathstring–Configuration file path override.
dst_specstringyesDestination spec <asset>[@<server>]:<path>.
src_specstringyesSource spec <asset>[@<server>]:<path>.

No output schema declared.

No examples provided.

jms_sftp_upload ~87

Upload a local file to an asset via SFTP.

NameTypeReqDescription
assetstringyesTarget asset, optionally <asset>@<server>.
config_pathstring–Configuration file path override.
dststringyesDestination path inside the asset.
serverstring–Server alias; the default server when omitted.
srcstringyesLocal source path.

No output schema declared.

No examples provided.

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.

mcpb · jms-client.mcpb

Download bundle

Check the download matches the SHA-256 the MCP registry declares before you open it. If it does not match, do not open the file.

SHA-256

cf06d02334893ddb5f9f096387c35b717f78bace2c8d4188586a0f1a0cbc1c40

macOS / Linux

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

Windows (PowerShell)

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

Run it in the folder you saved the bundle to, then open the file with an MCPB-capable host such as Claude Desktop.

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.