Quantum Management MCP Server

@chkp/quantum-management-mcp npm v1.4.10 Source verified

Published by checkpointsw — publish provenance cryptographically ties this package to that repository. That is proof of origin, not an official vendor package.

Official MCP server for Check Point Quantum Management

Trust grade
A
94/100
Last scanned get badge →
Trust
A · 94/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.
Share this Trust Score
𝕏 Share LinkedIn Reddit
A Why this grade threat 100 − adoption risk = 94/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 − 6 = 94. 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

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 1

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

In the server's implementation (`dist/index.js:25`): 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 { exec } from "child_process"; import { promisify } from "util"; import * as fs2 from "fs"; import * as path fr

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/index.js

Tools 54

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

  • show_access_rulebaseingests untrusted input
  • find_zero_hits_rulesno sensitive capability
  • management__initno sensitive capability
  • management__show_gateways_and_serversno sensitive capability
  • management__show_objectno sensitive capability
  • management__show_objectsno sensitive capability
  • show_access_layerno sensitive capability
  • show_access_layersno sensitive capability
  • show_access_point_namesno sensitive capability
  • show_access_ruleno sensitive capability
Show 44 more tools ↓
  • show_access_sectionno sensitive capability
  • show_address_rangesno sensitive capability
  • show_application_site_categoriesno sensitive capability
  • show_application_site_groupsno sensitive capability
  • show_application_sitesno sensitive capability
  • show_cluster_memberno sensitive capability
  • show_cluster_membersno sensitive capability
  • show_dns_domainsno sensitive capability
  • show_domainsno sensitive capability
  • show_dynamic_objectsno sensitive capability
  • show_groupsno sensitive capability
  • show_hostsno sensitive capability
  • show_lsm_clusterno sensitive capability
  • show_lsm_clustersno sensitive capability
  • show_lsm_gatewayno sensitive capability
  • show_lsm_gatewaysno sensitive capability
  • show_mdssno sensitive capability
  • show_multicast_address_rangesno sensitive capability
  • show_nat_rulebaseno sensitive capability
  • show_nat_sectionno sensitive capability
  • show_networksno sensitive capability
  • show_packagesno sensitive capability
  • show_security_zonesno sensitive capability
  • show_service_groupsno sensitive capability
  • show_services_icmpno sensitive capability
  • show_services_icmp6no sensitive capability
  • show_services_tcpno sensitive capability
  • show_services_udpno sensitive capability
  • show_simple_clusterno sensitive capability
  • show_simple_clustersno sensitive capability
  • show_simple_gatewayno sensitive capability
  • show_simple_gatewaysno sensitive capability
  • show_tagsno sensitive capability
  • show_time_groupsno sensitive capability
  • show_unused_objectsno sensitive capability
  • show_vpn_communities_meshedno sensitive capability
  • show_vpn_communities_remote_accessno sensitive capability
  • show_vpn_communities_starno sensitive capability
  • show_vpn_community_meshedno sensitive capability
  • show_vpn_community_remote_accessno sensitive capability
  • show_vpn_community_starno sensitive capability
  • show_wildcardsno sensitive capability
  • simulate_packetno sensitive capability
  • where_usedno sensitive capability

What this scan could not see

Versions 2

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.4.10 latest A 94/100 1 1.13.0 2026-09-07
v1.4.9 A 94/100 1 1.12.1 2026-08-20

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 · 94/100
Markdown (GitHub README)
[![MCP Trust Score](https://mcptrustchecker.com/registry/chkp-quantum-management-mcp/badge.svg)](https://mcptrustchecker.com/registry/chkp-quantum-management-mcp)
HTML
<a href="https://mcptrustchecker.com/registry/chkp-quantum-management-mcp"><img src="https://mcptrustchecker.com/registry/chkp-quantum-management-mcp/badge.svg" alt="MCP Trust Score" height="20"></a>
Prefer shields.io styling? Point it at https://mcptrustchecker.com/registry/chkp-quantum-management-mcp/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 @chkp/quantum-management-mcp --online

Use the free API → How scoring works

More in Business & CRM