AgentHubAgentHub

pkinative MCP MCP Setup & Guide

MCP ServerMCP RegistryOfficial

io.github.Nizoka/pkinative-mcp · v1.0.0

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

Copy the install config on this page first, then verify docs and permissions upstream.

Overview

PKI MCP server: inspect, verify, issue, sign X.509, CSR, CRL, OCSP, CMS, TSP, PKCS#12. 34 tools pkinative MCP — X.509, CMS, OCSP, time-stamps and PKCS#12 without a key byte leaving is a MCP Server listed from MCP Registry. Transports: stdio. This page includes an overview, setup tutorial, install commands, and use cases for Trae, Tongyi Lingma, Cursor, Claude Code, and VS Code.

Use cases

AgentHub Verified AvailabilityTested & Ready

Automated pipeline validated install commands, protocol & client compatibility

Verified At2026-10-18
Install Snippets TestedCLI & JSON config syntax verified
Protocol Handshake ReadyComplies with JSON-RPC 2.0 specifications
Origin Registry ActiveSourced from official-mcp-registry
Verified ClientsClaude Code、Claude Desktop、Cursor 等
Security Tier: A+ 级 · 官方认证推荐 (A+)·Maintained by official/verified teams, audited for standard MCP protocol compliance.

Copy by platform

Choose your platform

  1. Open or create .cursor/mcp.json in your project root
  2. Click Copy config and paste; merge only this mcpServers entry if others exist
  3. Replace <placeholders> in env with real secrets (see Environment variables below)
  4. Save, then Cmd+Shift+P → Reload Window

Pre-fill Environment Variables (Optional)

secret
secret
Privacy Guarantee: Keys are replaced 100% locally in your browser memory and are NEVER uploaded or stored on any server.
Click to copy snippet
{
  "mcpServers": {
    "pkinative-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "pkinative-mcp"
      ]
    }
  }
}

Setup tutorial

  1. Open the pkinative MCP — X.509, CMS, OCSP, time-stamps and PKCS#12 without a key byte leaving page and confirm this MCP Server (source: MCP Registry).
  2. Copy the Cursor, Claude Code, or VS Code snippet.
  3. Merge it into mcpServers and replace env placeholders with real secrets.
  4. Reload the window, then call the MCP tools from your agent chat.

Install commands

Install commands and setup steps are in the HTML so search engines and no-JS browsers can read them without running client JavaScript.

Claude Code (local)

  1. Install Claude Code CLI
  2. Copy the command below, replace <placeholders> with real env values, then run in terminal
  3. See Environment variables below if listed
claude mcp add pkinative-mcp -- npx -y pkinative-mcp

Cursor — .cursor/mcp.json (local)

  1. Open or create .cursor/mcp.json in your project root
  2. Click Copy config and paste; merge only this mcpServers entry if others exist
  3. Replace <placeholders> in env with real secrets (see Environment variables below)
  4. Save, then Cmd+Shift+P → Reload Window
{
  "mcpServers": {
    "pkinative-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "pkinative-mcp"
      ]
    }
  }
}

VS Code — .vscode/mcp.json (local)

  1. Install GitHub Copilot in VS Code with MCP support
  2. Open or create .vscode/mcp.json in your project root
  3. Click Copy config and paste; merge only this mcpServers entry if others exist
  4. Replace <placeholders> in env with real secrets
  5. Save and Developer: Reload Window
{
  "mcpServers": {
    "pkinative-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "pkinative-mcp"
      ]
    }
  }
}

Claude Desktop — claude_desktop_config.json (local)

  1. Open Claude Desktop claude_desktop_config.json (see remote guide for paths)
  2. Click Copy config and merge under mcpServers
  3. Replace <placeholders> in env with real secrets
  4. Fully quit and restart Claude Desktop
{
  "mcpServers": {
    "pkinative-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "pkinative-mcp"
      ]
    }
  }
}

Trae — .trae/mcp.json (local)

  1. Trae → Settings → MCP, or edit .trae/mcp.json / global mcp.json
  2. Click Copy config and merge mcpServers
  3. Replace <placeholders> in env with real secrets
  4. Save and reload Trae
{
  "mcpServers": {
    "pkinative-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "pkinative-mcp"
      ]
    }
  }
}

Cherry Studio — MCP settings (local)

  1. Cherry Studio → Settings → MCP Servers → Add (STDIO)
  2. Or import JSON: click Copy config and merge mcpServers
  3. Replace <placeholders> in env; ensure Node.js / uv (npx, uvx) are installed
  4. Enable the server and check tools load
{
  "mcpServers": {
    "pkinative-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "pkinative-mcp"
      ]
    }
  }
}

Tongyi Lingma — MCP config (local)

  1. Lingma Settings → MCP → + → STDIO or config file
  2. Click Copy config and merge mcpServers
  3. Replace <placeholders> in env; need Node.js 18+ (npx) or uv (uvx)
  4. Confirm connected before using tools in agent chat
{
  "mcpServers": {
    "pkinative-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "pkinative-mcp"
      ]
    }
  }
}

Windsurf — mcp_config.json (local)

  1. Edit ~/.codeium/windsurf/mcp_config.json
  2. Click Copy config and merge mcpServers (stdio same as Cursor)
  3. Replace <placeholders> in env, save, refresh Cascade
{
  "mcpServers": {
    "pkinative-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "pkinative-mcp"
      ]
    }
  }
}

Cline — MCP Servers (local)

  1. Cline panel → Settings → MCP Servers
  2. Click Copy config and merge
  3. Replace <placeholders> in env, then save
{
  "mcpServers": {
    "pkinative-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "pkinative-mcp"
      ]
    }
  }
}

WorkBuddy — .workbuddy/mcp.json (local)

  1. Edit ~/.workbuddy/mcp.json (user) or project .workbuddy/mcp.json
  2. Or Plugins → MCP Servers → Configure MCP and paste the JSON below
  3. Replace <placeholders> in env; on Windows prefer absolute paths for command/scripts
  4. Save, restart WorkBuddy, confirm connector status is green
{
  "mcpServers": {
    "pkinative-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "pkinative-mcp"
      ]
    }
  }
}

Troubleshooting & Common ErrorsFAQ

Common connection errors and verified fixes for pkinative MCP — X.509, CMS, OCSP, time-stamps and PKCS#12 without a key byte leaving

Getting 'connection closed' or exit code 1 in Cursor / Claude Code for pkinative MCP — X.509, CMS, OCSP, time-stamps and PKCS#12 without a key byte leaving?

Usually caused by missing runtime paths or IDE environment inheritance. Fix steps: 1. Verify Node.js 18+ (npx) or Python 3.10+ (uvx) is installed; 2. Run 'which npx' or 'which uvx' in terminal, and replace 'command' with absolute path; 3. Reload or restart the client window after modifying config.

Fix Snippet
# Check binary path in terminal:
which npx
node -v
Getting 'spawn npx ENOENT' or 'command not found'?

The editor background process does not inherit your full terminal PATH. Solution: Globally install the package, or set the absolute binary path (e.g. C:\Program Files\nodejs\npx.cmd on Windows, or /usr/local/bin/npx on macOS).

Missing required environment variable or authentication failure?

pkinative MCP — X.509, CMS, OCSP, time-stamps and PKCS#12 without a key byte leaving requires 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). Ensure you have added valid keys under the 'env' object in your config file without trailing whitespace.

Fix Snippet
// .cursor/mcp.json 或 claude_desktop_config.json
{
  "env": {
    "API_KEY": "your_actual_key_here"
  }
}

Tool Mock Playground

Sandbox

pkinative MCP — X.509, CMS, OCSP, time-stamps and PKCS#12 without a key byte leaving Tool Interface Simulation · Preview tool schema & outputs without local runtime

Sandbox Ready
fn: pkinative_mcpExecute the core tool interface of pkinative MCP — X.509, CMS, OCSP, time-stamps and PKCS#12 without a key byte leaving
Request ArgumentsJSON Schema
{
  "target": "pkinative MCP — X.509, CMS, OCSP, time-stamps and PKCS#12 without a key byte leaving",
  "action": "execute",
  "options": {
    "mode": "standard",
    "timeoutMs": 5000
  }
}
💡Parameters generated dynamically by Agent runtime
Agent Tool Output

Click 'Run Mock' above

to preview the raw response returned to the LLM

Env: AgentHub Virtual SandboxJSON-RPC 2.0

Decision Guide: Why & When to Use

Assess suitability before installing to save trial-and-error time

Best Suited For
  • PR review
  • Changelog generation
  • Cross-repo issue search
When NOT to Use
  • Replacing human security audit
  • Unauthorized repo access
Recommended Workflow Pairing:View Scenario →

pkinative MCP — X.509, CMS, OCSP, time-stamps and PKCS#12 without a key byte leaving + Scenario Prompt → Complete Agent Automation

MCP hands-on: install to visible results

Follow the full lab (expected UI/output + contrast checks). After installing this item, verify with the tutorial prompts.

Open tutorial →

Related resources

Often paired with

中文公文写作

v2.0.35

SkillClawHub9.7k

io.clawhub.gongyu0918-debug/chinese-official-writing

用于中文公文、事务性材料和新闻稿件的起草、改写、压缩、润色、审校、文种核对、去口语化、降 AI 味及 Word 格式处理,适用于机关、企事业单位、学校和新闻机构。涵盖申请、请示、报告、通知、通告、意见、决定、决议、议案、公报、命令、函、复函、批复、说明、方案、纪要、公告、公示、通报、制度、规定、办法、细则、操作规程、工作要点、总结、调研、讲话、致辞、主持词、述职、可研、审查材料、技术需求、新闻消息、编者按、新闻评论,以及采购、整改、反馈和 AI 算力等场景。

source

ai-insurance-advisor

v2.0.163

SkillClawHub8.7k

io.clawhub.mnetfairy/ai-insurance-advisor

中国大陆保险顾问。本 skill 仅覆盖 6 项实际实现的能力:保险需求分析(needs_analyzer.py)、产品对比(premium_calculator.py + 本地 products.json)、保费计算(premium_calculator.py)、方案设计(plan_designer.py)、保险知识问答(insurance-knowledge.md)、合规要点提示(compliance.md)。不提供核保预审、理赔代办、朋友圈/营销文案生成、培训话术、代理人展业工具等能力——这些场景请转人工或调用专业服务。

source

Keep exploring AgentHub

Most people compare similar tools or check scenario guides before installing—start here.

Listing badge: put AgentHub on your site

Copy either snippet into your project homepage, docs, or GitHub README. The badge is a hotlinked SVG — nothing to host — and it links back to this page so visitors can find the install steps.

PreviewListed on AgentHub: pkinative MCP — X.509, CMS, OCSP, time-stamps and PKCS#12 without a key byte leaving
HTML
<a href="https://myagenthub.cn/p/io.github.Nizoka/pkinative-mcp" title="Listed on AgentHub: pkinative MCP — X.509, CMS, OCSP, time-stamps and PKCS#12 without a key byte leaving" target="_blank" rel="noopener">
  <img src="https://myagenthub.cn/badge/io.github.Nizoka/pkinative-mcp?lang=en" alt="Listed on AgentHub: pkinative MCP — X.509, CMS, OCSP, time-stamps and PKCS#12 without a key byte leaving" height="20" style="border:0"/>
</a>
Markdown (GitHub README)
[![Listed on AgentHub: pkinative MCP — X.509, CMS, OCSP, time-stamps and PKCS#12 without a key byte leaving](https://myagenthub.cn/badge/io.github.Nizoka/pkinative-mcp?lang=en)](https://myagenthub.cn/p/io.github.Nizoka/pkinative-mcp)

Badges are generated on the fly from /badge/<package-id>, so name and listing changes propagate automatically. Keep the link target unchanged — it is what counts as the referral.

Unified Manifest

{
  "id": "io.github.Nizoka/pkinative-mcp",
  "type": "mcp-server",
  "version": "1.0.0",
  "displayName": "pkinative MCP — X.509, CMS, OCSP, time-stamps and PKCS#12 without a key byte leaving",
  "description": "PKI MCP server: inspect, verify, issue, sign X.509, CSR, CRL, OCSP, CMS, TSP, PKCS#12. 34 tools",
  "repository": {
    "url": "https://github.com/Nizoka/pkinative-mcp",
    "source": "github"
  },
  "homepage": "https://github.com/Nizoka/pkinative-mcp#readme",
  "distribution": {
    "packages": [
      {
        "registryType": "npm",
        "identifier": "pkinative-mcp",
        "version": "1.0.0",
        "runtimeHint": "npx",
        "transport": "stdio",
        "environmentVariables": [
          {
            "name": "PKINATIVE_MCP_OUTPUT_DIR",
            "description": "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."
          },
          {
            "name": "PKINATIVE_MCP_CACHE_DIR",
            "description": "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."
          },
          {
            "name": "PKINATIVE_MCP_PORT",
            "description": "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."
          },
          {
            "name": "PKINATIVE_MCP_HTTP_TOKEN",
            "description": "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.",
            "isSecret": true
          },
          {
            "name": "PKINATIVE_MCP_PASSWORD",
            "description": "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.",
            "isSecret": true
          },
          {
            "name": "PKINATIVE_MCP_AT",
            "description": "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."
          },
          {
            "name": "PKINATIVE_MCP_MAX_INPUT_BYTES",
            "description": "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."
          },
          {
            "name": "PKINATIVE_MCP_MAX_KDF_ITERATIONS",
            "description": "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."
          },
          {
            "name": "PKINATIVE_MCP_MAX_PATHS_EXPLORED",
            "description": "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."
          }
        ]
      }
    ],
    "remotes": []
  },
  "dependencies": [],
  "installTargets": [
    "claude-code",
    "claude-desktop",
    "cursor",
    "vscode",
    "trae",
    "cherry-studio",
    "lingma",
    "windsurf",
    "cline",
    "workbuddy"
  ],
  "keywords": [],
  "provenance": {
    "origin": "official-mcp-registry",
    "originalId": "io.github.Nizoka/pkinative-mcp",
    "originalUrl": "https://registry.modelcontextprotocol.io/v0.1/servers/io.github.Nizoka%2Fpkinative-mcp/versions/latest",
    "isOfficial": true,
    "status": "active"
  }
}