API Tools

webhook-toolkit.com

Creates and manages temporary webhook URLs to capture, list, and inspect incoming HTTP requests for testing and debugging API integrations.

1 endpoint10 known toolsFirst detected September 19, 2026Last detected September 19, 2026

ENDPOINT 1

https://webhook-toolkit.com/mcp

No auth detected

MCP server metadata

Name: webhook-toolkit
Version: 1.0.0

Capabilities

tools.listChanged

Server instructions

Webhook Toolkit gives you public URLs that capture any HTTP request (webhooks) so you can test integrations with third-party services (Stripe, GitHub, Shopify, Slack, Twilio, PayPal…). Typical flow: create_webhook_url → give the URL to the service (or trigger the event) → wait_for_webhook → inspect headers/body → optionally explain_webhook_request. Anonymous URLs expire after 7 days; with an API key they are permanent.

Known tools 10

create_webhook_url

Create a public HTTPS URL that captures every request sent to it (any method, any sub-path).

Potential side effects

list_webhook_urls

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

Inferred read-only

wait_for_webhook

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.

Inferred read-only

list_webhook_requests

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

Inferred read-only

get_webhook_request

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

Inferred read-only

set_webhook_response

Choose what the webhook URL answers to callers (status code, body, content type) — e.

Inferred read-only

replay_webhook_request

Re-send a captured request (same method, headers and raw body) to a PUBLIC URL and return the target's response.

Potential side effects

sign_webhook_payload

Build a webhook body with a VALID signature header for a provider, to test a handler's signature verification without triggering a real event.

Inferred read-only

verify_webhook_signature

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

Inferred read-only

explain_webhook_request

AI analysis of a captured request.

Inferred read-only

CONNECT WITH APPROVAL

Client installation

Review this server and its permissions before adding it. Secret placeholders must be set locally.

Codex

~/.codex/config.toml

[mcp_servers.webhook-toolkit]
url = "https://webhook-toolkit.com/mcp"
enabled = true

Claude Code

.mcp.json

{
  "mcpServers": {
    "webhook-toolkit": {
      "type": "http",
      "url": "https://webhook-toolkit.com/mcp"
    }
  }
}

Claude Desktop

Settings → Connectors → Add custom connector

Name: webhook-toolkit
Remote MCP URL: https://webhook-toolkit.com/mcp

Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.

Cursor

.cursor/mcp.json

{
  "mcpServers": {
    "webhook-toolkit": {
      "url": "https://webhook-toolkit.com/mcp"
    }
  }
}

Visual Studio Code

.vscode/mcp.json

Add to Visual Studio Code

{
  "servers": {
    "webhook-toolkit": {
      "type": "http",
      "url": "https://webhook-toolkit.com/mcp"
    }
  }
}

Generic MCP

Client-specific MCP configuration

{
  "name": "webhook-toolkit",
  "transport": "streamable-http",
  "url": "https://webhook-toolkit.com/mcp"
}

MCP Inspector

Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.

TRUST AND VERIFICATION EVIDENCE

Loading Trust v2 evidence…

Checking the associated registrable domain. The BuiltWith key remains server-side.

Indexed

Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.