Webhook Inspector

com.voronyuk.webhookPublished by webhook.voronyuk.comOfficial publisherv1.0.3Updated Oct 27, 2026

Capture and inspect webhooks: create URLs, wait for requests, read headers and bodies, set replies.

VerifiedStreamable HTTPWeb executableDeveloper Tools

Overview

AI-generated overview

Remote MCP server for capturing and inspecting webhooks: create URLs, wait for incoming requests, read headers and bodies, and set replies.

What you can do
  • Create webhook URLs to receive incoming requests
  • Wait for requests to arrive on a created URL
  • Read the headers and bodies of captured requests
  • Set the replies returned to the sender
When to use it
Useful when testing or debugging outbound webhooks from a service, or when an assistant needs to see the exact payload and headers a third party sends. It saves setting up a local tunnel or listener for quick inspection.
Requirements
A remote endpoint at webhook.voronyuk.com reached over streamable HTTP, with OAuth sign-in required. No packages, environment variables or headers are declared.
Before you install
Incoming webhook payloads may contain sensitive data from third-party services, and captured requests are stored on the provider's hosted service. Setting replies changes what the sending service receives. OAuth grants access to the account on that service.

Installation

In SourceWeft

  1. Open Webhook Inspector in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/com.voronyuk.webhook%2Finspector/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

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

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

1
  1. v1.0.3LatestOct 20, 2026

Score

67% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.