🧩

pkinative MCP — X.509, CMS, OCSP, time-stamps and PKCS#12 without a key byte leaving

Name: pkinative MCP — X.509, CMS, OCSP, time-stamps and PKCS#12 without a key byte leaving
Author: io.github.Nizoka

API key required

by @io.github.Nizoka

GitHub

Visit website GitHub

PKI MCP server: inspect, verify, issue, sign X.509, CSR, CRL, OCSP, CMS, TSP, PKCS#12. 34 tools

To add pkinative MCP — X.509, CMS, OCSP, time-stamps and PKCS#12 without a key byte leaving to Claude, run the install command below or copy the ready-made config for Claude Code, Claude Desktop, Cursor and VS Code further down. Restart your client after adding it and its tools show up in your next conversation. It needs 9 environment variables, listed below.

DevTools

Install

npx -y pkinative-mcp@1.0.0

Environment variables

PKINATIVE_MCP_OUTPUT_DIRSet in your MCP config

PKINATIVE_MCP_CACHE_DIRSet in your MCP config

PKINATIVE_MCP_PORTSet in your MCP config

PKINATIVE_MCP_HTTP_TOKENSet in your MCP config

PKINATIVE_MCP_PASSWORDSet in your MCP config

PKINATIVE_MCP_ATSet in your MCP config

PKINATIVE_MCP_MAX_INPUT_BYTESSet in your MCP config

PKINATIVE_MCP_MAX_KDF_ITERATIONSSet in your MCP config

PKINATIVE_MCP_MAX_PATHS_EXPLOREDSet in your MCP config

Install with your client

Terminal

claude mcp add pkinative-mcp-x-509-cms-ocsp-time-stamps-and-pkcs-12-without-a-key-byte-leaving --env PKINATIVE_MCP_OUTPUT_DIR=<YOUR_PKINATIVE_MCP_OUTPUT_DIR> --env PKINATIVE_MCP_CACHE_DIR=<YOUR_PKINATIVE_MCP_CACHE_DIR> --env PKINATIVE_MCP_PORT=<YOUR_PKINATIVE_MCP_PORT> --env PKINATIVE_MCP_HTTP_TOKEN=<YOUR_PKINATIVE_MCP_HTTP_TOKEN> --env PKINATIVE_MCP_PASSWORD=<YOUR_PKINATIVE_MCP_PASSWORD> --env PKINATIVE_MCP_AT=<YOUR_PKINATIVE_MCP_AT> --env PKINATIVE_MCP_MAX_INPUT_BYTES=<YOUR_PKINATIVE_MCP_MAX_INPUT_BYTES> --env PKINATIVE_MCP_MAX_KDF_ITERATIONS=<YOUR_PKINATIVE_MCP_MAX_KDF_ITERATIONS> --env PKINATIVE_MCP_MAX_PATHS_EXPLORED=<YOUR_PKINATIVE_MCP_MAX_PATHS_EXPLORED> -- npx -y pkinative-mcp@1.0.0

Run this in a terminal to add the server to Claude Code.

What this does

pkinative MCP — X.509, CMS, OCSP, time-stamps and PKCS#12 without a key byte leaving exposes a set of tools to Claude over the Model Context Protocol. After you add it to claude_desktop_config.json (snippet above) and restart Claude Desktop, those tools become callable inside any conversation.

Requirements

This server needs the following environment variables to be set before it can run:

PKINATIVE_MCP_OUTPUT_DIR
PKINATIVE_MCP_CACHE_DIR
PKINATIVE_MCP_PORT
PKINATIVE_MCP_HTTP_TOKEN
PKINATIVE_MCP_PASSWORD
PKINATIVE_MCP_AT
PKINATIVE_MCP_MAX_INPUT_BYTES
PKINATIVE_MCP_MAX_KDF_ITERATIONS
PKINATIVE_MCP_MAX_PATHS_EXPLORED

Set these via the env object in your MCP config (see claude_desktop_config.json snippet above).

Frequently asked questions

How do I install pkinative MCP — X.509, CMS, OCSP, time-stamps and PKCS#12 without a key byte leaving?

Run the Claude Code command in the install section to add pkinative MCP — X.509, CMS, OCSP, time-stamps and PKCS#12 without a key byte leaving to Claude Code, or copy the ready-made config for your client from the install section on this page. Restart your client afterwards and the tools appear in your next conversation.

Which clients work with pkinative MCP — X.509, CMS, OCSP, time-stamps and PKCS#12 without a key byte leaving?

This page carries setup and config for Claude Code, Claude Desktop, Cursor and VS Code. Any other MCP client that accepts a standard server config can connect to pkinative MCP — X.509, CMS, OCSP, time-stamps and PKCS#12 without a key byte leaving as well.

Does pkinative MCP — X.509, CMS, OCSP, time-stamps and PKCS#12 without a key byte leaving need an API key?

Yes. Before it can run, set these environment variables: PKINATIVE_MCP_OUTPUT_DIR, PKINATIVE_MCP_CACHE_DIR, PKINATIVE_MCP_PORT, PKINATIVE_MCP_HTTP_TOKEN, PKINATIVE_MCP_PASSWORD, PKINATIVE_MCP_AT, PKINATIVE_MCP_MAX_INPUT_BYTES, PKINATIVE_MCP_MAX_KDF_ITERATIONS, PKINATIVE_MCP_MAX_PATHS_EXPLORED. They go in the env block of your MCP config.

Imported from the Official MCP Registry. The details above come from the registry entry; the maker can claim this listing to correct them, add docs, and see its traffic.

Is this your MCP server?

Claim this listing to see its traffic, fix details yourself, and skip the review queue on future updates.

Add this badge to your README

Show visitors this server is listed in the ClaudeRules directory. The badge links straight to this listing.

Markdown

[![Listed on clauderules.net](https://clauderules.net/api/badge/io-github-nizoka-pkinative-mcp)](https://clauderules.net/mcp/io-github-nizoka-pkinative-mcp)

HTML

<a href="https://clauderules.net/mcp/io-github-nizoka-pkinative-mcp" target="_blank" rel="noopener noreferrer"><img src="https://clauderules.net/api/badge/io-github-nizoka-pkinative-mcp" alt="Listed on clauderules.net" /></a>

More DevTools MCP servers

🔌

GitHub

Connect AI assistants to GitHub - manage repos, issues, PRs, and workflows through natural language.

🔌

Serena MCP: the IDE for your agent

A powerful toolkit for coding, providing semantic retrieval and editing capabilities.

🔌

Figma-Context-MCP

Give your coding agent access to your Figma data. Implement designs in any framework in one-shot.

🔌

Inbox Zero

Search Gmail and Outlook, save drafts, manage email rules, and view email stats.

Alternatives to pkinative MCP — X.509, CMS, OCSP, time-stamps and PKCS#12 without a key byte leaving Best MCP servers for Git & Code Hosting Best MCP servers for GitHub