Skip to content

Webhook Toolkit MCP server

io.github.THE-KIPDEV/webhook-toolkitTHE-KIPDEVstreamable-httpv0.1.1Scanned

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

10 tools: 5 change things and 5 only read.

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

Tools listed without sign-in. Remote posture

With Anlyon

5 tools here change things. Govern them.

  • 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 Webhook Toolkit MCP server can do

The Webhook Toolkit MCP server is published by the GitHub account THE-KIPDEV. It has 10 tools. It can create or change data (5 tools: create_webhook_url, set_webhook_response, replay_webhook_request, sign_webhook_payload and 1 more), but cannot delete data. 5 tools only read.

3 tools bring in text other people can write (list_webhook_urls, wait_for_webhook and list_webhook_requests); 3 tools can send data out of your system (replay_webhook_request, sign_webhook_payload and verify_webhook_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 16, 2026, version 0.1.1.

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.

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.Can send data outNo findings

    Why it is in this group

    • The name "replay_webhook_request" says "request": a word for a change.

    What it can reach

    • outboundThe input takes a URL (input.target_url): a request to a URL can carry data to whoever runs it.
    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.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.target_url): a request to a URL can carry data to whoever runs it.
    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…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.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    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
    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 5Show 5 read-only tools
  • 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).Reads text others writeNo findings

    Why it is in this group

    • The name "list_webhook_requests" says "list": a word for reading.

    What it can reach

    • untrusted-inputThe description's first sentence says "list" and "url": it reads web pages, which anyone can write.
    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).Reads text others writeNo findings

    Why it is in this group

    • The name "list_webhook_urls" says "list": a word for reading.

    What it can reach

    • untrusted-inputThe name "list_webhook_urls" says "list" and "url": it reads web pages, which anyone can write.
    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.Reads text others writeNo findings

    Why it is in this group

    • The name "wait_for_webhook" says "wait": a word for reading.

    What it can reach

    • untrusted-inputThe description's first sentence says "url": it reads web pages, which anyone can write.
    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.

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.

Reads private data0
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write3
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out3
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, 19:01 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
5
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
  • WarnThe whole server

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

    Matched text

    https://webhook-toolkit.com/mcp: tools/list returned 10 tools to an anonymous client, including create_webhook_url (write), set_webhook_response (write), replay_webhook_request (write), sign_webhook_payload (write), verify_webhook_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 0.1.1. Values in angle brackets are yours to fill in.

claude mcp add --transport http webhook-toolkit https://webhook-toolkit.com/mcp
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 or a way out, 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. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as webhook-toolkit. Review it before you use it.

Capability tags behind 6 rules
  • mcp__webhook-toolkit__list_webhook_urls untrusted-input
  • mcp__webhook-toolkit__wait_for_webhook untrusted-input
  • mcp__webhook-toolkit__list_webhook_requests untrusted-input
  • mcp__webhook-toolkit__replay_webhook_request outbound
  • mcp__webhook-toolkit__sign_webhook_payload outbound
  • mcp__webhook-toolkit__verify_webhook_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/io.github.THE-KIPDEV/webhook-toolkit/verify?hash=1786ea937432e61d7e73e6cd28bc64040e8ba0804866822e05e08a2ca83cbe36" | jq -e '.changed == false'

Pinned hash 1786ea937432, from Nov 16, 2026, 06:18 UTC.

Watch

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

https://radar.anlyon.com/servers/io.github.THE-KIPDEV/webhook-toolkit/changes.xml

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

Badge

Anlyon Radar badge for io.github.THE-KIPDEV/webhook-toolkit
[![Anlyon Radar](https://radar.anlyon.com/badge/io.github.THE-KIPDEV/webhook-toolkit.svg)](https://radar.anlyon.com/servers/io.github.THE-KIPDEV/webhook-toolkit)

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

Webhook Toolkit MCP server: questions and answers

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

Is the Webhook Toolkit MCP server safe?

No scan can promise that. What its definitions show: 10 tools, 5 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 Webhook Toolkit MCP server delete data?

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

Can the Webhook Toolkit MCP server do things that cannot be undone?

No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.

What tools does the Webhook Toolkit MCP server have?

10 tools: 5 write, 5 read. create_webhook_url, set_webhook_response, replay_webhook_request, sign_webhook_payload, verify_webhook_signature, list_webhook_urls, wait_for_webhook, list_webhook_requests and 2 more.

Does the Webhook Toolkit MCP server need sign-in or OAuth?

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

Does the Webhook Toolkit MCP server send data to outside services?

3 tools can carry data out (it sends, posts or publishes, or takes a recipient, channel or URL): replay_webhook_request, sign_webhook_payload and verify_webhook_signature.

Has the Webhook Toolkit MCP server changed its tools?

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