Hookwarden — Webhook Integrity

io.github.HookwardenPublished by GitHub account Hookwardenv0.9.5Updated Oct 24, 2026

Webhook signature-verification audit. Stripe, GitHub, Shopify, Twilio +23. Local. Deterministic.

VerifiedSTDIODesktop onlyDeveloper ToolsSecurity & Monitoring

Overview

AI-generated overview

Local MCP server that audits webhook handler code for missing signature verification and verifies hookwarden evidence-pack hash chains offline.

What you can do
  • Scan pasted webhook handler code, or a set of virtual files, and get structured findings with a verified, not-verified or manual-review verdict per rule.
  • Check handlers against rule packs for Stripe, GitHub, Shopify, Twilio and 23 other providers, in JS, TS or Python.
  • Verify a hookwarden evidence pack's per-row hash chain, manifest hash and embedded ECDSA-P256 signatures offline, returning validity, the first broken row and a signature count.
  • Report engine and rule-pack version and content hashes with each scan, and flag drift between runtime and build-time hashes.
When to use it
Useful when reviewing or writing webhook endpoints and you want an assistant to check that signatures are actually verified before side effects run. Also fits auditors who need to check a hookwarden evidence pack's integrity without network access or credentials.
Requirements
Runs as a local stdio process, normally launched with npx from the npm package @hookwarden/mcp, so Node.js and npm are needed. No authentication, API keys or environment variables are declared, and the README states the process makes no network calls. An optional init command writes config files for Claude Desktop, Cursor and Continue.
Before you install
The init command detects installed MCP clients and writes or overwrites their config files, keeping .bak copies; use the dry-run and force options deliberately. Evidence-pack signature checks are trust-on-first-use unless the embedded public key is cross-checked out of band. PHP input is rejected in this version, and findings are static analysis, so manual-review verdicts still need a human.

Installation

In SourceWeft

  1. Open Hookwarden — Webhook Integrity in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

[hookwarden]

The first MCP server doing webhook signature verification.
Local. Deterministic. Zero network. JS / TS / Python / PHP / Go — 27 providers — 3-state verdicts.

[npm version] [License: Apache 2.0] [Node 22+] [MCP spec 2025-06-18]

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

bash
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
json
{  "mcpServers": {    "hookwarden": {      "command": "npx",      "args": ["-y", "@hookwarden/mcp"]    }  }}

Cursor

~/.cursor/mcp.json — same shape as Claude Desktop:

json
{  "mcpServers": {    "hookwarden": {      "command": "npx",      "args": ["-y", "@hookwarden/mcp"]    }  }}

Continue.dev

Continue uses a per-server file. Write ~/.continue/mcpServers/hookwarden.yaml:

yaml
name: hookwardencommand: npxargs: [-y, "@hookwarden/mcp"]

Anthropic Agent SDK

The Agent SDK is programmatic — there's no config file to edit. Drop this into your code:

ts
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

FieldTypeNotes
codestringSingle-blob mode. Defaults to TypeScript; override with language. Mutually exclusive with files.
filesRecord<string, string>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.
providerstringOptional. 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:

json
{  "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

VerdictMeaning
verifiedEngine proved the handler verifies signatures via the provider's documented SDK call.
not-verifiedEngine proved the handler does NOT verify signatures (or verifies after side effects).
manual-reviewEngine 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)

ErrorTrigger
empty_inputNeither code nor files provided.
exclusive_input_modesBoth code and files provided — pick one.
language_not_in_previewlanguage: "php" — PHP ships in v0.8.1. Suggestion: npx hookwarden scan.
unsupported_languagelanguage outside the known set.
unknown_providerprovider not in the rule pack. Response includes the sorted known list.
engine_drift / rules_driftBoot 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

FieldTypeNotes
evidence_pack_jsonstringThe full evidence-pack JSON (the file hookwarden's evidence export produces). Both v1.0 and v1.1 packs are accepted.

Output

json
{  "valid": true,  "broken_at_row": null,  "signatures_verified": 2}
FieldMeaning
validtrue iff the hash chain is intact AND the manifest hash roundtrips AND every signature that could be verified offline verified.
broken_at_rowThe 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_verifiedCount 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_handler call cross-checks the runtime-resolved engine + rule-pack hashes against the build-time dist/build-manifest.json. Mismatch returns isError: true with structured engine_drift / rules_drift payload. 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.) in dependencies or 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


Copyright 2026 Hookwarden contributors. Apache License 2.0.

Source: packages/mcp/README.md at commit 213ff9a

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

2
  1. v0.9.5LatestOct 9, 2026
  2. v0.8.7Sep 16, 2026

Score

50% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts