mcpbeat Sign in

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

local only

pkinative MCP — X.509, CMS, OCSP, time-stamps and PKCS#12 without a key byte leaving runs on your own machine — the client starts it, so there is no endpoint to ping. 62 installs a week from npm. Last commit 17 Oct 2026.

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

Installs per day peak 139 · avg 8 · +417% w/w
a month agotoday
62
Installs / week
npm · pkinative-mcp
0
Stars
0 open issues
17 Oct 2026
Last commit
2 releases in 90 days
MIT
License
TypeScript

Nothing serious here today

Today is the operative word: we check pkinative MCP — X.509, CMS, OCSP, time-stamps and PKCS#12 without a key byte leaving every 15 minutes and re-read its code on every release. Watch it and you find out the day that stops being true.

Three servers free · no card

Connect this server

This server runs on your own machine — install it with the package manager and the client starts it for you. Package name taken from the official registry entry.

run in your terminal
claude mcp add pkinative-mcp -- npx -y pkinative-mcp
~/Library/Application Support/Claude/claude_desktop_config.json
{
  "mcpServers": {
    "pkinative-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "pkinative-mcp"
      ]
    }
  }
}
~/.codex/config.toml
[mcp_servers.pkinative-mcp]
command = "npx"
args = ["-y", "pkinative-mcp"]
.cursor/mcp.json
{
  "mcpServers": {
    "pkinative-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "pkinative-mcp"
      ]
    }
  }
}
.vscode/mcp.json
{
  "servers": {
    "pkinative-mcp": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "pkinative-mcp"
      ]
    }
  }
}

Optional settings from the registry entry, left out of the block above: PKINATIVE_MCP_OUTPUT_DIR (Absolute path of the one sandbox directory: path inputs are read from it and outputMode='file' outputs are written under it (never overwritten; the real path of every file read and of every parent written must stay inside — a planted symlink or junction is SECURITY_VIOLATION). Key-bearing files (.key .p8 .p12 .pfx) are read by the key tools only, never written, never served as resources. Unset: every tool works on inline PEM / base64 only), PKINATIVE_MCP_CACHE_DIR (Opt-in content-addressed response cache directory (SHA-256 keyed, 1h TTL, 256 MiB LRU, plaintext at rest). Never caches path inputs, file output, a call carrying a password or a signer, a clock-dependent instant, a random serial or nonce, describe_engine or draft_governance_issue), PKINATIVE_MCP_PORT (Serve Streamable HTTP on this loopback port (POST /mcp) instead of stdio (MCP 2026-07-28, stateless, legacy fallback). Unauthenticated unless PKINATIVE_MCP_HTTP_TOKEN is set), PKINATIVE_MCP_HTTP_TOKEN (Opt-in bearer token for the HTTP transport (>= 16 chars, no whitespace; a weaker value refuses to start). When set, /mcp requires 'Authorization: Bearer <token>' or answers 401. Compared constant-time, never logged), PKINATIVE_MCP_PASSWORD (Operator-side password of the encrypted PKCS#8 key or PKCS#12 file the tools open (keeps the secret out of the model transcript). Exclusive with the per-call password input (both at once is VALIDATION_ERROR). Never logged; only its presence is reported at startup), PKINATIVE_MCP_AT (Pinned instant (ISO 8601 or epoch milliseconds) every omitted at / notBefore / signingTime falls back to, for reproducible verdicts and artefacts. Unset: the wall clock (a clock-dependent result is never cached). An invalid value refuses to start), PKINATIVE_MCP_MAX_INPUT_BYTES (Operator ceiling for limits.maxInputBytes and the decoded size of one PKI object (default 67108864 = 64 MiB, the engine default). Integer >= 1024, read once at startup; an invalid value refuses to start. A per-call value above it is refused with LIMIT_CEILING_EXCEEDED), PKINATIVE_MCP_MAX_KDF_ITERATIONS (Operator ceiling for limits.maxKdfIterations and limits.maxPkcs12KdfIterations (default 10000000, the engine default): the CPU bound of a hostile PBES2 key or PKCS#12 file. Integer >= 1, read once at startup; an invalid value refuses to start), PKINATIVE_MCP_MAX_PATHS_EXPLORED (Operator ceiling for limits.maxPathsExplored (default 1000, the engine default): the RFC 5280 section 6 path-building work bound. Integer >= 1, read once at startup; an invalid value refuses to start).

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

same job, measured the same way
zipnative MCP — ZIP creation, inspection, secure extraction & verification
by nizoka

ZIP MCP server: create, inspect, verify, extract, canonicalize, merge, modify. 15 tools

62 installs/wk local only
Ableton MCP Server
by ntworm

Inspect, analyze, and safely edit a running Ableton Live Set on Windows; 97 tools.

local only
AdWeave — Meta Ads MCP Server
by adweave

Meta Ads MCP server with 47 tools for campaigns, creatives, audiences, and insights.

answering
DesktopManager Windows Verification
by evotecit

Inspect and verify Windows x64 desktop apps through a local, read-only-by-default MCP server.

local only
Wayback Machine
by mearman

MCP server and CLI tool for interacting with the Wayback Machine without API keys

891 installs/wk local only
T
Tiled MCP
by fablenator

Inspect, validate and surgically edit Tiled map files (.tmx/.tmj) — byte-preserving, 12 tools.

58 installs/wk local only
Crypto Trends MCP
by trendsmcp

Crypto token and narrative trend volume over time, with growth signals. Free key at trendsmcp.ai

6 tools answering
Spotify
by jamiew

MCP server connecting LLMs to Spotify, with smart-batching and large-playlist tools

1 935 installs/wk local only

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

Answers built from our own checks of this server.

Why is there no uptime for pkinative MCP — X.509, CMS, OCSP, time-stamps and PKCS#12 without a key byte leaving?
pkinative MCP — X.509, CMS, OCSP, time-stamps and PKCS#12 without a key byte leaving runs on your own machine over stdio — there is no network address to reach, so uptime cannot be measured for it by anyone. What can be measured is adoption: the npm package pkinative-mcp was installed 62 times last week.
How do I connect pkinative MCP — X.509, CMS, OCSP, time-stamps and PKCS#12 without a key byte leaving?
Copy the ready config from this page. We generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each in the form that client actually reads. It runs locally, so the command pulls pkinative-mcp straight from npm; nothing to host, nothing to sign up for.
How many people use pkinative MCP — X.509, CMS, OCSP, time-stamps and PKCS#12 without a key byte leaving?
The npm package pkinative-mcp was installed 62 times in the last week. Week over week that is +417%. We show installs rather than GitHub stars on purpose: a star is a bookmark, an install is someone actually running it.
Is pkinative MCP — X.509, CMS, OCSP, time-stamps and PKCS#12 without a key byte leaving open source?
Yes — it is published under the MIT licence, written in TypeScript and 0 stars on GitHub. The source link is on this page, so you can read exactly what it does with your data before you connect it.