Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

HSM Kit

NPM · @HSMKIT/MCP-SERVER · SCANNED OCT 2

Local-first Base64, Luhn, key-component XOR, and synthetic ISO-0 PIN block tools.

Available components

npm · @hsmkit/mcp-server 80
−1 this week 80 Trust /100
Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →

Supply Chain Security100
  • No malware found by supply-chain analysis.Pass
  • No known CVEs affecting this package version or its production dependencies.Pass
  • No install/post-install scripts declared.Pass
  • 0 of 4 dependencies flagged as unhealthy. View diagnostics → Pass
Provenance & Transparency71
  • Repository presence not verified: we could not reach the forge to check. This is a gap on our side, not a finding about the repository. View diagnostics → Unverified
  • Cryptographically verified build provenance (signed, bound to hsm-kit/hsmkit). View diagnostics → Pass
  • Clear OSI-approved license (MIT).Pass
  • Actively maintained (last published 8 days ago).Pass
  • Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability80
  • AI-judged instruction clarity (excellent).Pass
  • Tool/resource definitions use about 231 tokens (~38/item across 6 items; 6 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management30
  • Stability observed for 9 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage90
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 71% of tool parameters carry a description.Partial
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 6 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Install

How do I install the HSM Kit MCP server?

HSM Kit runs locally as an npm package, launched with npx -y @hsmkit/mcp-server. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

npm · @hsmkit/mcp-server

# add to Claude Code
claude mcp add hsm-kit-hsmkit -- npx -y @hsmkit/mcp-server
// .cursor/mcp.json
{
  "mcpServers": {
    "hsm-kit-hsmkit": {
      "command": "npx",
      "args": [
        "-y",
        "@hsmkit/mcp-server"
      ]
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "hsm-kit-hsmkit": {
      "command": "npx",
      "args": [
        "-y",
        "@hsmkit/mcp-server"
      ]
    }
  }
}
# add to Codex CLI
codex mcp add hsm-kit-hsmkit -- npx -y @hsmkit/mcp-server
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "hsm-kit-hsmkit": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "@hsmkit/mcp-server"
      ],
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add hsm-kit-hsmkit --command npx --arg -y --arg @hsmkit/mcp-server
# ~/.hermes/config.yaml
mcp_servers:
  hsm-kit-hsmkit:
    command: "npx"
    args: ["-y", "@hsmkit/mcp-server"]
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "hsm-kit-hsmkit": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "@hsmkit/mcp-server"
      ]
    }
  }
}
# add to Vellum
assistant mcp add hsm-kit-hsmkit -t stdio -c npx -a -y @hsmkit/mcp-server
// mcp.json
{
  "mcpServers": {
    "hsm-kit-hsmkit": {
      "command": "npx",
      "args": [
        "-y",
        "@hsmkit/mcp-server"
      ]
    }
  }
}
Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 2 Oct 26 −5
    • Provenance: pass → unverified ▼ security
  • 1 Oct 26 +4
    • Stability: unverified → 0.27 ▲ functional
  • 28 Sept 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 25 Sept 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 24 Sept 26 +15
    • Malware scan: unverified → pass ▲ security
  • 23 Sept 26 66

    First indexed and scored.

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 2 Oct 2026 · Analysed npm/@hsmkit/mcp-server@0.1.0

Provenance Verified

A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.

Result Verified
Ecosystem npm
Reason Verified
Discovered via Registry attestation endpoint
Source repo hsm-kit/hsmkit
Certificate issuer https://token.actions.githubusercontent.com
Certificate SAN https://github.com/hsm-kit/hsmkit/.github/workflows/publish-packages.yml@refs/tags/v0.1.0
Rekor log index 2918478257
Predicate type SLSA build provenance https://slsa.dev/provenance/v1
Subject digest sha512:d5bcce344d97dbc4586d18ed5e8df0e4c79d0897f917f70054afa82d2e37dc65ac20ec64e0edff65d07e97fb18d8119c83cf2e82ffd35a430b302084b

Background: How many MCP packages publish verified provenance →

Dependencies 4 packages
Packages resolved 4
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 6 exposed · ~231 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
base64_decode ~27

Decode standard Base64 into UTF-8 text.

NameTypeReqDescription
base64stringyes–

No output schema declared.

No examples provided.

base64_encode ~26

Encode UTF-8 text as standard Base64.

NameTypeReqDescription
textstringyes–

No output schema declared.

No examples provided.

iso0_pin_block ~64

Generate an ISO 9564-1 format 0 clear PIN block from synthetic PIN and PAN test data.

NameTypeReqDescription
panstringyesSynthetic PAN containing 13 to 19 digits
pinstringyesSynthetic PIN containing 4 to 12 digits

No output schema declared.

No examples provided.

luhn_calculate_check_digit ~43

Calculate the Luhn (Mod 10) check digit for a digits-only payload.

NameTypeReqDescription
payloadstringyesDigits without the final check digit

No output schema declared.

No examples provided.

luhn_validate ~37

Validate a complete number using the Luhn (Mod 10) algorithm.

NameTypeReqDescription
valuestringyesComplete digits including the check digit

No output schema declared.

No examples provided.

xor_key_components ~34

XOR equal-length hexadecimal key components for synthetic interoperability tests.

NameTypeReqDescription
componentsarrayyesTwo or more equal-length hexadecimal values

No output schema declared.

No examples provided.

Common questions

What is the HSM Kit MCP server?

HSM Kit is an MCP server listed in the public MCP registry as io.github.hsm-kit/hsmkit. Local-first Base64, Luhn, key-component XOR, and synthetic ISO-0 PIN block tools. This page covers its npm package (@hsmkit/mcp-server).

Is the HSM Kit MCP server safe to use?

HSM Kit scores 80 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 2 October 2026. It declares no install or post-install scripts. Its build provenance is signed and verified. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the HSM Kit MCP server expose?

HSM Kit exposes 6 tools: luhn_calculate_check_digit, luhn_validate, xor_key_components, iso0_pin_block, base64_encode, base64_decode. Their descriptions and schemas cost roughly 231 tokens of context every time the server is loaded.

Is the HSM Kit MCP server still maintained?

HSM Kit is still listed as active in the MCP registry. We last reached this channel on 2 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What licence is the HSM Kit MCP server under?

HSM Kit declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.