Skip to main content
Glama
pkinative-mcp

pkinative-mcp

Related Servers

Alternatives to pkinative-mcp

No user-submitted related servers found.

    Related Servers

    • A
      license
      A
      quality
      B
      maintenance
      A local MCP server for AI-assisted PKI and ASN.1 workflows, providing tools for certificate parsing, key management, and PKCS#12 processing.
      28
      27 npm
      MIT
    • A
      license
      A
      quality
      C
      maintenance
      MCP server for offline verification of signed artifacts — receipts, manifests, and audit bundles. MIT licensed, works without accounts or API calls. Tools: self_test, verify_receipt, verify_bundle, explain_artifact.
      4
      95 npm
      6
      Apache 2.0
    • F
      license
      Not graded
      quality
      B
      maintenance
      Enables MCP clients and AI agents to verify credentials through a 12-stage pipeline, translate between eight credential formats, check domain risk and revocation status, search security-scored indexed MCP servers, fingerprint tool definitions, and submit scanned skills for catalog publication.
      -
    • A
      license
      Not graded
      quality
      C
      maintenance
      Free SSL/TLS scanning and Let's Encrypt certificate issuance (private key stays local), plus certificate-expiry monitoring via one MCP server. Public scan and cert tools need no account.
      3
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      Provides a unified tool for TLS certificate analysis with automatic OpenSSL integration, allowing users to fetch, analyze and assess security of TLS certificates without manual PEM handling.
      2
      MIT
    • A
      license
      B
      quality
      D
      maintenance
      Defense-grade cryptographic compliance and analysis tools for MCP, including FIPS 140-3 validation, CNSA 2.0 analysis, post-quantum readiness assessment, and classical cipher utilities.
      18
      2
      MIT

    TDQS

    A4.3/5.0

    Scored across 34 tools

    Disambiguation4/5

    The tools split into clear families — inspect (facts), verify/check (verdicts), create/sign, and encode/decode — and descriptions repeatedly point to the correct alternative. However, many adjacent inspect/verify/check pairs across CRL, OCSP, CMS, timestamp, and PKCS#12 create realistic routing ambiguity for less expert agents.

    Naming Consistency5/5

    Every tool is snake_case and starts with a verb, with resource nouns reused consistently (certificate, crl, ocsp, cms, timestamp, pkcs12). Minor variation such as open_pkcs12 vs inspect_pkcs12 still fits the overall pattern.

    Tool Count2/5

    34 tools is a very large surface; even for a broad PKI domain it exceeds the comfortable range and splits capabilities across many narrowly scoped calls. The scope justifies most tools individually, but the set is heavy for an agent to navigate reliably.

    Completeness4/5

    Coverage is unusually deep across certificates, CSRs, chain building/validation, CRL/OCSP, CMS, timestamping, keys, PKCS#12, ASN.1/PEM, and error introspection. Gaps are mostly intentional doctrine — no key generation/export, no network fetching — plus no enveloped CMS encryption/decryption, so the lifecycle is not fully closed.

    Maintenance

    ActivityMaintained
    ResponsivenessNo recent community issues