Open-source B2B and marketplace ecommerce; new stores include an MCP server for AI agents.
Hookwarden — Webhook Integrity
Overview
Description from the maker (original English)
Webhook signature-verification audit. Stripe, GitHub, Shopify, Twilio +23. Local. Deterministic.
PopNx MCP’s three pillars
These three are never merged into one score: opinions, measurements and popularity are different things.
- User voiceiNo reviews yetReviews open together with accounts in a later step
- Our basic checksi1 of 1 passedChecked from public information; code not scanned yet
- UsageiNot measured yet★ –
What you can do with it
We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.
- Connection: Runs on your computer
- Transport: stdio
- Category: Online shops & payments
Install
Pick the AI app you use, then copy the settings.
Before you install
- Basic checks: 1 of 1 passed
- Runs on your computer with your user’s permissions (files, network, apps).
- The registry lists no key to fill in.
You need
- npmNode.js installed (for the npx command)
Which app do you use?
Pick your app above. We remember it, so next time the button says “Install in …”.
Open Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json
{
"mcpServers": {
"hookwarden": {
"command": "npx",
"args": [
"-y",
"@hookwarden/mcp"
]
}
}
}Run this in your terminal
claude mcp add hookwarden -- npx -y @hookwarden/mcpOr copy the settings yourself
Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"hookwarden": {
"command": "npx",
"args": [
"-y",
"@hookwarden/mcp"
]
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
Or copy the settings yourself
Paste into .vscode/mcp.json in your project
{
"servers": {
"hookwarden": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@hookwarden/mcp"
]
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
This one runs on your computer, and ChatGPT can only connect to servers on the internet. Pick another app.
Your choice stays on this device in a cookie; no account needed.
These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.
What it can do
Runs on your computer; the tool list appears in your AI app after you install it.
Basic checksi
We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 7, 2026
- ✓ Pass
Maker matches the repo
The registry name was verified with the GitHub account Hookwarden, which owns the repo
- … Not checked yet
Still maintained
We have not read this repo from GitHub yet
- … Not checked yet
Has a licence
We have not read this repo from GitHub yet
- – Not applicable
Endpoint responds
This one runs on your computer; there is no internet endpoint
- – Not applicable
Sign-in with OAuth
Runs on your computer and uses local settings instead
- … Not checked yet
No hidden instructions in tool descriptions
Runs on your computer; we can only read tool lists from internet endpoints
Compared with others in Online shops & paymentsi
- More stars than 0% of the other 1748 servers in this category
- Published to the registry more recently than 53% of the other 1748 servers in this category
- Basic checks equal to or better than 100% of the other 1748 servers in this category
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
Common questions
Is Hookwarden — Webhook Integrity safe?
It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.
What keys or codes does it need?
The registry does not list a required key, though some servers ask you to sign in on first use.
Does it run on my computer or in the cloud?
It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).
Is it still maintained?
The GitHub repo last changed –, and the latest version (0.9.5) reached the registry 28 days ago.
Which apps can use it?
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Node.js on your computer.
What can I use instead?
In the same category: Spree Commerce: open-source B2B and marketplace ecommerce, Stripe MCP, MCP Cn Commerce
Alternatives
Servers in the same category from other makers, sorted by stars.
Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi
Stripe MCP
Stripe’s official server lets AI view and manage customers, products, payments and invoices. Connect to Stripe’s cloud and sign in with OAuth.
MCP Cn Commerce
8 read-only MCP platform entries; support is operation-specific; merchant live acceptance pending
README from the maker
Open the README
Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.
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.