PabloLec Keyprobe MCP

What PabloLec-keyprobe-mcp MCP server does

PabloLec-keyprobe-mcp MCP server is intended for certificate and keystore auditing. Its documented focus is identifying three categories of issues: certificates that may expire, algorithms that are weak, and configuration problems in certificate or keystore material.

This makes the server relevant to security review workflows involving cryptographic assets. The supplied description does not specify whether it reads files, accepts inline values, connects to another service, or supports a particular certificate or keystore format. It also does not list the individual MCP tool names or their input parameters.

How it works

The repository provides a Python module named keyprobe.server. The local testing command starts that module with uv run and places MCP Inspector in front of it:

npx @modelcontextprotocol/inspector uv run python -m keyprobe.server

In this arrangement, npx launches the inspector, while uv run executes the Python server module. The command is described as a local-testing workflow, so it is useful for checking that the server starts and for examining its MCP behavior during development.

The available material does not describe the inspection request format, the server transport beyond its use with MCP Inspector, result schemas, or how audit targets are supplied. Those details should be verified in the repository before building an automated workflow around the server.

Setup and configuration

PabloLec-keyprobe-mcp can be tested locally with the command shown above. This requires the tooling referenced by that command, including npx and uv, as well as the repository's Python package and its keyprobe.server module.

No environment variables, command-line options, configuration files, installation steps, or credential requirements are documented in the supplied excerpt. Do not assume that configuration is unnecessary; the available material only establishes the documented local launch command.

Tools and capabilities

The documented audit scope covers:

• Checking certificates for expiry risks.
• Finding weak cryptographic algorithms.
• Detecting certificate or keystore misconfigurations.

The source material does not identify separate tool names, parameters, return values, supported file types, or remediation operations. In particular, it does not establish that the server can renew certificates, modify keystores, generate keys, or apply fixes. PabloLec-keyprobe-mcp should therefore be evaluated as an auditing component unless the repository documents additional behavior.

Limitations and notes

The supplied information is limited to a short description and a local testing command. It does not state which certificate and keystore formats are supported, whether remote assets can be inspected, how secrets are handled, or which MCP clients have been tested. It also does not provide a license declaration.

Before deployment, confirm the supported inputs, security boundaries, output structure, and handling of private key material. For an initial evaluation, run PabloLec-keyprobe-mcp locally through MCP Inspector and inspect the exposed capabilities and responses. This is the clearest documented path for validating how the server fits a certificate or keystore review workflow.