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.

io.github.krystiangw/zen

NPM · @KRYSTIANGW/ZEN-MCP · SCANNED OCT 1

Unofficial MCP server for the ZEN.com Payment Gateway: payment links, transactions, refunds.

Available components

0 this week 82 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 Security98
  • 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
  • 31 of 93 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
Schema Quality & AI Usability79
  • 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 729 tokens (~45/item across 16 items; 14 tools + 2 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
  • No destabilizing schema changes in the last 30 days.Pass
Tool Coverage67
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 0% of tool parameters carry a description.Fail
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
  • An AI judge read all 15 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 io.github.krystiangw/zen MCP server?

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

npm · @krystiangw/zen-mcp

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

  • 1 Oct 26 0
    • Stability: 0.97 → pass security
  • 30 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.

  • 28 Sept 26 +1
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 26 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.

  • 25 Sept 26 −3
    • 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 0
    • Stability: 0.97 → pass security
  • 23 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.

  • 21 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.

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 1 Oct 2026 · Analysed npm/@krystiangw/zen-mcp@0.1.1

Provenance No attestation

The registry publishes no build provenance for this version, so there is nothing to verify.

Result No attestation
Ecosystem npm

Background: How many MCP packages publish verified provenance →

Dependencies 93 packages
Packages resolved 93
Stale 31
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 14 exposed · ~697 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
cancel_transaction ~47

Destructive write: cancel a ZEN transaction. This may prevent or reverse payment processing; confirm before use.

NameTypeReqDescription
idstringyes–
idempotencyKeystring––

No output schema declared.

No examples provided.

capture_transaction ~49

Destructive write: capture an authorized transaction, causing funds to be collected. Confirm before use.

NameTypeReqDescription
amount–––
idstringyes–
idempotencyKeystring––

No output schema declared.

No examples provided.

create_customer ~68

Write operation: create a customer record in ZEN for future payment flows; this stores personal data.

NameTypeReqDescription
emailstringyes–
firstNamestring––
idempotencyKeystring––
lastNamestring––
phonestring––

No output schema declared.

No examples provided.

create_payment_link ~84

Write operation: create a hosted ZEN checkout link and QR code for a customer to pay.

NameTypeReqDescription
amount–yes–
currencystringyes–
customIpnUrlstring––
descriptionstring––
expiresAtstring––
idempotencyKeystring––
merchantTransactionIdstringyes–

No output schema declared.

No examples provided.

create_payout ~106

Highest-risk destructive write: send money outward through ZEN. Verify recipient, channel, currency, and amount before use.

NameTypeReqDescription
amount–yes–
currencystringyes–
customerEmailstring––
customerFirstNamestring––
customerLastNamestring––
customerPhonestring––
idempotencyKeystring––
merchantTransactionIdstringyes–
paymentChannelstringyes–

No output schema declared.

No examples provided.

download_report ~53

Read-only: request a transaction or settlement report download from ZEN.

NameTypeReqDescription
endDatestring––
formatstring––
reportTypestring––
startDatestring––

No output schema declared.

No examples provided.

get_payment_link ~29

Read-only: retrieve a hosted ZEN payment link by ID.

NameTypeReqDescription
idstringyes–

No output schema declared.

No examples provided.

get_payout ~31

Read-only: retrieve a ZEN payout by its ZEN ID.

NameTypeReqDescription
zenIdstringyes–

No output schema declared.

No examples provided.

get_transaction ~42

Read-only: retrieve a transaction by exactly one ZEN ID or merchant transaction ID.

NameTypeReqDescription
merchantTransactionIdstring––
zenIdstring––

No output schema declared.

No examples provided.

list_payment_links ~40

Read-only: list hosted ZEN payment links.

NameTypeReqDescription
limitinteger––
pageinteger––
statusstring––

No output schema declared.

No examples provided.

list_payment_methods ~23

Read-only: list payment methods available to the configured ZEN terminal.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

list_supported_currencies ~23

Read-only: list currencies confirmed in the public ZEN documentation.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

refund_transaction ~62

Destructive write: return all or part of a payment to the customer. Confirm the transaction and amount before use.

NameTypeReqDescription
amount–––
idempotencyKeystring––
transactionIdstring––
zenIdstring––

No output schema declared.

No examples provided.

verify_webhook_signature ~40

Read-only: verify a ZEN IPN webhook signature using the configured IPN secret.

NameTypeReqDescription
payload–yes–
signaturestringyes–

No output schema declared.

No examples provided.

Common questions

What is the io.github.krystiangw/zen MCP server?

io.github.krystiangw/zen is an MCP server listed in the public MCP registry as io.github.krystiangw/zen. Unofficial MCP server for the ZEN.com Payment Gateway: payment links, transactions, refunds. This page covers its npm package (@krystiangw/zen-mcp).

Is the io.github.krystiangw/zen MCP server safe to use?

io.github.krystiangw/zen scores 82 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 1 October 2026. It declares no install or post-install scripts. 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 io.github.krystiangw/zen MCP server expose?

io.github.krystiangw/zen exposes 14 tools: list_payment_methods, get_transaction, list_payment_links, get_payment_link, get_payout, and 9 more. Their descriptions and schemas cost roughly 697 tokens of context every time the server is loaded.

Is the io.github.krystiangw/zen MCP server still maintained?

io.github.krystiangw/zen is still listed as active in the MCP registry. We last reached this channel on 1 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 io.github.krystiangw/zen MCP server under?

io.github.krystiangw/zen declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.