Open-source B2B and marketplace ecommerce; new stores include an MCP server for AI agents.
Hookwarden — Webhook Integrity
概览
作者提供的说明(英文原文)
Webhook signature-verification audit. Stripe, GitHub, Shopify, Twilio +23. Local. Deterministic.
PopNx MCP 的三大支柱
这三项永远不会合并成一个分数:意见、测量和人气是不同的东西。
- 用户评价i暂无评价评价功能将在后续阶段与账户功能一起开放
- 我们的基础检查i1 项中通过 1 项依据公开信息检查;尚未扫描代码
- 使用情况i尚未统计★ –
它能帮你做什么
我们还没有为它写通俗的介绍。下面是我们从注册中心读取到的事实。
- 连接方式: 在你的电脑上运行
- 传输方式: stdio
- 分类: 网店与支付
安装
选择你使用的 AI 应用,然后复制设置。
安装之前
- 基础检查:1 项中通过 1 项
- 在你的电脑上运行,拥有你的用户账户的权限(文件、网络、应用)。
- 注册中心没有列出需要填写的密钥。
你需要
- npm已安装 Node.js(用于 npx 命令)
你用的是哪个应用?
在上方选择你的应用。我们会记住它,下次按钮会显示“安装到 …”。
打开 Claude Desktop → Settings → Developer → Edit Config,把下面的内容粘贴到 claude_desktop_config.json
{
"mcpServers": {
"hookwarden": {
"command": "npx",
"args": [
"-y",
"@hookwarden/mcp"
]
}
}
}在终端中运行这条命令
claude mcp add hookwarden -- npx -y @hookwarden/mcp或者自己复制设置
粘贴到项目中的 .cursor/mcp.json,或 ~/.cursor/mcp.json
{
"mcpServers": {
"hookwarden": {
"command": "npx",
"args": [
"-y",
"@hookwarden/mcp"
]
}
}
}浏览器会先询问是否打开应用,然后应用会显示设置并请你确认。密钥的值会留空,由你自己填写。
或者自己复制设置
粘贴到项目中的 .vscode/mcp.json
{
"servers": {
"hookwarden": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@hookwarden/mcp"
]
}
}
}浏览器会先询问是否打开应用,然后应用会显示设置并请你确认。密钥的值会留空,由你自己填写。
这个服务器在你的电脑上运行,而 ChatGPT 只能连接互联网上的服务器。请选择其他应用。
你的选择通过 Cookie 保存在这台设备上,无需账户。
这些设置是根据作者在注册中心的条目生成的。如果 README 的写法不同,请以 README 为准。
它能做什么
它在你的电脑上运行;安装后,工具列表会显示在你的 AI 应用中。
基础检查i
我们检查的是任何人都能看到的信息;我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月6日
- ✓ 通过
作者与仓库一致
注册名称已通过 GitHub 账户 Hookwarden 验证,该账户拥有此仓库
- … 尚未检查
仍在维护
我们还没有从 GitHub 读取这个仓库
- … 尚未检查
有许可证
我们还没有从 GitHub 读取这个仓库
- – 不适用
端点有响应
它在你的电脑上运行,没有互联网端点
- – 不适用
使用 OAuth 登录
在你的电脑上运行,改用本地设置
- … 尚未检查
工具描述中没有隐藏指令
它在你的电脑上运行;我们只能读取互联网端点的工具列表
与“网店与支付”中的其他服务器比较i
- 星标数多于此分类中其他 1745 个服务器的 0%
- 发布到注册中心的时间比此分类中其他 1745 个服务器的 53% 更新
- 基础检查结果等于或优于此分类中其他 1745 个服务器的 100%
与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时,星标数才计入。
常见问题
Hookwarden — Webhook Integrity 安全吗?
它在 1 项适用的基础检查中通过了 1 项。我们没有阅读代码。在添加密钥或令牌之前,请先看看这个服务器要求哪些权限,并使用只具备所需权限的密钥。
它需要哪些密钥或代码?
注册中心没有列出必需的密钥,不过有些服务器会在首次使用时要求你登录。
它在我的电脑上运行还是在云端?
它在你的电脑上运行。你的 AI 应用会在需要时启动它,数据不会经过作者的服务器(除非它自己调用在线服务)。
它还在维护吗?
GitHub 仓库最后更新于–,最新版本(0.9.5)于28天前进入注册中心。
哪些应用可以使用它?
支持 MCP 的应用,例如 Claude Desktop、Claude Code、Cursor 和 VS Code。你的电脑上还需要有 Node.js。
有什么可以替代它?
同一分类中有:Spree Commerce: open-source B2B and marketplace ecommerce, Stripe MCP, MCP Cn Commerce
替代选择
同一分类中其他作者的服务器,按星标数排序。
如何看卡片:★ GitHub 星标i三大支柱:评价 · 检查 · 使用情况i更新 = 最新版本发布到注册中心的时间i
Stripe MCP
MCP server integrating with Stripe - tools for customers, products, payments, and more.
MCP Cn Commerce
8 read-only MCP platform entries; support is operation-specific; merchant live acceptance pending
作者的 README
打开 README
按原文从作者的仓库复制。PopNx MCP 没有审查或背书其内容。HTML、图片和脚本已被移除。链接会离开本站。
The first MCP server doing webhook signature verification.
Local. Deterministic. Zero network. JS / TS / Python / PHP / Go — 27 providers — 3-state verdicts.
What it does
@hookwarden/mcp exposes hookwarden's deterministic webhook-verification engine as MCP tools. AI coding agents — Claude Desktop, Cursor, Continue, and apps built on the Anthropic Agent SDK — get two tools:
- `scan_handler` — scan pasted webhook handler code and get back a structured finding (
verified/not-verified/manual-review) for Stripe, GitHub, Shopify, Twilio, and 23 other providers. - `verify_audit_chain` — verify a hookwarden evidence pack's hash chain + KMS-signed Merkle roots offline (no network, no auth), returning
{ valid, broken_at_row, signatures_verified }.
Runs entirely client-side. Zero network egress from the MCP process. Zero auth. The same engine the hookwarden CLI ships — same rule pack, same content hashes, end-to-end provenance.
Install in one command
npx @hookwarden/mcp init
That command detects your installed MCP clients (Claude Desktop / Cursor / Continue), prints a per-OS summary table, and writes the canonical config to each one. .bak files land alongside every config it touches. Restart the relevant client and scan_handler + verify_audit_chain appear in the tool list.
Pass --all for non-interactive use, --dry-run to preview, --force to overwrite an existing mcpServers.hookwarden entry, or --clients claude-desktop,cursor to limit the set.
Manual configuration
If you'd rather not run the init helper, write the config by hand.
Claude Desktop
- macOS:
~/Library/Application Support/Claude/claude_desktop_config.json - Windows:
%APPDATA%/Claude/claude_desktop_config.json
{
"mcpServers": { "hookwarden": { "command": "npx", "args": ["-y", "@hookwarden/mcp"] } } }
Cursor
~/.cursor/mcp.json — same shape as Claude Desktop:
{
"mcpServers": { "hookwarden": { "command": "npx", "args": ["-y", "@hookwarden/mcp"] } } }
Continue.dev
Continue uses a per-server file. Write ~/.continue/mcpServers/hookwarden.yaml:
name: hookwarden
command: npx args: [-y, "@hookwarden/mcp"]
Anthropic Agent SDK
The Agent SDK is programmatic — there's no config file to edit. Drop this into your code:
import { query } from "@anthropic-ai/claude-agent-sdk";
for await (const message of query({ prompt: "Audit this webhook handler for missing signature verification...", options: { mcpServers: { hookwarden: { command: "npx", args: ["-y", "@hookwarden/mcp"], }, }, }, })) { console.log(message); }
The init helper does not write here — the SDK integration is code, not config.
The scan_handler tool
Inputs
| Field | Type | Notes | ||
|---|---|---|---|---|
code | string | Single-blob mode. Defaults to TypeScript; override with language. Mutually exclusive with files. | ||
files | Record | Multi-file mode. Keys are virtual file paths; language inferred from extension. | ||
language | `"js" \ | "ts" \ | "python"` | Optional. "php" returns language_not_in_preview — PHP support ships in v0.8.1. |
provider | string | Optional. Case-insensitive ("stripe" = "Stripe"). unknown_provider if not in the rule pack. |
Output
Returns Tool.result with structuredContent first-class (MCP spec 2025-06-18) plus a companion stringified-JSON text block for backwards compatibility:
{
"verdict_summary": { "verified": 0, "not_verified": 1, "manual_review": 0, "parse_error": 0 }, "findings": [ { "rule_id": "stripe/missing-signature-verification", "provider": "stripe", "severity": "critical", "verdict": "not-verified", "file": "__handler.ts", "line_start": 7, "line_end": 9, "message": "Webhook handler reads req.body without calling stripe.webhooks.constructEvent...", "provider_docs_url": "https://stripe.com/docs/webhooks", "references": [ "https://www.svix.com/blog/common-failure-modes-for-webhook-signatures/", "https://hookdeck.com/webhooks/guides/webhook-security-vulnerabilities-guide" ], "rule_pack_version": "0.7.2" } ], "scan_metadata": { "engine_version": "0.7.2", "rule_pack_version": "0.7.2", "rule_pack_content_hash": "938f7565e29f19e0cbd34594731d1de2b0ffd40ee87aacaa8be2435fc1f47f32" } }
Verdict vocabulary
| Verdict | Meaning |
|---|---|
verified | Engine proved the handler verifies signatures via the provider's documented SDK call. |
not-verified | Engine proved the handler does NOT verify signatures (or verifies after side effects). |
manual-review | Engine has structural evidence but can't decide without human eyes — review the snippet. |
Same 3-state vocabulary as the CLI. No remapping in the MCP layer.
Error payloads (isError: true)
| Error | Trigger |
|---|---|
empty_input | Neither code nor files provided. |
exclusive_input_modes | Both code and files provided — pick one. |
language_not_in_preview | language: "php" — PHP ships in v0.8.1. Suggestion: npx hookwarden scan. |
unsupported_language | language outside the known set. |
unknown_provider | provider not in the rule pack. Response includes the sorted known list. |
engine_drift / rules_drift | Boot or call-time drift — see drift-detection. |
Parse failures don't crash the transport — they emit as rule_id: "engine/parse-error" findings with severity high and increment verdict_summary.parse_error.
The verify_audit_chain tool
Verify a hookwarden evidence pack's integrity offline — no network, no AWS, no credentials. "Verify the chain without trusting hookwarden." The tool walks the per-row hash chain, roundtrips the manifest hash, and — for v1.1 packs that embed the signing CMK's SPKI public key — verifies the ECDSA-P256 (MessageType:DIGEST) Merkle-root + manifest signatures with node:crypto.
Inputs
| Field | Type | Notes |
|---|---|---|
evidence_pack_json | string | The full evidence-pack JSON (the file hookwarden's evidence export produces). Both v1.0 and v1.1 packs are accepted. |
Output
{
"valid": true, "broken_at_row": null, "signatures_verified": 2 }
| Field | Meaning |
|---|---|
valid | true iff the hash chain is intact AND the manifest hash roundtrips AND every signature that could be verified offline verified. |
broken_at_row | The seq of the first row whose chain hash didn't match, or null if the chain is intact. Signature validity is independent of chain integrity. |
signatures_verified | Count of offline-verified signatures: N Merkle-root signatures + 1 manifest signature (N+1). 0 for v1.0 packs (no embedded public key) — the tool emits a signatures not verifiable offline (v1.0 pack) note instead of failing. |
Trust model
The v1.1 pack carries its own SPKI public key. The signature proves the pack was not altered after signing by the holder of that key — it is trust-on-first-use. To pin trust to a specific signer out-of-band, an auditor can cross-check signature.signing_cmk_arn against AWS KMS GetPublicKey and confirm the embedded SPKI key matches. Malformed pack JSON returns isError: true (error: "invalid_pack_json") — the tool never throws past its boundary.
This tool imports only @hookwarden/canonical-json (the shared RFC 8785 byte-equality anchor) + node:crypto. It does not load the engine or rule pack and does not run the drift gate.
Integrity claims
- Zero outbound TCP — the published tarball passes
pnpm inspect-bundle, a structural CI gate that rejects any source-file import of HTTP clients (node:http,axios,undici, etc.) and any direct dependency outside the documented allowlist. - Drift detection — every
scan_handlercall cross-checks the runtime-resolved engine + rule-pack hashes against the build-timedist/build-manifest.json. Mismatch returnsisError: truewith structuredengine_drift/rules_driftpayload. No env-var opt-out. See drift-detection — including the v0.8.0 engine-content-hash limitation. - No telemetry — the tarball declares no analytics or tracking SDKs (
@datadog/*,@segment/*,@sentry/*, etc.) independenciesor transitively in source-file imports. - Open source — Apache-2.0 at
Hookwarden/hookwarden/packages/mcp/. Engine + rule pack land in the same monorepo and ship under the same license.
Links
- Documentation — getting started, tool surface reference, drift detection
- npm package
- GitHub repository
- Apache-2.0 License
Copyright 2026 Hookwarden contributors. Apache License 2.0.