Skip to content
MCP server

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

Inspect, verify and issue X.509, CMS, OCSP and time-stamps; key bytes never leave

Runs locally
Install
Pricing
Open source
Platforms
CLI, macOS, Linux
Runs
Locally
Version
1.0.0
Listing updated
3 days ago

Similar MCP servers

About 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 is an open-source MCP server for security. It runs locally on your machine and is started by your AI client.

pkinative-mcp is a PKI toolkit with 34 tools and 7 prompts, built on the author's zero-dependency TypeScript engine that uses Web Crypto for signatures. It inspects certificates, CSRs, CRLs, OCSP responses, CMS SignedData and RFC 3161 time-stamps, decodes ASN.1, PEM and OIDs, builds and validates certificate chains with RFC 5280 path validation, and creates certificates, CSRs, CMS signatures and time-stamp or OCSP requests.

Keys are handled defensively. PKCS#8 and PKCS#12 files are opened as non-extractable Web Crypto keys and never returned, private-key blocks are refused by the encoding tools, and an optional sandbox directory limits file reads and writes with symlink checks. Verdict tools return valid plus reasons rather than an error for a negative result. The README says there is no network access, so revocation checks use CRL and OCSP bytes you supply.

It runs over stdio, with an optional loopback HTTP mode protected by a bearer token. A pinned-time setting makes verdicts reproducible.

Install

Run in a terminal

claude mcp add pkinative-mcp --env PKINATIVE_MCP_HTTP_TOKEN='<PKINATIVE_MCP_HTTP_TOKEN>' --env PKINATIVE_MCP_PASSWORD='<PKINATIVE_MCP_PASSWORD>' -- npx -y pkinative-mcp

Add to claude_desktop_config.json

{
  "mcpServers": {
    "pkinative-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "pkinative-mcp"
      ],
      "env": {
        "PKINATIVE_MCP_HTTP_TOKEN": "<PKINATIVE_MCP_HTTP_TOKEN>",
        "PKINATIVE_MCP_PASSWORD": "<PKINATIVE_MCP_PASSWORD>"
      }
    }
  }
}

Add to ~/.cursor/mcp.json

{
  "mcpServers": {
    "pkinative-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "pkinative-mcp"
      ],
      "env": {
        "PKINATIVE_MCP_HTTP_TOKEN": "<PKINATIVE_MCP_HTTP_TOKEN>",
        "PKINATIVE_MCP_PASSWORD": "<PKINATIVE_MCP_PASSWORD>"
      }
    }
  }
}

Add to .vscode/mcp.json

{
  "servers": {
    "pkinative-mcp": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "pkinative-mcp"
      ],
      "env": {
        "PKINATIVE_MCP_HTTP_TOKEN": "<PKINATIVE_MCP_HTTP_TOKEN>",
        "PKINATIVE_MCP_PASSWORD": "<PKINATIVE_MCP_PASSWORD>"
      }
    }
  }
}

Add to ~/.codeium/windsurf/mcp_config.json

{
  "mcpServers": {
    "pkinative-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "pkinative-mcp"
      ],
      "env": {
        "PKINATIVE_MCP_HTTP_TOKEN": "<PKINATIVE_MCP_HTTP_TOKEN>",
        "PKINATIVE_MCP_PASSWORD": "<PKINATIVE_MCP_PASSWORD>"
      }
    }
  }
}

Add to your client's MCP settings (most use this shape)

{
  "mcpServers": {
    "pkinative-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "pkinative-mcp"
      ],
      "env": {
        "PKINATIVE_MCP_HTTP_TOKEN": "<PKINATIVE_MCP_HTTP_TOKEN>",
        "PKINATIVE_MCP_PASSWORD": "<PKINATIVE_MCP_PASSWORD>"
      }
    }
  }
}

Using several servers? Build one config file with the MCP config generator.

Configuration

  • PKINATIVE_MCP_OUTPUT_DIRAbsolute 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_DIROpt-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_PORTServe 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_TOKENOpt-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_PASSWORDOperator-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_ATPinned 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_BYTESOperator 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_ITERATIONSOperator 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_EXPLOREDOperator 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.

Tools this server provides (15)

Taken from the project documentation; the running server may differ.

convert_pem
Decodes or encodes PEM blocks.
resolve_oid
Names, validates, encodes and decodes object identifiers.
compute_fingerprint
Computes fingerprints and key identifiers.
decode_asn1
Decodes the ASN.1 node tree of a DER object.
encode_asn1
Encodes a JSON node spec to DER.
inspect_certificate
Reports a certificate's fields and extensions.
create_certificate
Issues an X.509 v3 certificate.
encode_x509_structure
Encodes an X.509 building block.
decode_extension
Decodes one certificate extension by OID.
check_certificate_name
Checks a certificate's identity match for a host or IP.
check_certificate_purpose
Checks whether a certificate may be used for a purpose.
inspect_csr
Reports a PKCS#10 request and its proof of possession.
create_csr
Creates a signed PKCS#10 request.
verify_certificate_chain
Returns a trust verdict for a chain with revocation data.
build_certificate_path
Discovers intermediates from a leaf to an anchor.

What it does

Chain verification
Checks a path to your trust anchors with RFC 5280 rules and supplied revocation data.
Certificate issuance
Creates X.509 certificates and CSRs signed by a non-extractable key.
Key safety
Never returns key bytes from PKCS#8 or PKCS#12 files.
Verdict results
Negative verdicts return reasons rather than errors.
ASN.1 tools
Decodes and encodes DER, PEM and OIDs.
No network
Operates offline using only material you supply.

Good for

  • Inspect a certificate's extensions and fingerprints
  • Verify a server certificate chain against your own roots
  • Create a CSR or test certificate without exposing the key
  • Decode an unknown ASN.1 structure

Pricing

Open source

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

Does it make network calls?

No, the README says no network, ever.

Can it reveal private keys?

No, key-bearing files are read by key tools only and never returned or served.

How many tools does it have?

34 tools and 7 prompts.

How does it run?

Over stdio, or optionally over loopback HTTP with a bearer token.

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

Yes. pkinative MCP — X.509, CMS, OCSP, time-stamps and PKCS#12 without a key byte leaving is open source, so you can use and self-host it for free.

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

Run this command in your terminal: claude mcp add pkinative-mcp --env PKINATIVE_MCP_HTTP_TOKEN='<PKINATIVE_MCP_HTTP_TOKEN>' --env PKINATIVE_MCP_PASSWORD='<PKINATIVE_MCP_PASSWORD>' -- npx -y pkinative-mcp

What are the best alternatives to pkinative MCP — X.509, CMS, OCSP, time-stamps and PKCS#12 without a key byte leaving?

The closest alternatives to pkinative MCP — X.509, CMS, OCSP, time-stamps and PKCS#12 without a key byte leaving are IDigiTrust SSL Toolkit, Tracekit MCP gateway, mcp-pin, RugSnare and Toolproof.

Where this comes from

  • Description: written from the project's README.
  • Install steps: from the official MCP Registry entry.

How AIPoweredBot checks servers