Threat Prevention MCP Server
@chkp/threat-prevention-mcp
npm
v1.5.8
Source verified
Published by checkpointsw — publish provenance cryptographically ties this package to that repository. That is proof of origin, not an official vendor package.
Threat Prevention MCP server for Check Point products
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:
| Points | Adoption-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 25
Each tool and what it can reach — statically extracted from the published source.
check_cve_protectionno sensitive capabilityshow_exception_groupno sensitive capabilityshow_exception_groupsno sensitive capabilityshow_ips_protection_extended_attributeno sensitive capabilityshow_ips_protection_extended_attributesno sensitive capabilityshow_ips_statusno sensitive capabilityshow_ips_update_scheduleno sensitive capabilityshow_threat_advanced_settingsno sensitive capabilityshow_threat_indicatorno sensitive capabilityshow_threat_indicatorsno sensitive capability
Show 15 more tools ↓
show_threat_ioc_feedno sensitive capabilityshow_threat_ioc_feedsno sensitive capabilityshow_threat_layerno sensitive capabilityshow_threat_layersno sensitive capabilityshow_threat_profileno sensitive capabilityshow_threat_profilesno sensitive capabilityshow_threat_protectionno sensitive capabilityshow_threat_protectionsno sensitive capabilityshow_threat_ruleno sensitive capabilityshow_threat_rule_exception_rulebaseno sensitive capabilityshow_threat_rulebaseno sensitive capabilitythreat-prevention__initno sensitive capabilitythreat-prevention__show_gateways_and_serversno sensitive capabilitythreat-prevention__show_objectno sensitive capabilitythreat-prevention__show_objectsno sensitive capability
What this scan could not see
- Tools were statically extracted from the published source (25 recovered), not enumerated from a running server. Tool-poisoning, Unicode-smuggling, capability and toxic-flow analysis ran on this inferred surface, but a mis-parsed registration could be missed or mis-attributed, so tool-derived findings are capped below “confirmed”. To grade the real runtime surface, scan the running server: --command "npx -y <package>".
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.
| Version | Score | Findings | Engine | Scanned |
|---|---|---|---|---|
v1.5.8 latest |
A 94/100 | 1 | 1.13.0 | 2026-09-07 |
v1.5.7 |
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.
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/threat-prevention-mcp --onlineMore in Analytics & Monitoring
Public-safe MCP admin discovery contract descriptors and response builders.
Pokemon Champions battle advisor MCP server
Airflow MCP server — DAG list, runs, task instances, log tails, trigger and clear over the Airflow REST API
MCP analytics wrapper SDK that instruments MCP tool declarations with telemetry.
AI-ready GIS, geofencing, DataSynch, CRM, inventory, routing, APIs, telemetry and workflows.
AI-native social listening. Monitor buying signals and run GTM workflows via natural language.