Developer · Remote MCP server

WebhookTest.net

Anonymous webhook capture, inspection, waiting, and response configuration for AI agents.

Visit WebhookTest.net's website

What the MCP Registry states

The entry as published to the official MCP Registry (read 2026-10-04), latest version.

Registry name
net.webhooktest/webhook-tester
Version
1.0.1
Status
Active
Category
developer
Transport
Streamable HTTP
Published
2026-09-23
Updated
2026-09-23
Publisher
net.webhooktest
Namespace
Namespace verified by the MCP Registry via the domain webhooktest.net · how
Website
webhooktest.net/mcp-server
Source
Registry API entry

Remote endpoints

TransportURLHeaders declared
Streamable HTTPhttps://webhooktest.net/mcpNone

Live check

This directory connected to each remote endpoint and asked for its list of tools. The check connects and lists tools only; it doesn't run tools, sign in or test security.

Reachable
Yes (HTTP 200)
Handshake
net.webhooktest/webhook-tester 1.0.1 · protocol 2025-06-18
Tools discovered
8: clear_webhooks, configure_webhook_response, create_webhook_bucket, delete_webhook_bucket, get_webhook, get_webhook_bucket, list_webhooks, wait_for_webhook
Checked on
2026-10-05

How the live check works

How to connect WebhookTest.net

WebhookTest.net is a remote MCP server: there is nothing to install. Its endpoint is https://webhooktest.net/mcp, served over Streamable HTTP. In an assistant that accepts remote MCP servers (often under a setting named connectors, integrations or tools), add a new server and give it this URL; in a client configured by file, add it as a remote (HTTP) server with the same URL.

No headers are declared in the registry entry. If the server needs you to sign in, a client that supports MCP authorization opens the service's own sign-in page when it first connects.

Derived from the registry entry; the live check above only shows whether the endpoint answered. What the server does, and on what terms, is set by its publisher; check its repository or website before giving it access to your accounts or files. How to add an MCP server to an assistant · Before you connect

More developer servers

All 5,152 →
ServerRunsEndpoint or package
Webhook StudioKeyless webhook endpoints: capture, wait, replay, forward, and generate types from real traffic.Remote · HTTPLive check: ✓ handshakewebhook-studio.com
Webhook ToolkitWebhook URLs for AI agents: receive, wait for, replay, sign and verify webhooks (Stripe, GitHub…).Remote & Local · HTTP, stdioLive check: ✓ handshakewebhook-toolkit.com
webhook.coReceive, inspect, replay and deliver webhooks - with signature verification and agent triggers.Remote · HTTPLive check: sign-in requiredmcp.webhook.co
Webhook.site MCP ServerCapture HTTP, email, and DNS callbacks with webhook.site from MCP clients.Local · stdioPyPI: webhook-mcp-server
Webmcpactionreceipt MCPPaid remote MCP for WebMCP action receipt MCP, structured receipts, audit logs, and reviewer-ready e.Remote · HTTPLive check: ✗ no handshakewebmcpactionreceipt.clauxel.com
WebnavA zero-LLM MCP server that replays recorded site maps instead of re-exploring browser routes.Local · stdionpm: @dikshanty94/webnav
WeboperatorHands your live Chrome tab to any MCP client - snapshot, navigate, click, type, extract.Local · stdionpm: weboperator-mcp
WebsharpSearch the web and extract article text for LLMs.Local · HTTPOCI image (Docker): docker.io/jessegador/websharp-mcp:v0.99.0-rc2