Skip to content

Hookden MCP server

dev.pages.hookden/hookdenhookden.pages.devstreamable-httpv1.3.0Scanned

Webhook capture bins for agents: get a URL, wait for webhooks, set replies, verify signatures.

7 tools: 1 do something that can't be undone, 3 change things and 3 only read.

Tools: 0 delete, 1 irreversible, 3 write, 3 read.
  • Reads private data · 0
  • Reads text others write · 0
  • Can send data out · 2
  • No findings

Tools listed without sign-in. Remote posture

With Anlyon

1 tool here does something that can't be undone. Govern it.

  • Anlyon lists the tools and adopts none.
  • Each tool you adopt gets approvals and receipts.
  • Your agent never holds the key.
Govern this server →

A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.

What the Hookden MCP server can do

The Hookden MCP server is published by hookden.pages.dev, a domain the MCP Registry verified. It has 7 tools. It can do things that cannot be undone, such as sending, paying or publishing (send_test_webhook) and create or change data (3 tools: create_bin, set_response and verify_signature), but cannot delete data. 3 tools only read.

2 tools can send data out of your system (send_test_webhook and verify_signature).

None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.

Its remote endpoint lists its tools without sign-in.

Last scanned Nov 15, 2026, version 1.3.0.

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

7 tools

Can't be undone 1Claude Code: ask
  • send_test_webhookSimulate a webhook delivery into a bin — no external sender or HTTP client needed.Can send data outNo findings

    Why it is in this group

    • The name "send_test_webhook" says "send": a word for sending, and what is sent cannot be taken back.

    What it can reach

    • outboundThe name "send_test_webhook" says "send": it sends or publishes something to other people.
    Description, as the server wrote it
    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-intent-succeeded", "slack-event-callback", "shopify-order-created"). Sample captures are marked as simulated and never count as real webhook traffic.
Changes things 3Claude Code: ask
  • create_binCreate a new webhook capture bin.No findings

    Why it is in this group

    • The name "create_bin" says "create": a word for a change.
    Description, as the server wrote it
    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.
  • set_responseConfigure what a bin replies to webhook senders: HTTP status, content-type, body, custom response headers, optional delay.No findings

    Why it is in this group

    • The name "set_response" says "set": a word for a change.
    Description, as the server wrote it
    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 code: Slack URL verification (body {{body.challenge}}), Zoom CRC (JSON with the hmac_sha256 helper), Meta/WhatsApp GET echo (text/plain {{query.hub.challenge}}), Strava (JSON {"hub.challenge":"{{query.hub.challenge}}"}), Asana (response header X-Hook-Secret: {{header.x-hook-secret}}). Only the fields you pass change; everything else keeps its current value. Works on bins created via create_bin by this same client; the incoming request is still captured in full either way.
  • verify_signatureVerify a webhook signature against a secret — 25 provider-exact schemes plus a generic HMAC mode, the same engine that computes ✓/✗ badges on captures.Can send data outNo findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.

    What it can reach

    • outboundThe input takes a URL (input.url): a request to a URL can carry data to whoever runs it.
    Description, as the server wrote it
    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 body (body_base64 for binary). The secret is used only for this one in-memory computation — never stored or logged. No bin needed. If verification fails, the #1 cause is a re-serialized body: point the real webhook at a capture bin (create_bin) to get the true raw bytes first.
Only reads 3Show 3 read-only tools
  • get_captureGet one captured request in full: method, path, query, every header, and the body.No findings

    Why it is in this group

    • The name "get_capture" says "get": a word for reading.
    Description, as the server wrote it
    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).
  • list_capturesList requests captured by a bin, oldest first.No findings

    Why it is in this group

    • The name "list_captures" says "list": a word for reading.
    Description, as the server wrote it
    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.
  • wait_for_captureBlock until the next request arrives at a bin (or a timeout passes), then return it in full.No findings

    Why it is in this group

    • The name "wait_for_capture" says "wait": a word for reading.
    Description, as the server wrote it
    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.

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or untrusted-input.

Reads private data0
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write0
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out2
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

Tools listed without sign-in

Looked at Nov 20, 2026, 18:52 UTC, unchanged since Oct 22, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
yes
HTTP status of an anonymous initialize
200
tools/list served without credentials
yes
Tools that change things, listed without credentials
4
Protocol version
2025-06-18
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
not observed
Authorization servers
not observed
Legacy HTTP+SSE transport
no
Dynamic client registration
not observed
Client ID metadata documents
not observed
  • HighThe whole server

    The endpoint served tools/list without credentials, and the list has 4 tools that change things (1 irreversible, 3 write). Whether a call also works without credentials was not tested: tools are never called.

    Matched text

    https://hookden.pages.dev/mcp: tools/list returned 7 tools to an anonymous client, including send_test_webhook (irreversible), create_bin (write), set_response (write), verify_signature (write)

    What this check looks for

Findings

Matches of fixed checks, with the text they matched.

No check matched anything in these tool definitions. That is not a safety guarantee.

History

Changes to its tool definitions and to its remote endpoint, newest first.

No change seen yet. Its tools are rescanned every day, and a remote endpoint is looked at once a week.

Install

Pinned to version 1.3.0. Values in angle brackets are yours to fill in.

claude mcp add --transport http hookden https://hookden.pages.dev/mcp
claude mcp add --transport http hookden https://hookden.pages.dev/mcp

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__hookden__list_captures",
      "mcp__hookden__get_capture",
      "mcp__hookden__wait_for_capture"
    ],
    "ask": [
      "mcp__hookden__create_bin",
      "mcp__hookden__send_test_webhook",
      "mcp__hookden__set_response",
      "mcp__hookden__verify_signature"
    ],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as hookden. Review it before you use it.

Capability tags behind 2 rules
  • mcp__hookden__send_test_webhook outbound
  • mcp__hookden__verify_signature outbound

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://radar.anlyon.com/api/v1/servers/dev.pages.hookden/hookden/verify?hash=75fad325105af1d99509af9111c89fe1ceb70e47c62d88aaf4fe6871cd3e5a88" | jq -e '.changed == false'

Pinned hash 75fad325105a, from Nov 15, 2026, 02:18 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/dev.pages.hookden/hookden/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for dev.pages.hookden/hookden
[![Anlyon Radar](https://radar.anlyon.com/badge/dev.pages.hookden/hookden.svg)](https://radar.anlyon.com/servers/dev.pages.hookden/hookden)

Source: MCP Registry. Synced Oct 21, 2026, 18:12 UTC.

Hookden MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the Hookden MCP server safe?

No scan can promise that. What its definitions show: 7 tools, 4 of which can change, send or delete something, and 0 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.

Can the Hookden MCP server delete data?

No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.

Can the Hookden MCP server do things that cannot be undone?

Yes. 1 tool can send, pay, publish or merge: send_test_webhook.

What tools does the Hookden MCP server have?

7 tools: 1 irreversible, 3 write, 3 read. send_test_webhook, create_bin, set_response, verify_signature, list_captures, get_capture and wait_for_capture.

Does the Hookden MCP server need sign-in or OAuth?

Its remote endpoint listed its tools to an anonymous client, without sign-in.

Does the Hookden MCP server send data to outside services?

2 tools can carry data out (it sends, posts or publishes, or takes a recipient, channel or URL): send_test_webhook and verify_signature.

Has the Hookden MCP server changed its tools?

Not since Anlyon Radar started tracking it. Last scanned Nov 15, 2026.