PabloLec Keyprobe Mcp
- Updated September 10, 2025
- PabloLec/KeyProbe-MCP
KeyProbe MCP is a MCP server that audits certificates and keystores to expose expiry, weak algorithms, and misconfigurations.
About
KeyProbe MCP wraps certificate and keystore auditing so developers shipping HTTPS APIs, SaaS, or CLI tools with TLS can ask the agent to inspect material before cutover or during incidents. It fits the Ship security lane: catching soon-to-expire certs, deprecated ciphers, and keystore layout mistakes that operators often discover only from uptime monitors. The server is remote on Smithery (v1.13.1) with upstream repo on GitHub, aimed at developers who already manage certs manually or via scripts and want conversational triage plus structured findings in the agent. Intermediate complexity reflects needing correct keystore paths, formats, and safe handling of secrets. It is an audit MCP, not a full CA or auto-renewal platform—use it alongside ACME or your cloud provider’s cert manager.
- Audit certificates and keystores via MCP tools
- Surface expiry risks before outages
- Flag weak algorithms and misconfigurations
- KeyProbe-MCP v1.13.1 on Smithery with GitHub source
- Required secret Bearer token for Smithery auth
PabloLec Keyprobe Mcp by the numbers
- Data as of Jul 7, 2026 (Skillselion catalog sync)
claude mcp add --transport http pablolec-keyprobe-mcp https://server.smithery.ai/@PabloLec/keyprobe-mcp/mcp --header "Authorization: Bearer YOUR_TOKEN"Add your badge
Show developers this MCP server is listed on Skillselion. Paste this into your README.
| Transport | HTTP |
|---|---|
| Auth | Required |
| Last updated | September 10, 2025 |
| Repository | PabloLec/KeyProbe-MCP ↗ |
What it does
Audit TLS certificates and keystores from the agent before expiry or weak crypto surprises production.
Who is it for?
Best when you rotate TLS material infrequently and want agent-driven cert health checks in Ship security workflows.
Skip if: Skip if you need fully automated renewal, HSM provisioning, or penetration testing beyond certificate and keystore analysis.
What you get
After install, your agent can run KeyProbe-style audits and return actionable risks on certs and keystores before you ship or rotate keys.
- Expiry and validity findings
- Weak algorithm or misconfiguration reports
- Structured audit output for remediation
By the numbers
- Server version 1.13.1
- GitHub repository: PabloLec/KeyProbe-MCP
- Smithery streamable-http remote with required secret auth header
README.md
Local testing :
npx @modelcontextprotocol/inspector uv run python -m keyprobe.server
Recommended MCP Servers
1Claw VaultHSM-backed vault secrets for AI agents (JIT fetch) plus prompt-injection and threat scanning.2
1passwordMCP server for 1Password service accounts — tools and resources for vaults and credentials18
402sentinel McpAssess an x402 counterparty's risk BEFORE paying: allow/review/block, scored on-chain (Base).1
A2adependencyinspector McpRemote MCP for A2A dependency inspector MCP, structured receipts, audit logs, and reviewer-ready evi
A2a Governance Bridge McpA2A Governance Bridge MCP server.A2aidentitytoll McpRemote MCP for A2A caller identity, scope policy, verdict receipts, and audit history.How it compares
Security audit MCP for certs and keystores, not a certificate authority or agent planning skill.
FAQ
Who is KeyProbe MCP for?
Developers and operators shipping TLS-terminated services who want MCP-driven certificate and keystore audits from Claude Code or similar agents.
When should I use KeyProbe MCP?
Use it in Ship security before launches, after infra changes, or when investigating TLS errors in production.
How do I add KeyProbe MCP to my agent?
Configure the Smithery remote MCP URL with Authorization Bearer {smithery_api_key} (required secret), then enable the server in your MCP client.