Connect the remote server
Add the HTTPS URL to a client that supports Streamable HTTP. The service is anonymous: there is no OAuth flow, API key, local package, or account.
Hosted MCP server ยท v1.0.0
Webhook testing for AI agents.
Give an MCP client a temporary public endpoint, inspect the next delivery, and tune its HTTP response without leaving the agent workflow.
AnonymousStreamable HTTP8 tools
Remote Streamable HTTP endpoint
https://webhooktest.net/mcpSetup and test workflow
Ask the agent to create a bucket
The create_webhook_bucket tool returns a capability-style bucket ID, webhook endpoint, dashboard link, and the 15-day inactivity policy.
Trigger and inspect a delivery
Send a test event to the returned endpoint, then use wait_for_webhook, list_webhooks, or get_webhook to examine the request.
Shape the sender response
Use configure_webhook_response to return a chosen status, content type, and body. Clear captures or delete the bucket with explicit confirmation when testing ends.
What the server exposes
Create and understand
`create_webhook_bucket` creates a temporary endpoint; `get_webhook_bucket` reads its name and response settings.
Observe deliveries
`wait_for_webhook` waits up to 25 seconds; `list_webhooks` paginates summaries; `get_webhook` returns one scoped capture.
Control and clean up
`configure_webhook_response` changes the reply. `clear_webhooks` and `delete_webhook_bucket` require explicit confirmation.
Privacy and limits
Authorization, cookie, API-key, token, secret, password, and signature-like header or query values are redacted by default. Agents must explicitly request sensitive values. Bodies are limited to 64 KiB in tool output by default and can be raised only to 256 KiB. Use synthetic data: the endpoint is a debugging service, not a production processor.
Troubleshooting
- Use the exact HTTPS URL and select remote or Streamable HTTP transport.
- Restart or reload the client after changing MCP configuration.
- Check that corporate policy allows the endpoint and outbound HTTPS.
- A timeout with
received:falseis successful; verify the sender used the returned bucket URL. - HTTP 429 means the per-IP call, creation, bucket, or concurrent-wait limit was reached.