Validate Formhaus form definitions and simulate multi-step paths against the real engine.
Nothing to run from here
Hookden is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
7
tools declared
—
trust score
remote
at its publisher
—
calls last 7d
What it does
Webhook capture bins for agents: get a URL, wait for webhooks, set replies, verify signatures.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http hookden-mcp https://hookden.pages.dev/mcp
# 2 — ask your agent for something these tools do
# create_bin, list_captures, get_capture and 4 more
Hookden costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Publishernot claimed
HOAll 1 server
hookden1 server
1 category
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Installation
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. Nothing here runs on your machine and nothing runs on ours: this server answers at its publisher’s own address, and what you install is the connection straight to it.
Claude Codedeclared by this listing
This is a public server: it answers at its publisher’s own address and this marketplace is not in the path. Claude Code registers it in one command; --scope user makes it available in every project. The transport below is http, as the publisher's own manifest declares it.
claude mcp add --scope user --transport http hookden-mcp https://hookden.pages.dev/mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
Free on mcprush, and it answers at its publisher’s own address: this marketplace is not in the path, so there is no key of ours to hold and no card to add.
What it writes
One config entry pointing straight at the publisher’s own address — this marketplace is not in the path, and nothing from this listing executes on your machine.
What you approve
7 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
Create a new webhook capture bin. Returns a public capture_url — point any webhook (Stripe, GitHub, Slack, your own service…) at it and every request sent there (any method, any subpath, headers + raw body) is stored. Then read what arrived with list_captures, get_capture, or wait_for_capture. Anonymous bins keep requests ~24h. No auth needed.
No parameter schema on file.
List requests captured by a bin, oldest first. Compact summaries (id, method, path, time, content-type, body size, signature status). Use get_capture for full headers/body. Pass after (a capture id) to only see newer captures.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| bin | string | yes | bin id (or custom slug) from create_bin |
| after | integer | no | only captures with id greater than this (default 0) |
| limit | integer | no | max results, 1-50 (default 20) |
Get one captured request in full: method, path, query, every header, and the body. Binary bodies are returned base64-encoded (up to 8KB, with a URL for the raw bytes).
| Parameter | Type | Required | Notes |
|---|---|---|---|
| bin | string | yes | bin id or slug |
| id | integer | yes | capture id from list_captures / wait_for_capture |
Block until the next request arrives at a bin (or a timeout passes), then return it in full. Ideal flow: create_bin → configure the webhook sender → trigger it → wait_for_capture. If after_id is omitted, waits for the next capture after "now". Returns timed_out:true instead of erroring when nothing arrives.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| bin | string | yes | bin id or slug |
| after_id | integer | no | return the first capture with id greater than this; default = latest id at call time |
| timeout_seconds | integer | no | 1-45 seconds to wait (default 20) |
Simulate a webhook delivery into a bin — no external sender or HTTP client needed. Seeds one realistic, clearly-labeled sample capture (default: a GitHub push event) and returns it in full, so you can exercise the whole loop (create_bin → send_test_webhook → list_captures / get_capture) entirely from MCP. Pass example to pick a provider payload from the /examples library (e.g. "stripe-payment-in
| Parameter | Type | Required | Notes |
|---|---|---|---|
| bin | string | yes | bin id (or custom slug) from create_bin |
| example | string | no | optional example payload slug from /examples (default: a GitHub push event) |
Configure what a bin replies to webhook senders: HTTP status, content-type, body, custom response headers, optional delay. Body and header values support {{…}} templates rendered per-request from the INCOMING delivery — {{body.challenge}}, {{query.hub.challenge}}, {{header.x-hook-secret}}, {{hmac_sha256 body.plainToken YOUR_SECRET}} — so a bin can pass provider verification handshakes with zero co
| Parameter | Type | Required | Notes |
|---|---|---|---|
| bin | string | yes | bin id (or custom slug) from create_bin |
| status | integer | no | HTTP status to respond with, 100-599 (bins default to 200) |
| content_type | string | no | Content-Type of the response (e.g. application/json, text/plain) |
| body | string | no | response body, max 10000 chars; {{…}} templates allowed |
| headers | object | no | custom response headers as name→value (max 10; values may use {{…}} templates). Pass {} to clear. Hop-by-hop/security headers (set-cookie, location, strict-transport-security…) are rejected. |
| delay_ms | integer | no | artificial response delay in milliseconds, 0-10000 (for testing sender timeouts/retries) |
Verify a webhook signature against a secret — 25 provider-exact schemes plus a generic HMAC mode, the same engine that computes ✓/✗ badges on captures. Covers HMAC-SHA256 (GitHub, Stripe, Svix/Standard Webhooks, Shopify-style base64, URL-signing Square/HubSpot/Trello…), ECDSA (SendGrid), RSA (Kick) and HMAC-MD5 (Patreon). Pass the scheme, the secret, the delivery's headers, and the BYTE-EXACT raw
| Parameter | Type | Required | Notes |
|---|---|---|---|
| scheme | string | yes | signature scheme (usually the provider name); "hmac" = generic HMAC over the raw body |
| secret | string | yes | signing secret or key exactly as the provider shows it (sendgrid/kick: the PUBLIC verification key) |
| headers | object | no | the delivery's HTTP headers — at least the signature/timestamp headers; names are case-insensitive |
| body | string | no | raw request body, byte-exact as the provider sent it (not re-serialized!) |
| body_base64 | string | no | alternative to body for binary payloads: base64 of the raw body bytes |
| url | string | no | full delivery URL — REQUIRED for square, hubspot and trello (the URL is part of the signed string) |
| method | string | no | HTTP method of the delivery (hubspot v3 signs it; default POST) |
| signature_header | string | no | scheme "hmac" only: which header carries the signature (default x-signature) |
Free
$0 forever
- Every tool — any call limit is its publisher’s, not ours
- No card, and mcprush charges nothing for it
- Runs at its publisher’s own address — this marketplace is not in the path
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install Hookden or to call it, at any volume.
Call allowance · this installenforced at the gateway
Monthly allowance, in calls
—
—
Alert at 80% · then the tool returns a normal MCP error
Used this month: —
—Grade not published
No rule-by-rule report on file for this release
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
This listing is an address its publisher runs, and you connect to it directly — this marketplace is not in the path. The scanner reads packages and public source, and an address is neither. So there is no grade — not a withheld one, an unmeasured one.
Release history
This is an address its publisher runs: which release it serves is theirs to choose, so there is nothing here to pin. The history below is for reading; the current release on file is 1.3.0.
1.3.0
undated
latestNo release note was published with this version.
—
no reviews yet
Who can review
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Sign in to write one
Any signed-in account that does not publish Hookden can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
No reviews yet
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.