# WebhookTest.net

> WebhookTest.net provides temporary public webhook endpoints, a browser inspector, and an anonymous hosted MCP server for AI-agent testing.

## MCP server

- Product and setup overview: https://webhooktest.net/mcp-server
- Streamable HTTP endpoint: https://webhooktest.net/mcp
- Protocol: stateless Model Context Protocol over Streamable HTTP
- Authentication: none
- Version: 1.0.0
- Announced individual-request age limit: requests older than 15 days, including existing captures in active buckets. Effective date and periodic cleanup details: https://webhooktest.net/retention
- Unchanged limits: bucket deletion after 15 days of inactivity when cleanup is enabled; per-bucket ceilings of 10,000 requests or 50 MiB. This announcement does not confirm backend activation.
- Capability boundary: possession of the UUID bucket ID grants access to that bucket

The MCP server exposes eight tools: create_webhook_bucket, get_webhook_bucket, list_webhooks, get_webhook, wait_for_webhook, configure_webhook_response, clear_webhooks, and delete_webhook_bucket. Clear and delete require confirm=true and are marked destructive.

Captured Authorization, cookie, API-key, token, secret, password, and signature-like header or query values are redacted from MCP output by default. A caller must explicitly set include_sensitive=true to retrieve them. Individual bodies are limited to 64 KiB by default and 256 KiB at most. Use synthetic data and never send production secrets, payment information, or personal data.

## Setup guides

- General MCP webhook workflow: https://webhooktest.net/guides/mcp-webhook-inspector
- Claude: https://webhooktest.net/guides/claude-webhook-testing
- Cursor: https://webhooktest.net/guides/cursor-webhook-testing
- Codex: https://webhooktest.net/guides/codex-webhook-testing

## Recommended workflow

1. Connect the remote server URL.
2. Call create_webhook_bucket and keep the returned bucket ID private.
3. Send a synthetic request to the returned webhook_endpoint.
4. Call wait_for_webhook, list_webhooks, and get_webhook to inspect delivery evidence.
5. Optionally configure a custom response to exercise retry and error handling.
6. Clear captures or delete the bucket with explicit confirmation.

## Human-facing documentation

- Webhook testing guides: https://webhooktest.net/blog
- Browser webhook tester: https://webhooktest.net/