Skip to content

Webhook Toolkit

by THE-KIPDEV · remote · local (npm) · no sign-in to list tools · v0.1.1 · published by GitHub user THE-KIPDEV

Webhook URLs for AI agents: receive, wait for, replay, sign and verify webhooks (Stripe, GitHub…).

Changes · 5
CompareRegistry entry

10 tools: 5 change things and 5 only read.

Scanned Oct 21, 2026

No check matched anything in the tool definitions. No finding is not a safety guarantee. How the checks work.

claude mcp add --transport http webhook-toolkit https://webhook-toolkit.com/mcp

Tools

Open a tool for its reasons and full description. Descriptions are the publisher's own words, shown as they are.

10 tools

Changes things 5Claude Code: ask
  • create_webhook_urlCreate a public HTTPS URL that captures every request sent to it (any method, any sub-path).No findings

    Why it is in this group

    • The name "create_webhook_url" says "create": a word for a change.
    Description, as the server wrote it
    Create a public HTTPS URL that captures every request sent to it (any method, any sub-path). Use it when you need an endpoint to receive a webhook from a third-party service while building or debugging an integration. Returns the URL to configure in the service and a live inspector link for the human.
  • replay_webhook_requestRe-send a captured request (same method, headers and raw body) to a PUBLIC URL and return the target's response.No findings

    Why it is in this group

    • The name "replay_webhook_request" says "request": a word for a change.
    Description, as the server wrote it
    Re-send a captured request (same method, headers and raw body) to a PUBLIC URL and return the target's response. Localhost and private IPs are refused here: for localhost use the CLI (`npx webhook-toolkit replay`) or the local MCP server (`npx webhook-toolkit mcp`).
  • set_webhook_responseChoose what the webhook URL answers to callers (status code, body, content type) — e.g.No findings

    Why it is in this group

    • The name "set_webhook_response" says "set": a word for a change.
    Description, as the server wrote it
    Choose what the webhook URL answers to callers (status code, body, content type) — e.g. return 500 to test the sender's retries, or a specific JSON/XML body the service expects.
  • sign_webhook_payloadBuild a webhook body with a VALID signature header for a provider, to test a handler's signature verification without triggering a real event.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    Build a webhook body with a VALID signature header for a provider, to test a handler's signature verification without triggering a real event. Providers: stripe, github, shopify, slack, twilio, mailgun. Returns the headers, the exact body to send and a ready-to-run curl command.
  • verify_webhook_signatureCheck whether a webhook signature is valid for a raw body and a secret, and diagnose why it fails (wrong secret, whitespace, re-serialized JSON body, expired timestamp, wrong URL f…No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    Check whether a webhook signature is valid for a raw body and a secret, and diagnose why it fails (wrong secret, whitespace, re-serialized JSON body, expired timestamp, wrong URL for Twilio). Providers: stripe, github, shopify, slack, twilio.

    Annotations the server declares

    • readOnlyHint: true
Only reads 5Claude Code: allow
  • explain_webhook_requestAI analysis of a captured request.No findings

    Why it is in this group

    • The name "explain_webhook_request" says "explain": a word for reading.
    Description, as the server wrote it
    AI analysis of a captured request. mode=explain: who sent it, which event, key fields, how to verify the signature, pitfalls. mode=handler: complete receiving code that verifies the signature and handles this event. Included in paid plans; anonymous and free users get 3 trials.
  • get_webhook_requestReturn one captured request in full (headers, raw body, detected provider/event).No findings

    Why it is in this group

    • The name "get_webhook_request" says "get": a word for reading.
    Description, as the server wrote it
    Return one captured request in full (headers, raw body, detected provider/event).

    Annotations the server declares

    • readOnlyHint: true
  • list_webhook_requestsList the most recent requests captured by a webhook URL, newest first (summaries; use get_webhook_request for one full request).No findings

    Why it is in this group

    • The name "list_webhook_requests" says "list": a word for reading.
    Description, as the server wrote it
    List the most recent requests captured by a webhook URL, newest first (summaries; use get_webhook_request for one full request).

    Annotations the server declares

    • readOnlyHint: true
  • list_webhook_urlsList the webhook URLs of the account behind the API key (requires an API key).No findings

    Why it is in this group

    • The name "list_webhook_urls" says "list": a word for reading.
    Description, as the server wrote it
    List the webhook URLs of the account behind the API key (requires an API key).

    Annotations the server declares

    • readOnlyHint: true
  • wait_for_webhookBlock until the next request reaches a webhook URL (or the timeout elapses), then return it in full: method, path, headers, body, detected provider and event.No findings

    Why it is in this group

    • The name "wait_for_webhook" says "wait": a word for reading.
    Description, as the server wrote it
    Block until the next request reaches a webhook URL (or the timeout elapses), then return it in full: method, path, headers, body, detected provider and event. Use right after triggering an action that should send a webhook. Call again with `after` set to the last request's createdAt to wait for the following one.

    Annotations the server declares

    • readOnlyHint: true

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.

Install

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

claude mcp add --transport http webhook-toolkit https://webhook-toolkit.com/mcp

Run in a terminal.

Claude Code permissions

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

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__webhook-toolkit__list_webhook_urls",
      "mcp__webhook-toolkit__wait_for_webhook",
      "mcp__webhook-toolkit__list_webhook_requests",
      "mcp__webhook-toolkit__get_webhook_request",
      "mcp__webhook-toolkit__explain_webhook_request"
    ],
    "ask": [
      "mcp__webhook-toolkit__create_webhook_url",
      "mcp__webhook-toolkit__set_webhook_response",
      "mcp__webhook-toolkit__replay_webhook_request",
      "mcp__webhook-toolkit__sign_webhook_payload",
      "mcp__webhook-toolkit__verify_webhook_signature"
    ],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. It assumes the server is installed as webhook-toolkit. Review it before you use it.