CheckPoint MCP Servers Explorer
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
| logging | {} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| extensions | {
"io.modelcontextprotocol/ui": {}
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| echoA | Echo back the provided message. |
| fetch_readmeA | Fetch the README content from CheckPointSW/mcp-servers repository. Returns: The content of the README.md file as text |
| list_chkp_mcp_serversA | List all CheckPoint MCP servers by parsing the README table. Fetches the README from CheckPointSW/mcp-servers repository and extracts server information from the markdown table. Returns: A list of MCP servers with server_name, package_name, and description |
| get_chkp_mcp_server_toolsA | Get all tools from a CheckPoint MCP server. Connects to the specified MCP server via stdio and retrieves all available tools with their metadata including name, description, and input schema. |
| get_chkp_mcp_server_promptsA | Get all prompts from a CheckPoint MCP server. Connects to the specified MCP server via stdio and retrieves all available prompts with their metadata including name, description, and arguments. |
| get_chkp_mcp_server_documentationA | Get NPM package documentation for a CheckPoint MCP server. Fetches the NPM package page and converts it to markdown format, including README, configuration details, environment variables, and usage information. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 6 tools
Most tools have distinct purposes: fetch_raw vs parse list, retrieve tools, prompts, or docs. echo is unrelated but clearly separate. Slight overlap between fetch_readme and list_chkp_mcp_servers since both read the README, but their outputs differ.
The main tools follow a consistent pattern with prefixes like list_chkp_mcp_servers and get_chkp_mcp_server_*. However, 'echo' and 'fetch_readme' deviate from the dominant naming convention, creating minor inconsistency.
With 6 tools, the set is well-scoped for an explorer server focused on discovering and inspecting CheckPoint MCP servers. Each tool adds distinct value without redundancy.
The server covers the exploration lifecycle well: listing servers, fetching tools/prompts/documentation, and raw README access. Minor gaps include lack of direct config retrieval or server metadata details, but these are workarounds via documentation.