checkpoint-security-mcp-servers

Created By
ngardinera year ago
Anthropic MCP servers to enable AI agent integration and autonomous defense for Check Point firewalls, endpoint, and more.
Overview

What is Checkpoint Security MCP Servers?

Checkpoint Security MCP Servers are open-source implementations of Anthropic's Model Context Protocol (MCP) designed to enable AI agent integration and autonomous defense for Check Point security products, including firewalls and endpoints.

How to use Checkpoint Security MCP Servers?

To use the MCP servers, clone the repository, set up a Python virtual environment, install dependencies, configure Check Point API access, and run the server script to start the MCP server. Connect an MCP-compatible AI application to interact with the server.

Key features of Checkpoint Security MCP Servers?

  • Integration of AI agents with Check Point security products.
  • Standardized communication through the Model Context Protocol (MCP).
  • Initial implementation of tools for firewall management and endpoint actions.

Use cases of Checkpoint Security MCP Servers?

  1. Automating firewall management tasks.
  2. Enhancing security operations with AI-driven responses.
  3. Facilitating seamless integration of AI applications with Check Point security infrastructure.

FAQ from Checkpoint Security MCP Servers?

  • Is this project officially affiliated with Check Point?

No, this is an independent community project and is not officially endorsed by Check Point Software Technologies.

  • What programming language is used?

The project is implemented in Python.

  • How can I contribute to the project?

You can contribute by forking the repository, creating a new branch, making changes, and submitting a pull request.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
ngardiner
Star
0
Language
Python
License
MIT license
Category
security
Tags

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

a day ago