Skip to main content
Glama

Server Details

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

If you are the author of this connector, you can claim ownership. Claimed connector authors can inspect health checks, view analytics, and manage their listing.
Status
Healthy
Uptime
100.0% over the last 24 hours
Last Tested
Transport
Streamable HTTP · MCP 2025-11-25
URL
Repository
THE-KIPDEV/webhook-toolkit
GitHub Stars
0
Server Listing
webhook-toolkit
ChatGPT
–
Claude
–

TDQS

A4.2/5.0

Scored across 10 tools

Disambiguation5/5

Each tool targets a distinct action in the webhook lifecycle: create/list URLs, capture/inspect/wait for requests, set responses, replay, sign/verify, and explain. There is no meaningful overlap, and even similar-looking tools like get_webhook_request and explain_webhook_request are clearly separated as raw retrieval versus AI analysis.

Naming Consistency5/5

All tools follow a consistent `verb_webhook_noun` pattern in snake_case: create_, list_, get_, replay_, set_, sign_, verify_, wait_, explain_. The noun after the verb is also predictable, using webhook_url, webhook_request, webhook_response, webhook_payload, or webhook_signature. Naming is uniform and easy to predict.

Tool Count5/5

Ten tools is within the well-scoped 3-15 range and each tool earns its place by covering a distinct part of the webhook workflow: creating endpoints, inspecting traffic, simulating responses, replaying requests, and testing signatures. No tool feels redundant or filler.

Completeness4/5

The tool surface covers the full webhook debugging loop: create a URL, capture and inspect requests, wait for incoming events, set custom responses, replay, sign, verify, and receive AI explanations. Minor gaps exist, such as the lack of a delete webhook URL tool and no single-URL detail endpoint, but these can be worked around and do not block the core purpose.

Available Tools

10 tools
create_webhook_urlCreate a webhook URLAInspect

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.

Inputs: name.

explain_webhook_requestExplain a webhook / write its handler (AI)AInspect

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.

Inputs: token (required), request_id (required), mode, language.

get_webhook_requestGet a captured requestA
Read-only
Inspect

Return one captured request in full (headers, raw body, detected provider/event).

Inputs: token (required), request_id (required).

list_webhook_requestsList captured requestsA
Read-only
Inspect

List the most recent requests captured by a webhook URL, newest first (summaries; use get_webhook_request for one full request).

Inputs: token (required), limit.

list_webhook_urlsList my webhook URLsA
Read-only
Inspect

List the webhook URLs of the account behind the API key (requires an API key).

Inputs: no named parameters.

replay_webhook_requestReplay a captured requestAInspect

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).

Inputs: token (required), request_id (required), target_url (required).

set_webhook_responseSet the HTTP responseAInspect

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.

Inputs: token (required), body, status, content_type.

sign_webhook_payloadSign a test webhook payloadAInspect

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.

Inputs: secret (required), provider (required), payload, event_type, +1 more.

verify_webhook_signatureVerify a webhook signatureA
Read-only
Inspect

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.

Inputs: secret (required), provider (required), raw_body (required), signature (required), +2 more.

wait_for_webhookWait for a webhookA
Read-only
Inspect

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.

Inputs: token (required), after, timeout_seconds.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    Related MCP Connectors

    Related MCP Servers

    • A
      license
      A
      quality
      C
      maintenance
      Let AI agents operate your webhook gateway: inspect failed deliveries, read payloads, replay dropped events, and fire test webhooks.
      4
      22 npm
      MIT
    • A
      license
      A
      quality
      D
      maintenance
      Enables AI agents to create disposable webhook URLs, capture incoming HTTP requests, inspect headers and bodies, and replay them against local or remote endpoints, streamlining the webhook handler development loop.
      5
      6 npm
      MIT
    Try in Browser

    Glama MCP Gateway

    Add one secure layer between your agents and this server.